We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hey, I start using snakmake workflows and modules.
My goal is to factorize a large snakemake pipeline in smaller modules that then might be recombined in new piplines.
I saw that sometimes you require many config variables e.g., in the dna-seq-short-read-circle-map or even more in the dna-seq-gatk-variant-calling
How exactly should one ensure that all the config variables are correctly defined when the module will be used in a new pipeline?
E.g. the template config is empty.
Is there a way to ensure updates to the config are also available in new pipelines?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hey, I start using snakmake workflows and modules.
My goal is to factorize a large snakemake pipeline in smaller modules that then might be recombined in new piplines.
I saw that sometimes you require many config variables e.g., in the dna-seq-short-read-circle-map or even more in the dna-seq-gatk-variant-calling
How exactly should one ensure that all the config variables are correctly defined when the module will be used in a new pipeline?
E.g. the template config is empty.
Is there a way to ensure updates to the config are also available in new pipelines?
The text was updated successfully, but these errors were encountered: