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

snakemake-tibanna run not finding rule #110

Open
SooLee opened this issue Nov 14, 2019 · 3 comments
Open

snakemake-tibanna run not finding rule #110

SooLee opened this issue Nov 14, 2019 · 3 comments

Comments

@SooLee
Copy link
Contributor

SooLee commented Nov 14, 2019

@johanneskoester Do you mind taking a quick look at this issue? You may find the problem more easily. 4dn-dcic/tibanna#256

@sengoku93
Copy link

Hi @johanneskoester ,

I have posted several comments in 4dn-dcic/tibanna#256. Please let me know if you have any suggestions. Thank you!

Best,

@rvalieris
Copy link
Contributor

I just ran into the same problem, it looks like the snakemake target includes the S3 bucket as a prefix but the Snakefile does not have this prefix, so snakemake cant figure it out which rules produces this output.

example:
rule a: output: a.txt

ends up being submitted to tibanna as snakemake $S3_BUCKET/a.txt

but there's no rule that produces $S3_BUCKET/a.txt

@rvalieris
Copy link
Contributor

rvalieris commented Dec 21, 2019

I think I figured out.
there are 2 issues that can cause this rule not found error.

First, is that I think snakemake is assuming a bucket subdir is always present. if I try to use --default-remote-prefix=BUCKET it gives the error, but with --default-remote-prefix=BUCKET/dir it works.

Second, is that you can't mix rules that depend on the default prefix with rules that use explict S3.remote, that is you can either write:
rule a: output: "a.txt"; rule b: input: "a.txt" or
rule a: output: S3.remote("BUCKET/dir/a.txt"); rule b: input: S3.remote("BUCKET/dir/a.txt")
but you can't mix both styles, which is a bummer because rule all downloads the inputs to the local host if you are using the default prefix.
also I rather not use S3.remote at all to try to leave the pipeline as generic as possible.

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

3 participants