-
Notifications
You must be signed in to change notification settings - Fork 27
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
add workflow to download multiple SRA accessions to multiple bams: fetch_multiple_sra_to_bams #537
Open
tomkinsc
wants to merge
12
commits into
master
Choose a base branch
from
ct-pluralize-fetch-sra-to-bam
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…tch_multiple_sra_to_bams add workflow to download multiple SRA accessions to multiple bams: fetch_multiple_sra_to_bams; this is useful in the event a sample is associated with multiple sequencing runs (i.e. more than one SRR###). It also adjusts the Fetch_SRA_to_BAM task to find metadata for the requested run, in the event multi-run metadata is returned for a given accession
…) function not available until WDL >= 1.1) name the output tsv file using the first specified ID since we are operating under WDL 1.0 (the `sep()` function is not available to join arrays of strings until WDL >= 1.1, and `~{sep="_" variable}` seemingly does not work outside a command block)
…dinstitute/viral-pipelines into ct-pluralize-fetch-sra-to-bam
dpark01
reviewed
May 4, 2024
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks -- since I missed the use case motivating this I just have some questions:
- Would it be useful to emit a merged bam
File
output at the workflow level (either instead of or in addition to theArray[File]
, again depending on the use case motivating this)? - I might feel better if we threw in a check / assertion that there is one and only one unique
biosample_accession
value across all the results. If that's not in conflict with the use case, maybe we can do that at the end of the workflow? - And if we can assume that, it might also be nice if the workflow could emit an output like
Map[String,String] biosample_metadata
(which of course should be identical for all elements of the scatter so this just presents the deduplicated map). This would just contain the keys that start withsample_
but not the other ones that are tied to the SRA entry.
try googleLegacyMachineSelection to set GCP machineType, per broadinstitute/cromwell@7fa57a0
ask for valid storage for N2 https://cloud.google.com/compute/docs/disks/local-ssd#choose_number_local_ssds
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
add workflow to download multiple SRA accessions to multiple bams:
fetch_multiple_sra_to_bams
This is useful in the event a sample is associated with multiple sequencing runs (i.e. more than one SRR###). It also adjusts the
Fetch_SRA_to_BAM task
to find metadata for the requested run in the event multi-run metadata is returned for a given accession.