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
The three valid scenarios for hits being returned from bwa aln are:
Read is unmapped. HN = 0, there should be no XA tags returned, and thus hits = []
Read is mapped, potentially multiply-mapped. 0 < HN <= max_hits. HN = n, where n is the number of hits, and len(hits) == n
Read is multiply-mapped, HN > max_hits. HN = n, where n is the number of hits, and hits = [] because although the primary hit is returned, there are no XA tags representing the alternate reads, so we return none of them.
bwa aln
sometimes returns a read that is unmapped but does have hits (both primary andXA
tag). Suggest that we ignore this case:The text was updated successfully, but these errors were encountered: