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

more docs for somatic exome #872

Open
wants to merge 5 commits into
base: master
Choose a base branch
from
Open

more docs for somatic exome #872

wants to merge 5 commits into from

Conversation

zlskidmore
Copy link
Collaborator

@jasonwalker80 @jhundal can you +1 content

definitions/pipelines/somatic_exome.cwl Outdated Show resolved Hide resolved
@@ -124,13 +124,25 @@ inputs:
In general for a WES exome reagent bait_intervals and target_intervals are the same.
per_base_intervals:
type: ../types/labelled_file.yml#labelled_file[]
label: "per_base_intervals: yaml file specifying name and input for picard CollectHsMetrics"
doc: |
Optional input, redundant with bait_intervals, provides a way to name name the output file from running picard CollectHsMetrics. See ../types/labelled_file.yml for an example.
Copy link
Member

Choose a reason for hiding this comment

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

In subworkflows/hs_metrics.cwl, the CollectHsMetrics tool runs multiple times with different options. It's not just a different filename; it's a different mode of running!

Copy link
Member

Choose a reason for hiding this comment

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

@zlskidmore
Copy link
Collaborator Author

@tmooney Is this more what you had in mind, this is my understanding based on reading the cwl

@tmooney
Copy link
Member

tmooney commented Feb 4, 2020

@zlskidmore Yeah, something like that. I'd prefer to describe them as optional extra regions for further metric generation rather than "redundant". But at a minimum they are definitely not YAML files! 😄

Copy link
Member

@jasonwalker80 jasonwalker80 left a comment

Choose a reason for hiding this comment

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

Yeah, I would definitely change the wording from redundant. They are ideally not redundant at all, but rather specific regions of interest at a specific level, ex. base, target, etc.

@gschang
Copy link
Contributor

gschang commented Feb 12, 2020

Hi @zlskidmore, this input doc sounds relevant with my recent PR each other. I wrote a doc for exome alignment and QC.

#882

@zlskidmore
Copy link
Collaborator Author

yeah, I you suggesting we merge PRs?

@chrisamiller
Copy link
Collaborator

@zlskidmore - doing a little cleanup here. Did this get merged into gchang's PR, or otherwise included? Are there changes that still need to be made? I'm all for extra documentation - just wondering where this PR stands. Thanks!

@zlskidmore
Copy link
Collaborator Author

I don't think it was ever merged, perhaps @gschang can verify, I never did a merge though

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.

5 participants