This page covers use of the module command in the OSG computing environment.
Environment modules have historically been used in HPC environments to provide users with an easy way to access different versions of software and to access various libraries, compilers, and software (c.f. the wikipedia reference). OSG has implemented a version based on Lmod to provide the typical module commands on any site in the OSG. You can test workflows on the OSG Connect login node and then submit the same workflow without any changes.
Using modules on OSG Connect
$ module avail to see available software applications and libraries:
In order to load a module, you should run
$ module load [modulename].
Some modules require other modules to be loaded. If that occurs then you'll get an error message indicating this:
In addition, some modules such as the all-pkgs for python won't be available until the relevant packages are loaded.
To unload a package and remove it from the environment, use
$ module unload [modulename].
To see currently loaded modules, use
$ module list.
$module help will give you more detailed information.
Submit file changes
Not all resources available through OSG Connect support OASIS and distributed environment modules. In order to make sure that the jobs you submit run on resources that do support distributed environment modules, you will need to add the following condition to the requirements in your condor job submission file.
A list of currently installed software is available here.