-
Notifications
You must be signed in to change notification settings - Fork 592
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
Comments
@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. |
@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. |
VCF output can be a reach for the release.
…On Wed, Dec 20, 2017 at 1:44 PM, samuelklee ***@***.***> wrote:
@asmirnov239 <https://github.com/asmirnov239> @MartonKN
<https://github.com/martonkn> @mbabadi <https://github.com/mbabadi> Note
the remaining TODOs. Let's be in a position where we can get all
gCNV-related branches merged shortly after @mbabadi
<https://github.com/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 <https://github.com/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.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3826 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACDXk02sFz6dsTAaLaJ3gzcMLWzbFAJGks5tCVWKgaJpZM4Qcfhw>
.
--
Lee Lichtenstein
Broad Institute
75 Ames Street, Room 8011A
Cambridge, MA 02142
617 714 8632
|
Hi Sam,
updating ReCapSegCaller with the new version and updating the tutorial data
is assigned to me as a task. But as far as I understand those tasks will
not need to be ready by the release. Could you confirm it?
Happy holidays,
Marton
…On Wed, Nov 29, 2017 at 4:08 PM, samuelklee ***@***.***> wrote:
Assigned #3826 <#3826> to
@MartonKN <https://github.com/martonkn>.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#3826 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGPkHrgsag4Wro95TToAuawWDdtzSxp4ks5s7cfKgaJpZM4Qcfhw>
.
--
Marton Kanasz-Nagy
Physics Department, Harvard University
17 Oxford Street, Cambridge, MA 02138
[email protected]
|
@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. |
Going to close this out and spin off new issues. |
Legacy pipeline (note, the following should only be done after final ModelSegments PR is in):
Add deprecated/legacy tag to legacy pipeline tools. (SL, PR issued by 12/1 EDIT: need further input from @vdauwera )Update docs/arguments (w/ Comms, see All hands on deck: tool doc updates #3853). This will follow deletion of prototype tools. (all, PR issued by 12/15)(Reach) Collect all legacy code in a new package.ModelSegments pipeline:
Write MultidimensionalKernelSegmenterUnitTest.(SL, punting, filed Add a few more tests to ModelSegments pipeline. #3916)Write ModelSegmentsIntegrationTest.(SL, punting, filed Add a few more tests to ModelSegments pipeline. #3916)gCNV pipeline:
Miscellaneous:
The text was updated successfully, but these errors were encountered: