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

Optimizing run time #43

Closed
will-NYGC opened this issue Aug 10, 2016 · 3 comments
Closed

Optimizing run time #43

will-NYGC opened this issue Aug 10, 2016 · 3 comments

Comments

@will-NYGC
Copy link

Hi, I have ATAC-seq libraries with between 200-300M mapped reads and NucleoATAC is taking in the order of 5-10 days to run. I'm using 4 cores, as well, and and am hesitant to increase this b/c of increased memory demands. Do you have any suggestions as to how to speed up run times?

@AliciaSchep
Copy link
Contributor

I would look at what fraction of the genome you are running it, if your peak calling is quite liberal, it might make sense to run it on peaks with higher coverage only (what is read count for weakest peak?). Don't really have any tips beyond that and increasing cores unfortunately.

@will-NYGC
Copy link
Author

thanks for suggestion. Do you have any guidance as to the level of minimum coverage needed to get useful results from NucleoATAC?

@will-NYGC will-NYGC reopened this Aug 12, 2016
@AliciaSchep
Copy link
Contributor

addressed in #50

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