-
Notifications
You must be signed in to change notification settings - Fork 113
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
Simplify hello-gatk #364
base: master
Are you sure you want to change the base?
Simplify hello-gatk #364
Conversation
… methods. This should make it quicker and cleaner to use as training material.
… more approachable methods.
✅ Deploy Preview for nextflow-training ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
params.reads_bam = "./data/samplesheet.csv" | ||
|
||
// Accessory files | ||
params.genome_reference = "${projectDir}/data/ref/ref.fasta" | ||
params.genome_reference_index = "${projectDir}/data/ref/ref.fasta.fai" | ||
params.genome_reference_dict = "${projectDir}/data/ref/ref.dict" | ||
params.calling_intervals = "${projectDir}/data/intervals.list" | ||
params.reference = "./data/ref/ref.fasta" | ||
params.reference_index = "./data/ref/ref.fasta.fai" | ||
params.reference_dict = "./data/ref/ref.dict" | ||
params.calling_intervals = "./data/intervals.list" |
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.
workflow.projectDir
doesn't exist in the configuration, so we just use a relative path.
We could wrap it in closures but that makes it complicated.
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.
From a quick look, it seems cool! It'd be good if someone else could try out the new version of this training.
Co-authored-by: Marcel Ribeiro-Dantas <[email protected]>
A small side benefit I noticed while testing, because the two containers share most of the layers downloading them is much more efficient. |
@adamrtalbot Just a heads up that we'd like to merge this for our training in SF tomorrow. |
I'm happy with it, if you are hit merge. Currently needs an approval 😉 |
I've reviewed in more detail and I feel like there's a couple of things that are a bit of a jump, so I'm making an intermediate version with most but not all of the changes |
I've just tried removing the reference channels and it still works. From:
to:
So let's do that. In addition, we should remove |
Based on Adam's branch at #364
* Simplified version of Hello-GATK Based on Adam's branch at #364 * Intermediate scripts by section * starter script for hello-gatk * Replace bams with Adam's * Add Adam's smaller reference files * Delete hello-nextflow/data/samplesheet.csv No longer needed * Delete hello-nextflow/data/ref.tar.gz replaced by Adam's ref files * Delete hello-nextflow/data/intervals.list reolaced by Adam's BED file * Move ref under data (oops) * convert fromPath().collect() to file() For accessory file inputs * Prettier fixes whitespace * addressing review - add note about working directory - remove collect mention which is no longer applicable and replace with informative statement
Most of the changes in here were made in my recent PR (thanks @adamrtalbot for your hard work!) so this is no longer going to be used, but I'm leaving it open for now in case there's anything else we want to pilfer from it. |
This PR simplifies the hello-gatk example.
collect
), which makes it more obvious what each step doesNegatives:
chr20:coordinateStart-coordinateEnd
) which is harder to develop for usResolves #355