When using runxtb -p48 -C crest the script will correctly set the queuing system parameters and export the correct environment variables for xtb. However, crest will not pick those environment variables up and only run with 4 processors. Not sure where that setting is coming from, though.
Example when using crest directly (exactly as in the generated submission script):
$ crest coord
...
Estimated runtime for one MTD (9.0 ps) on a single thread: 7 min 46 sec
Estimated runtime for a batch of 14 MTDs on 4 threads: 31 min 4 sec
...
Example when using crest explicitly with the -T option:
$ crest coord -T 24
...
Estimated runtime for one MTD (9.0 ps) on a single thread: 17 min 30 sec
Estimated runtime for a batch of 14 MTDs on 24 threads: 17 min 30 sec
...
When using
runxtb -p48 -C crest
the script will correctly set the queuing system parameters and export the correct environment variables for xtb. However,crest
will not pick those environment variables up and only run with 4 processors. Not sure where that setting is coming from, though.Example when using crest directly (exactly as in the generated submission script):
Example when using crest explicitly with the
-T
option: