-
Notifications
You must be signed in to change notification settings - Fork 4
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
we need a smart solution for wrappers #6
Comments
Meren, don't take this to think that I'm working ;-)
But shouldn't we aspire to use the official snakemake wrapper repository?
And then we don't need people to put the wrappers in a specific place.
On Aug 27, 2017 1:38 PM, "A. Murat Eren" <[email protected]> wrote:
I am all for wrappers, but currently we use them at one place, and we need
to copy the wrappers directory to a relative location to the snakemake
file. I think this is not very feasible, and we need to find a better way
to handle wrappers.
This is how I'm running things at the moment:
diff --git a/workflows/assembly-based-metagenomics-workflow/merenlab-metagenomics-pipeline.snakefile
b/workflows/assembly-based-metagenomics-workflow/merenlab-metagenomics-pipeline.snakefile
index 38b3b6c..fcd96d2 100644---
a/workflows/assembly-based-metagenomics-workflow/merenlab-metagenomics-pipeline.snakefile+++
b/workflows/assembly-based-metagenomics-workflow/merenlab-metagenomics-pipeline.snakefile@@
-450,10 +450,7 @@ rule reformat_fasta:
params: prefix = "{group}"
threads: T('reformat_fasta')
resources: nodes = T('reformat_fasta'),- wrapper:- #
Notice that path to wrapper is relative to the workdir (if you-
# want an absolute path, use 'file://' instead of 'file:')-
"file:wrappers/reformat-fasta"+ shell: "anvi-script-reformat-fasta
{input} -o {output.contigs} -r {output.report} --simplify-names
--prefix {params.prefix} >> {log} 2>&1"
if run_remove_human_dna_using_centrifuge:
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#6>, or mute the
thread
<https://github.com/notifications/unsubscribe-auth/AQ18dOItNs5nVqXyC7PSo2aD47tIj8yWks5scbeigaJpZM4PD4Vj>
.
|
Hey Alon, I just wanted to leave something behind so we remember it later :) What are YOU doing here!?
Absolutely. But this shouldn't stop us from testing and using our stuff effectively and without pain. We can find a way to make this process seamless. I.e, if a wrapper is in the official repository the code would use it from there, if not, the code would set some environmental variables to use them from whatever location on the disk we keep them. Having to copy a directory to run a snakemake file is what is not working :) I will ask @ozcan's opinion on this during the week. |
I am all for wrappers, but currently we use them at one place, and we need to copy the wrappers directory to a relative location to the snakemake file. I think this is not very feasible, and we need to find a better way to handle wrappers.
This is how I'm running things at the moment:
The text was updated successfully, but these errors were encountered: