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

we need a smart solution for wrappers #6

Open
meren opened this issue Aug 27, 2017 · 2 comments
Open

we need a smart solution for wrappers #6

meren opened this issue Aug 27, 2017 · 2 comments

Comments

@meren
Copy link
Member

meren commented Aug 27, 2017

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:
@ShaiberAlon
Copy link
Contributor

ShaiberAlon commented Aug 27, 2017 via email

@meren
Copy link
Member Author

meren commented Aug 27, 2017

Hey Alon,

I just wanted to leave something behind so we remember it later :) What are YOU doing here!?

But shouldn't we aspire to use the official snakemake wrapper repository?

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.

meren added a commit that referenced this issue Aug 27, 2017
Hopefully this will not stay long.
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

No branches or pull requests

2 participants