-
Notifications
You must be signed in to change notification settings - Fork 7
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
How does modkit extract handle indels on reads? #249
Comments
Hello @Fu-Yilei, I apologize for the delayed response. When you use the |
Thank you Arthur! |
Hello @Fu-Yilei, Using |
Sure I'd love to do that! I have several insertion breakpoint to test in a mixed cell line sample. |
Hey I recently am running modkit on/around some structural variant calls. I was interested in using
modkit extract
to extract the methylation status within each reads on and around SVs. However, when I was trying to runmodkit extract
with given BED file generated from my SV calls, I found themodkit extract
seems only output the location within my provided reference genome.My command is:
modkit extract -t 20 -q 100000 --reference GCA_000001405.15_GRCh38_no_alt_analysis_set.fa --read-calls-path ./modkit_extract/sv_related_read_calls.csv --cpg --include-bed sv_related.bed --allow-non-primary --log-filepath log.log ont.bam sv_related.csv
In here,
sv_related.bed
is several hundreds - thousands bps around the SV breakpoint.Does removing the
--reference
option helps rescuing the locations on reads that are not aligned to the reference genome? Have you guys have any practices with profiling the methylation along with SVs?The text was updated successfully, but these errors were encountered: