-
Notifications
You must be signed in to change notification settings - Fork 54
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
Methylation data #51
Comments
I don't think so, but I think the XM tag could be added. It would be nice not to have to hit the reference index for methylation extraction... |
@brentp |
when I have to do something like this. I make sure the reads are sorted by chromosome, then, the first time a new chrom is seen, I read that fasta for that chrom into memory. so that's e.g. 250 MB for human chr1. I'd prefer to keep this out of bwa-meth. I think Methyldackel can do this anyway, no? |
MethylDackel just added this feature. It’s a function called “perRead” |
sweet! let's close this then. bwa-meth does a good job for what it does but I want to keep that fairly atomic and let tools like methyl-dackel do the downstream stuff. |
@nchernia : Nice! looks like perRead does what I want. Never would have thought to look at that branch without your prompting - Thanks! |
Thanks for the tool. One question - is there an easy way to detect from the read itself whether or not it is methylated? MethylDackel calculates on a per-cytosine basis but I'm also looking for essentially the inverse. Bismark does this with the XM tag.
The text was updated successfully, but these errors were encountered: