This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
apps-dev [2018/11/22 14:06] bbosak@man.poznan.pl [The main ''vecma'' module] |
apps-dev [2018/11/22 14:10] bbosak@man.poznan.pl [The main VECMA module] |
||
---|---|---|---|
Line 12: | Line 12: | ||
==== The main VECMA module ==== | ==== The main VECMA module ==== | ||
- | In order to simplify usage of VECMA environment, the resources have set up the top-level module for VECMA. This module will configure the common settings for all VECMA participants. The ''vecma'' module should be available for users when they run a QCG job (also inside an interactive one), however, in case of regular queuing-system jobs, the ''$MODULEPATH'' won't be automatically updated, thus the module won't be visible. Therefore it is advised to add the appropriate command to users' .bashrc. In case of EAGLE cluster the line extending ''$MODULEPATH'' should look as follows: | + | In order to simplify usage of VECMA environment, the resources have set up the top-level module for VECMA. This module will configure the common settings for all VECMA participants. The ''vecma'' module should be available for users out-of-the-box when they run a QCG job (also interactive one), however, in case of regular jobs, started without QCG, the ''$MODULEPATH'' won't be automatically updated and the module won't be visible. Thus it is advised for users to add the command extending ''$MODULEPATH'' to their ''.bashrc'' files. In case of EAGLE cluster it will look as follows: |
''export MODULEPATH=$MODULEPATH:/home/plgrid-groups/plggvecma/.qcg-modules'' | ''export MODULEPATH=$MODULEPATH:/home/plgrid-groups/plggvecma/.qcg-modules'' |