-
Notifications
You must be signed in to change notification settings - Fork 15
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
Bug(s?): Soft clipping in cigar outputs #51
Comments
Definitely a bug. I'm just getting over being sick so it'll probably be next week before I can tackle these though! |
Hope you feel better! |
Almost better. :/ Working on this today, hoping to get it pushed out soon (coincides with the minimap2 version update, so that's actually great!) |
I believe 1 is fixed. 2 may need an additional option. Minimap doesn't output soft clipping options unless it is in SAM format, and does not output it in PAF. So it's not as automated in the upstream library. Will keep working on it though, but it may need to be an additional option. |
@holtjma I've added the option with_cigar_clipping for aligner (aligner.with_cigar_clipping()). I'm keeping it this way as minimap2 does not return the CIGAR with soft clipping except in the string (never seen in PAF, but seen in SAM, for example). Trying to keep the library as close to minimap2 as possible when in default mode. Let me know if that works. I don't have a good example for soft clipping on the front, but I see minimap2 has the workings for it, so if you come up with something you can share, let me know! |
That sounds good to me! I'm not sure why minimap2 does it that way, but I definitely understand the desire to keep it as close as possible. Happy to try everything out once it's ready. Thanks again for taking the time to work on this! |
Hello,
I came across an issue with soft clipping results in the output. I think at least one of these is probably a bug, the other I'm not sure if I'm just missing an option to enable it. For context, I'm using
minimap2 = "0.1.16"
and mapping extracted reference sequences into a read (I can provide more details around how I'm calling .map() if needed).Here are some example output Mappings where I saw the issue:
The key values of the cigar string and cigar Vec, I have extracted below:
There are two issues I noticed in these outputs:
cigar
Vec. I'm not sure if this is a bug, or if I'm just missing an option to make them appear.I found a workaround using the
query_start
andquery_end
fields to get these soft-clipping values. Are you able to confirm if these are bugs or if there's something I'm missing in the usage?Thanks for maintaining this crate!
Matt
The text was updated successfully, but these errors were encountered: