-
Notifications
You must be signed in to change notification settings - Fork 415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No query sequence in sam? #4
Comments
See the flag "272", in particular the "256" bit. This is the so-called "secondary alignment", which usually don't have SEQ and QUAL to save disk space. BWA-MEM doesn't output secondary alignment by default. When developing minimap2, I found having secondary alignments are often useful for trouble shooting, so I made them outputted by default. Many tools, such as samtools pileup and depth, ignore secondary alignments. If more people find this is confusing, I can switch off the feature by default. |
Secondary alignments are basically alternative and often suboptimal alignments of a read. However, for long noisy reads, the best scoring alignment may not be the true alignment. That is why I thought outputting them may be useful. |
Thanks for the info, I think it's fine to have the secondary alignments on. All the other aligners I had tried for these reads (minialign, bwa mem, ngm-lr, graph map) must have been defaulting to no secondary alignments as well which is why I hadn't seen that output before for this dataset. |
* commit 'f206762c88fb4b2325846e21d03b16572642f928': Mask out warnings and sanitizer failures Avoid trying to access uninitialized variable Avoid buffer overflow in mm_sync_regs Add zlib fallback Add PacBio Meson
Thanks for the quick fix on the last issue. I am also seeing some mapped reads which don't have either the query sequence or qual, yet they seem to be mapped. I thought the query should always be supplied in the sam format in this case or am I wrong? Here is an example from the sam fastq.gz as in issue #3
The text was updated successfully, but these errors were encountered: