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
However, I think there is a bug as the start coordinate is 9094 and alignment length 111 (from CIGAR) = end of alignment 9195, which is longer than the reference (9181bp). What I think is going on is the start coordinate is flipped with the end coordinate, as when I TBLASTX these sequences, the alignment spans ~8994 to ~9098:
OR
and when I output in SAM via blastn, I get the following:
Not sure if related to #845. I tried reviewing the source but couldn't spot the issue and it looks like MMSeqs tries to do the correct thing (as per SAM spec) here,
Thanks for your hard work on MMSeqs!
I ran the following using v
17.b804f
installed via bioconda:Query:
Reference: NC_001802.1
I got the following alignment:
However, I think there is a bug as the start coordinate is 9094 and alignment length 111 (from CIGAR) = end of alignment 9195, which is longer than the reference (9181bp). What I think is going on is the start coordinate is flipped with the end coordinate, as when I TBLASTX these sequences, the alignment spans ~8994 to ~9098:
OR
and when I output in SAM via blastn, I get the following:
Not sure if related to #845. I tried reviewing the source but couldn't spot the issue and it looks like MMSeqs tries to do the correct thing (as per SAM spec) here,
MMseqs2/src/util/convertalignments.cpp
Lines 733 to 734 in 8ef870f
The text was updated successfully, but these errors were encountered: