You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have aligned contigs to longreads using Minimap2 and generated the paf file. I am trying to use racon to get a consensus of these.
The command I am using:
./racon PA_hifi.fa minimapConToHiFimapped_PA.paf minia_contigs_Pseudomonas.contigs.fa
and the error I am getting is:
[racon::Polisher::initialize] loaded target sequences 0.059568 s
[racon::Polisher::initialize] error: duplicate sequence 0 with unequal data
I know that minimap2 gives more than one position for a particular contig. Is that the reason I am getting this error?
But I am also having the same error with mashmap alignment where it is giving me one hit. I have checked by grep if my files have any duplicate sequences or not which it does not.
The text was updated successfully, but these errors were encountered:
Hello,
do files PA_hifi.fa and minia_contigs_Pseudomonas.contigs.fa have a sequence with the same name but different data? Racon has error correction mode for which we included a check that if a sequence name appears in both files it should have the same length (which should imply the same contents).
I have aligned contigs to longreads using Minimap2 and generated the paf file. I am trying to use racon to get a consensus of these.
The command I am using:
./racon PA_hifi.fa minimapConToHiFimapped_PA.paf minia_contigs_Pseudomonas.contigs.fa
and the error I am getting is:
[racon::Polisher::initialize] loaded target sequences 0.059568 s
[racon::Polisher::initialize] error: duplicate sequence 0 with unequal data
I know that minimap2 gives more than one position for a particular contig. Is that the reason I am getting this error?
But I am also having the same error with mashmap alignment where it is giving me one hit. I have checked by grep if my files have any duplicate sequences or not which it does not.
The text was updated successfully, but these errors were encountered: