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

CNV TODOs before release. #3826

Closed
20 of 24 tasks
samuelklee opened this issue Nov 13, 2017 · 6 comments
Closed
20 of 24 tasks

CNV TODOs before release. #3826

samuelklee opened this issue Nov 13, 2017 · 6 comments

Comments

@samuelklee
Copy link
Contributor

samuelklee commented Nov 13, 2017

Legacy pipeline (note, the following should only be done after final ModelSegments PR is in):

ModelSegments pipeline:

gCNV pipeline:

Miscellaneous:

@samuelklee
Copy link
Contributor Author

@vdauwera We will try to have some preliminary slides/evaluations for you for both of the new pipelines, if you'd like to include them in your retreat talk---nothing too technical or detailed, mostly for marketing purposes. Let us know when you'd need things finalized by.

@samuelklee
Copy link
Contributor Author

@asmirnov239 @MartonKN @mbabadi Note the remaining TODOs. Let's be in a position where we can get all gCNV-related branches merged shortly after @mbabadi returns on 1/4 but with a margin before release on 1/9. I will spend some time over break to get my review in.

I will also finish up docs for ModelSegments + update PreprocessIntervals this week. Review should be quick.

I think we can consider preliminary evaluations complete; we'll run more and shore up evaluation infrastructure after break.

@LeeTL1220 Following our discussion about evaluation tools, I added VCF output for the somatic pipeline as a TODO. Hopefully I can have some basic output by release, if not shortly thereafter.

@LeeTL1220
Copy link
Contributor

LeeTL1220 commented Dec 20, 2017 via email

@MartonKN
Copy link
Contributor

MartonKN commented Dec 22, 2017 via email

@samuelklee
Copy link
Contributor Author

@MartonKN I've labeled the update of the caller as a "reach", so I'm not expecting that it gets done before release.

However, I expect that the tutorial data should be updated well before release. The tutorial data runs quickly (~1 hr for coverage collection, which is mostly limited by the slowest samples or cloud preemptions, and then ~minutes once collection has been call cached), so we should have plenty of time.

Whether or not the actual tutorial itself will be ready depends on whether @sooheelee has available bandwidth and if it is a high priority for comms.

@samuelklee
Copy link
Contributor Author

Going to close this out and spin off new issues.

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

No branches or pull requests

5 participants