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

Problem with scaleFactor setting in bamCoverage #482

Closed
ycl6 opened this issue Feb 14, 2017 · 2 comments
Closed

Problem with scaleFactor setting in bamCoverage #482

ycl6 opened this issue Feb 14, 2017 · 2 comments

Comments

@ycl6
Copy link

ycl6 commented Feb 14, 2017

Hi,

I am using bamCoverage to generate signal file for viewing on UCSC. So I choose to output as bedGraph format because I need to edit the chrom prefix before I convert it to bigwig. I set the scaleFactor as follow

bamCoverage --numberOfProcessors 10 --scaleFactor 0.9022 --binSize 1 --outFileFormat bedgraph --filterRNAstrand forward --bam file.bam -o forward.bedGraph

But when I view the output file, it seems the values are not scaled. Why is it so?

1       1640711 1640713 6
1       1640713 1640725 8
1       1640725 1640726 12
1       1640726 1640778 16
1       1640778 1640780 14
1       1640780 1640844 12
1       1640844 1640853 10
1       1640853 1640854 4
1       1640854 1640857 2
1       1640857 1640879 0
@dpryan79
Copy link
Collaborator

Please note the help for the --scaleFactor option:

Indicate a number that you would like to use. When used in combination with --normalizeTo1x or --normalizeUsingRPKM, the computed scaling factor will be multiplied by the given scale factor.

Since you didn't use --normalizeUsingRPKM or --normalizeTo1X then --scaleFactor was ignored.

Having said that, I can make this possible in the next release.

@dpryan79
Copy link
Collaborator

This is now implemented in the develop branch and will be present in the 2.5.0 release.

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