You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This option is used to tell snakemake the directory it should use when resolving relative file names in the workflow. Our workflows aren't using relative files, though. We are using absolute file names wherever possible.
When --directory is passed, Snakemake goes crazy when copying workflow files to AWS via Tibanna. On every new job it keeps going one level deeper, looking for config.json relative to output, then output/output, then output/output/output, etc. (This is when the --directory argument is $PWD/output.)
We should test our workflows without this option, both in cluster execution mode as well as local execution.
The text was updated successfully, but these errors were encountered:
We are passing
--directory
to snakemake:pigx-common/common/pigx-runner.in
Line 389 in 502f8ad
This option is used to tell snakemake the directory it should use when resolving relative file names in the workflow. Our workflows aren't using relative files, though. We are using absolute file names wherever possible.
When
--directory
is passed, Snakemake goes crazy when copying workflow files to AWS via Tibanna. On every new job it keeps going one level deeper, looking forconfig.json
relative tooutput
, thenoutput/output
, thenoutput/output/output
, etc. (This is when the--directory
argument is$PWD/output
.)We should test our workflows without this option, both in cluster execution mode as well as local execution.
The text was updated successfully, but these errors were encountered: