-
Notifications
You must be signed in to change notification settings - Fork 104
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
Getting GC context methylation report #621
Comments
Hmm, I would assume that your command is correct, I am not sure if you also need to add Other things:
|
Thanks for spotting this, this bug was triggered when the coverage was set to 0. I have now fixed it in the dev version (here), can you clone the dev branch and try again? |
Hi Felix, Excellent news: it seems to be working now! Apologies that it took some time for me to test it out -- this was my first time cloning a dev branch or running any program from within it, so it took me a minute to figure out (I am learning!). Thank you so much for your help and for debugging. Best, |
Excellent, glad it's working well now! |
Hello,
I am running into an issue when I try running coverage2cytosine with the --gc/--gc_context option.
I run the following command:
coverage2cytosine --gc_context --genome_folder <path> -o <output> [input.cov.gz]
My input file is the *cov.gz file generated by first running bismark_methylation_extractor with the CX context option:
bismark_methylation_extractor --report --buffer_size 10G --gzip --CX --bedGraph --counts --output <output> [input.bam]
When I run the coverage2cytosine GC command, this is what happens:
The first part, "Methylation information will now be written into a genome-wide cytosine report," works as expected. However, the second part, "Methylation information for GC context will now be written to a GpC-context report" fails and returns the following error:
Illegal division by zero at /path/to/opt/anaconda3/bin/coverage2cytosine line 984, <IN> line 48318.
(In the above, I changed my directory names to "/path/to" for privacy reasons).
I would greatly appreciate any help in resolving this, as I have been unable to find a solution on my own so far.
The text was updated successfully, but these errors were encountered: