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

Can I run nucleoatac with a consensus peak file? #56

Closed
ghost opened this issue Apr 6, 2017 · 2 comments
Closed

Can I run nucleoatac with a consensus peak file? #56

ghost opened this issue Apr 6, 2017 · 2 comments

Comments

@ghost
Copy link

ghost commented Apr 6, 2017

Hello,

I have ATAC-seq samples from which I called peaks using MACS2 to create a consensus peak file (as advised by https://academic.oup.com/nar/article-lookup/doi/10.1093/nar/gku351). Now I would like to run nucleoatac to identify nucleosome positions.

nucleoatac run --bed consensus.broadPeaks --bam sample1.bam --fasta mm10.fa --out sample1 --cores 16";

nucleoatac run --bed consensus.broadPeaks --bam sample2.bam --fasta mm10.fa --out sample1 --cores 16";

nucleoatac run --bed consensus.broadPeaks --bam sample3.bam --fasta mm10.fa --out sample1 --cores 16";

... and so on for 32 samples.

Can I pass the same (consensus) peak file to each sample bam file?

Thank you

@AliciaSchep
Copy link
Contributor

Yup that should be fine!

One thing I'll note is that when interpreting the output it is important to remember that lack of nucleosome signal or call on its own does not imply lack of nucleosome; without sufficient reads (i.e. sufficient accessibility at the linkers) NucleoATAC won't be able to detect a nucleosome. This becomes especially important when considering a set of peaks that is a merge of several peak sets where there may be some peaks with very low coverage in some of the samples.

@ghost
Copy link
Author

ghost commented Apr 7, 2017

Thank you :)

@ghost ghost closed this as completed Apr 7, 2017
This issue was closed.
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

1 participant