We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi there,
Firstly, thank you nf-core team for the development of this chip-seq pipleine. I have used it successfully multiple times, I LOVE IT.
I was just wondering about the specifics of the normalisation procedure.
You write on the pipeline overview page "Create normalised bigWig files scaled to 1 million mapped reads"
Does this mean that the generated bigwig files are just scaled to reads per million - or are these resulting bigwig files also normlaised to input?
If they are normalised to input are they IP-input or IP/input? Also, if they are normalised to input then is there a way to circumvent this?
Thanks and all the best,
Alex
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Description of feature
Hi there,
Firstly, thank you nf-core team for the development of this chip-seq pipleine. I have used it successfully multiple times, I LOVE IT.
I was just wondering about the specifics of the normalisation procedure.
You write on the pipeline overview page "Create normalised bigWig files scaled to 1 million mapped reads"
Does this mean that the generated bigwig files are just scaled to reads per million - or are these resulting bigwig files also normlaised to input?
If they are normalised to input are they IP-input or IP/input? Also, if they are normalised to input then is there a way to circumvent this?
Thanks and all the best,
Alex
The text was updated successfully, but these errors were encountered: