-
Notifications
You must be signed in to change notification settings - Fork 594
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
List data access patterns in Picard/GATK/Foghorn #1
Comments
The doc is here -it may be easier to edit as a google doc. https://docs.google.com/a/broadinstitute.org/document/d/10j9UvZQ_jOY2vKz59eHrRdrazxHUscs1DnWan5sVTao/edit# |
Can someone here take inventory of the various Picard tools that you want to consider moving over? These are NOT represented in the GATK best practices document, for example |
@nh13 my sense is that most of picard tools (non-private ones) will either be moved over to hellbender or we'll keep linking to picard (but the latter seems suboptimal - there should be just one toolkit) |
this is done |
We need to understand the data access patterns in the existing engines: Picard/GATK/Foghorn
@lbergelson and @kshakir already started doing it. Can you move the list here?
The text was updated successfully, but these errors were encountered: