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
I would like to use megadepth for quantifying intron retention events in TCGA patients. When using get_coverage(), I noticed that the start position of all ranges is shifted by 1 nucleotide, which is most likely due to the BED file being 0-based. However, I would expect that in the final GRanges object, the start positions are not 0-based, as these represent true genomic coordinates.
Here is some example where I create a GRanges object with two introns, save them as a BED-File and use the BED-File together with a BigWig-File as input for get_coverage().
In R, and particularly in GRanges objects from the GenomicRanges package, all genomic positions are 1 based and follow R rules. Aka: [1, x]. See how rtracklayer::import() on a BED file internally changes BED position coordinates to R ones.
thanks for the super quick reply. I'm still a little bit confused.
As you said, rtracklayer::import() adjusts the coordinates. Shouldn't I expect megadepth to do the same? Right now, the ranges of the GRanges object reported by get_coverage() have an extra nucleotide at the left end, which is not present in my original ranges.
Hi guys,
I would like to use megadepth for quantifying intron retention events in TCGA patients. When using get_coverage(), I noticed that the start position of all ranges is shifted by 1 nucleotide, which is most likely due to the BED file being 0-based. However, I would expect that in the final GRanges object, the start positions are not 0-based, as these represent true genomic coordinates.
Here is some example where I create a GRanges object with two introns, save them as a BED-File and use the BED-File together with a BigWig-File as input for get_coverage().
As you can see below the start position of the ranges is shifted by 1 nucleotide, which is not the behavior I would expect.
I can easily adjust this on my own but was wondering whether the additional nucleotide is used for the calculation of the mean coverage.
Best,
Mario
The text was updated successfully, but these errors were encountered: