You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
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.
The text was updated successfully, but these errors were encountered: