Support for "module load" in torque scripts

[GoogleCodeExporter]

It would be good for torque jobs to support the "module load" command, and for 
it to be mentioned in the online documentations.

Original issue reported on code.google.com by bjp...@unimelb.edu.au on 7 Feb 2012 at 6:43

[GoogleCodeExporter]

+1 on this, though not all PBS/Torque installs have environment modules (we 
added module support on our cluster at a later point).

Original comment by cjfiel...@gmail.com on 29 Sep 2013 at 7:05

[GoogleCodeExporter]

I usually deal with this by either putting 'module load' statements into my 
.bashrc file for ones that I want globally or into my actual commands to be 
executed.

Not saying this would be good to have, but I'm curious if there are cases where 
these workarounds don't work? If so I would prioritise this higher.

Original comment by ssade...@gmail.com on 30 Sep 2013 at 12:29

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

It would be great to be able to do this in the config for the pipeline.

Original comment by h.dash...@gmail.com on 30 Apr 2014 at 5:39

[GoogleCodeExporter]

This isn't a torque specific thing, the module command is from the "environment 
modules" package and is independent of even having a grid scheduler.

I'm not sure the pipeline inherits changes to the environment made by 
applications but you could just run the command as the first stage in your 
pipeline.

Original comment by gdeve...@gmail.com on 11 Oct 2014 at 5:21