Closed JamesYang1209 closed 2 years ago
Thanks for reporting this issue. We will fix this issue in next major upgrade. As pilon was designed for short read polishing, we would like to know why not using racon for long read polishing instead.
Hi, My workflow is assembly -> racon -> medaka -> pilon -> homopolish to use both long read and short read for polish. Could you advise me if there is any concern about my workflow? Thank you.
Oh. You are doing hybrid assembly. I would put homopolish right after medaka as our models were trained for improving sys errors left by medaka. And I’d move pilon polishing with short reads as the last step. This is, to my best knowledge, the workflow used by other groups, though not comprehendively evaluated.
Thank you for the suggestion, I will follow this workflow.
Hi professor,
Thanks for the new update. I have found that homopolish will crash if I use it after pilon directly. I think the bug is caused by the sequence ID contains " | " which created by pilon. (>Seq1|sizeXXX|pilon) After I substitute " | " to "_" and everything goes well.