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

Determine which parameters matter/should be added for peak callers of interest #6

Open
3 of 4 tasks
j-andrews7 opened this issue Apr 3, 2022 · 1 comment
Open
3 of 4 tasks
Labels
Monday For doin' on Monday.

Comments

@j-andrews7
Copy link
Contributor

j-andrews7 commented Apr 3, 2022

Many of the peak callers mentioned in #2 have a ton of parameters. Some matter, some don't. Making note of which ones are worth making available to the user and which should just use default settings will be important.

Pretty easy to adjust later, so we can throw the obvious ones up at first and go from there.

  • MACS2
  • PeakRanger - Actually has 3 different peak callers in it (ranger, ccat, bcp).
  • MACS - Gonna have to check the command line for this one, can't even find the manual online anymore.
  • SICER2 - This actually contains another variant of their peakcaller called RECOGNICER too.
@j-andrews7 j-andrews7 added the Monday For doin' on Monday. label Apr 3, 2022
@j-andrews7
Copy link
Contributor Author

#13 took care of this for MACS2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Monday For doin' on Monday.
Projects
None yet
Development

No branches or pull requests

1 participant