-
Notifications
You must be signed in to change notification settings - Fork 22
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
Specifying non-standard rule-specific cluster resource settings #25
Comments
Yes, it does need to be in the working directory sorry. There is no way of propagating information about the location of this file to the submitter (that I know of - happy to see a PR if you can do this). |
My guess would have been to use I can check whether this could work. If not, do you think that it's worth asking in the main Snakemake repository about it? |
I see. We could have it as an option when creating the template from cookiecutter. i.e. you put in the location to the config file, relative to the working directory? |
This would only work for a single specific working directory, wouldn't it? |
Correct. If |
As expected, using In [2]: import snakemake
In [3]: snakemake.workflow.srcdir('.')
---------------------------------------------------------------------------
NameError Traceback (most recent call last)
~/Library/Application Support/snakemake/lsf/lsf_submit.py in <module>
----> 1 snakemake.workflow.srcdir('.')
~/Library/Python/3.7/lib/python/site-packages/snakemake/workflow.py in srcdir(path)
1548 def srcdir(path):
1549 """Return the absolute path, relative to the source directory of the current Snakefile."""
-> 1550 if not workflow.included_stack:
1551 return None
1552 return os.path.join(os.path.dirname(workflow.included_stack[-1]), path)
NameError: name 'workflow' is not defined I have asked for a better solution in the main snakemake repository: snakemake/snakemake#424. |
Hello,
In order to specify e.g. a time limit (which can be needed to select an appropriate queue) for a certain rule, one needs to create
lsf.yaml
(see also #7 and #13). This file needs to be in the working directory of the pipeline.This can be difficult/slightly annoying to handle when
lsf.yaml
needs to be moved manually to the correct working directory before executing the pipeline is possible.Is there a better way of doing this that I am missing?
Or asked differently, what is the difference between standard and non-standard resources?
The text was updated successfully, but these errors were encountered: