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

Clarify Read Inputs and Differential Peak Calling #52

Open
quantumdot opened this issue May 16, 2017 · 1 comment
Open

Clarify Read Inputs and Differential Peak Calling #52

quantumdot opened this issue May 16, 2017 · 1 comment

Comments

@quantumdot
Copy link

I hope that you can clarify the relationship of reads when supplying multiple treatment and control files to epic. For example, are multiple treatment files pooled (like MACS) or are they treated independently?

Also, I have interest in differential peak calling between treated and non-treated ChIP samples with corresponding input controls. Does epic have this ability like SICER-df.sh, or is there a mechanism to reproduce this functionality?

Thanks for the great work, I am enjoying using epic so far.

@endrebak
Copy link
Member

endrebak commented May 17, 2017

No such df-feature unfortunately. Should not be too hard to implement though.

Input files are pooled after removing duplicate reads. The same is true for ChIP btw. If you want to avoid pooling, you should just run epic multiple times, once on each dataset.

I am finishing my PhD right now, so I do not have time to work much on epic. But it isn't abandoned, will do bug fixes and such.

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