In order to compare coverages in genome browsers, it is desirable to scale them across samples. Add a rule that converts a BAM file to a coverage (e.g., wiggle or bedgraph format) track that is scaled by a constant factor.
Edited
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items ...
Show closed items
Linked items 0
Link issues together to show that they're related.
Learn more.
So this rule generates Read-per-million normalised coverage tracks (.bedgraph or wiggle) for stranded (i.e. separated strands) data. A unstranded version is possible as well. However, I think at least, it can only take one .bam at a time and I generally one .bam corresponds to one library.
@kanitz When you open some mapped reads with IGV and you want to compare two samples (by eye) you can't do that, as the files are not normalized. What you need to do is to scale the coverage by a constant factor. A useful way of normalizing reads is the Reads Per Million (RPM).
1
Dominik Burrichanged title from Add a script that takes as input a list of BAM files and exports them to a format (BAM/bigwig/...) where the data are library size normalized for IGV view to Normalised coverage track for view in IGV
changed title from Add a script that takes as input a list of BAM files and exports them to a format (BAM/bigwig/...) where the data are library size normalized for IGV view to Normalised coverage track for view in IGV