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

examples of the input files to the train process without AQUAS #1

Open
avilella opened this issue Jul 14, 2017 · 1 comment
Open

examples of the input files to the train process without AQUAS #1

avilella opened this issue Jul 14, 2017 · 1 comment

Comments

@avilella
Copy link

Hi,

Are there examples of what the input files to the training process should look like if they haven't been produced by the AQUAS pipeline? E.g. starting from a file like file1_dedup.bam file, what are the peaks and signal tracks files that are needed, and how are they produced by MACS2?

Thanks.

@kohpangwei
Copy link
Collaborator

Hi! Sorry for the late response; just got back from traveling.

We don't have a good example of input files without going through AQUAS, sorry, but you could try to download and extract our processed data to get a sense. You can also look at the prepData.py file and specifically at the run_pipeline_commands() function (line 956, https://github.com/kundajelab/coda/blob/master/prepData.py#L956). That function is essentially a wrapper that makes calls to the AQUAS pipeline via the included shell scripts; once you see which parameters we're passing to the AQUAS pipeline, you can then map those to actual MACS2 calls via the AQUAS documentation (https://docs.google.com/document/d/1lG_Rd7fnYgRpSIqrIfuVlAz2dW1VaSQThzk836Db99c/edit#heading=h.9ecc41kilcvq contains the calls to MACS2 that AQUAS does).

Hope that helps!

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