Skip to content
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 strand information from/for bedGraph/coverage files #700

Open
jonasbucherETH opened this issue Sep 24, 2024 · 1 comment
Open

Getting strand information from/for bedGraph/coverage files #700

jonasbucherETH opened this issue Sep 24, 2024 · 1 comment

Comments

@jonasbucherETH
Copy link

Is there a straightforward way to get strand information for the bedGraph or coverage files produced by Bismark, without generating a genome-wide cytosine report? I would like to avoid that for runtime reasons, as I don't need the genome-wide report for further analysis. I have been trying to figure out a way with bedtools by using the respective bam file, but I was wondering if there is a more simple solution to this.

@FelixKrueger
Copy link
Owner

coverage2cytosine associates strand information with the positions reported in the coverage file by going through the entire genome sequence, scanning it for Cs (in CpG context in the default mode) and testing if that position was covered in the the coverage file. This approach is reference-based and produces equivalent output between different runs (unless you use a coverage threshold > 0).

Another option could be to scan the coverage file directly, and check if a reported position is a C (+ strand) or G (- strand), however there is currently no option go down this route (it might be a fairly straight forward task for ChatGPT though?). The downside of such an approach is that the output file is different for each sample, and since it is not strictly reference genome based it doesn't have a cytosine context check in place; as a result you may include a certain number of context differences in the output file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants