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

List data access patterns in Picard/GATK/Foghorn #1

Closed
akiezun opened this issue Dec 10, 2014 · 4 comments
Closed

List data access patterns in Picard/GATK/Foghorn #1

akiezun opened this issue Dec 10, 2014 · 4 comments
Milestone

Comments

@akiezun
Copy link
Contributor

akiezun commented Dec 10, 2014

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?

@akiezun
Copy link
Contributor Author

akiezun commented Dec 11, 2014

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#

@nh13
Copy link
Contributor

nh13 commented Dec 11, 2014

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 MergeBamAlignment or ValidateSamFile.

@akiezun
Copy link
Contributor Author

akiezun commented Dec 12, 2014

@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)

@akiezun akiezun added this to the Aye-aye milestone Dec 15, 2014
@akiezun
Copy link
Contributor Author

akiezun commented Jan 9, 2015

this is done

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

3 participants