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

TSPS-183 Beagle imputation hg38 wdl and associated support wdls #1333

Open
wants to merge 94 commits into
base: develop
Choose a base branch
from

Conversation

mmorgantaylor
Copy link
Member

@mmorgantaylor mmorgantaylor commented Jul 15, 2024

Description

We are adding a new WDL, ImputationBeagle.wdl, that performs array imputation using the Beagle tool instead of minimac4, which is used by the existing Imputation.wdl.

Supporting PR in warp-tools for the Beagle docker: broadinstitute/warp-tools#114

Jira ticket: https://broadworkbench.atlassian.net/browse/TSPS-222


Checklist

If you can answer "yes" to the following items, please add a checkmark next to the appropriate checklist item(s) and notify our WARP documentation team by tagging either @ekiernan or @kayleemathews in a comment on this PR.

  • Did you add inputs, outputs, or tasks to a workflow?
  • Did you modify, delete or move: file paths, file names, input names, output names, or task names?
  • If you made a changelog update, did you update the pipeline version number?

@dsde-jenkins
Copy link
Collaborator

Can one of the admins verify this patch?

Copy link

Remember to squash merge!

This comment was marked as outdated.

This comment was marked as outdated.

Copy link

Remember to squash merge!

This comment was marked as outdated.

This comment was marked as outdated.

Copy link

Remember to squash merge!

This comment was marked as outdated.

This comment was marked as outdated.

@jessicaway
Copy link
Member

@mmorgantaylor is this still relevant?

@mmorgantaylor
Copy link
Member Author

@jessicaway yes this is our working branch for beagle imputation for the imputation service. cc @jsotobroad. Jess, would it be helpful for us to squash and rebase off of develop?

@jessicaway
Copy link
Member

OK, no problem! Whatever works best is fine. We were just cleaning up PRs and thought we would check in. I don't think we have touched imputation much recently, so I don't anticipate any conflicts

@mmorgantaylor mmorgantaylor force-pushed the TSPS-183_mma_beagle_imputation_hg38 branch from 79d3510 to eaeabdc Compare February 13, 2025 21:44
Copy link

Remember to squash merge!

This comment was marked as outdated.

This comment was marked as outdated.

@mmorgantaylor mmorgantaylor force-pushed the TSPS-183_mma_beagle_imputation_hg38 branch from 4f107d0 to 0a302fe Compare February 18, 2025 21:40
Copy link

Remember to squash merge!

This comment was marked as outdated.

This comment was marked as outdated.

@mmorgantaylor mmorgantaylor force-pushed the TSPS-183_mma_beagle_imputation_hg38 branch from 0a302fe to 6eb5bfc Compare February 19, 2025 21:56
Copy link

Remember to squash merge!

This comment was marked as outdated.

This comment was marked as outdated.

Copy link

Remember to squash merge!

Copy link

🔍Changelog Validation Results:

Comparing changelogs for pipelines that differ from the versions on 'origin/develop':
All changelog files are valid for this release.

Copy link

🔍Version Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

Copy link

Remember to squash merge!

Copy link

🔍Changelog Validation Results:

Comparing changelogs for pipelines that differ from the versions on 'origin/develop':
All changelog files are valid for this release.

Copy link

🔍Version Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

Copy link

Remember to squash merge!

Copy link

🔍Version Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

Copy link

🔍Changelog Validation Results:

Comparing changelogs for pipelines that differ from the versions on 'origin/develop':
All changelog files are valid for this release.

Copy link

Remember to squash merge!

Copy link

🔍Version Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

Copy link

🔍Changelog Validation Results:

Comparing changelogs for pipelines that differ from the versions on 'origin/develop':
All changelog files are valid for this release.

# 1.0.0
2025-02-24 (Date of Last Commit)

* * Initial public release of the ImputationBeagle pipeline.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* * Initial public release of the ImputationBeagle pipeline.
* Initial public release of the ImputationBeagle pipeline.

2025-02-24 (Date of Last Commit)

* * Initial public release of the ImputationBeagle pipeline.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change

@@ -0,0 +1,8 @@
{
"ImputationBeagle.multi_sample_vcf": "gs://broad-gotc-test-storage/imputation_beagle/scientific/vcfs/NA12878_10_duplicate.merged.cleaned.vcf.gz",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i see that this path points to a vcf.gz in a scientific directory, is that expected?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is - the way the scientific test differs from plumbing is that scientific runs on all chromosomes, and plumbing only runs on on a couple smaller chromosomes. the input data files themselves are the same. is that acceptable? i think the plumbing runs in just over an hour.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

that sounds great!

File ref_panel_bref3
File genetic_map_file
String basename
String chrom # not needed if ref file has been chunked and you are using the entire chunk
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

if these are not needed, should they be optional inputs?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ah these were comments from our collaborator when we were creating this WDL; they are indeed needed. I'll remove these comments since they're confusing.

Copy link

Remember to squash merge!

Copy link

🔍Version Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

Copy link

🔍Changelog Validation Results:

Comparing changelogs for pipelines that differ from the versions on 'origin/develop':
All changelog files are valid for this release.

Copy link

Remember to squash merge!

Copy link

🔍Changelog Validation Results:

Comparing changelogs for pipelines that differ from the versions on 'origin/develop':
All changelog files are valid for this release.

Copy link

🔍Version Validation Results:

Comparing versions and changelogs for pipelines that differ from the versions on 'origin/staging':
All WDLs and changelog files appear to be valid for this release.

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

Successfully merging this pull request may close these issues.

7 participants