Each resource provides a dedicated environment for VECMA application teams and end-users. This webpage provides information how to use this environment.
Each resource provides a dedicated directory and disk space for VECMA. This directory is shared among all VECMA participants.
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:
vecma module could be loaded with the following command:
module load vecma
When loaded, the module set up the
$VECMA_DIR environment variable that points to the shared directory.
The shared directory
$VECMA_DIR has the following structure:
| ||The directory for use by application providers|
| ||The directory for application App1|
| ||The directory for application AppN …|
| ||Common stuff, possibly useful for more than one team|
| ||The directory for VECMA Environment Modules|
The modules created for the VECMA project follow the following scheme:
| ||The main module for the VECMA project. Will load basic settings|
| ||The module for a single application (e.g. App1)|
| ||The module for a common software item (e.g. Item1), possibly useful for many teams|