Error when launching with executable on absolute path #63
Comments
jimboid
added a commit
that referenced
this issue
Aug 21, 2017
Fix for keyerror when no modules are given with an absolute path to a self compiled executable. Longbow will assume the user knows what they are doing if they are able to compile software. If modules are required such as intel etc then these should be given by the user in a job config file. This should have also fixed a related but slightly different and unreported bug with the use of environment variables. Had a user given an executable that didn't have a longbow plugin (ie a generic one) along with no modules, this would also have given an error, even though they might have configured the HPC user account with environment vars.
jimboid
added a commit
that referenced
this issue
Aug 21, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following traceback is generated when trying to launch own compiled gromacs
2017-08-04 13:58:40 - ERROR - longbow - '/work/c01/c01/jtg2/gmx/bin/mdrun_mpi' Traceback (most recent call last): File "/home/jimboid/.local/lib/python2.7/site-packages/longbow/corelibs/entrypoints.py", line 224, in launcher longbow(parameters) File "/home/jimboid/.local/lib/python2.7/site-packages/longbow/corelibs/entrypoints.py", line 266, in longbow jobs = configuration.processconfigs(parameters) File "/home/jimboid/.local/lib/python2.7/site-packages/longbow/corelibs/configuration.py", line 175, in processconfigs _processconfigsfinalinit(jobs) File "/home/jimboid/.local/lib/python2.7/site-packages/longbow/corelibs/configuration.py", line 444, in _processconfigsfinalinit jobs[job]["modules"] = modules[jobs[job]["executable"]] KeyError: '/work/c01/c01/jtg2/gmx/bin/mdrun_mpi'The text was updated successfully, but these errors were encountered: