MARS configuration and binaries
The MARS syntax relevant in this context is:
mars [-t] [-p|-n] <request_file>Configuration (prod and test)
The current deployment supports two distinct configurations: prod (default) and test.
Users can select test configuration by adding the -t flag to the mars command
MARS configurations are stored in:
<prefix>/mars/configs/[prod|test]The production MARS client configuration has 3 primary options, which are set via the database keyword:
database=fdb- The production local fdb for each EuroHPC
database=databridge- The production databridge remote fdb for each EuroHPC
database=databridge-fdb- The production databridge remote fdb for each EuroHPC but served with the FDB protocol.
| Expand | ||
|---|---|---|
| ||
In addition, the ClimateDT group have 2 additional FDBs on LUMI & MN5 which were used initially to compare the healpix grid output to both lat-lon and native grid output. The production MARS client configuration has 2 additional options for this:
|
Version of the binaries (prev, current and next)
Current deployment support versioning. MARS and FDB binaries are installed in
<prefix>/mars/versions/<version_number>MARS is configured to use three different versions: prod (default - current stable version) | prev (previous stable version) | next (candidate new version)
The user can select the desired version by adding a flag to the mars/fdb script
- <no flags>: mars script selects the default production version of the binaries
- -p (prev): mars script selects the previous version of the binaries
- -n (next): mars script selects the candidate version of the binaries
The flag -t can be combined with [-p | -n] flags.
Please see the Versions of MARS Client installed at EuroHPC sites for information on the installation.
The mapping between the previous/current/next production|test versions is specified in the script
<prefix>/mars/configs/[prod|test]/etc/versions.shFDB configuration and binaries
The fdb syntax can be found at the documentation here.
Configuration
The production FDB configuration files are stored in the top-level installation directory for each EuroHPC.
The production FDB configuration has 2 primary options, which are set via the FDB_HOME environment variable:
FDB_HOME=<prefix>/fdb- The production local fdb for each EuroHPC
FDB_HOME=<prefix>/databridge- The production databridge remote fdb for each EuroHPC
| Expand | ||
|---|---|---|
| ||
In addition, the ClimateDT group have 2 additional FDBs on LUMI & MN5 which were used initially to compare the healpix grid output to both lat-lon and native grid output. The production FDB configuration has 2 additional options for this:
|
Version of the binaries
Software components deployed:
- FDB (with multiple roots for each DE contract/project)
- C++ MARS Client configured to use the HPC FDB + the MARS Server/Data Bridge Remote FDB
MARS & FDB (binaries and configuration) installation prefix folder:
- LUMI:
<prefix> = /appl/local/destine - MN5:
<prefix> = /gpfs/projects/ehpc01/dte
- Leonardo:
<prefix> = /leonardo_work/DestE_devel_25
mars script is installed in:
<prefix>/binfdb and other binaries for the current version are installed in:
<prefix>/mars/versions/current/binFDB_HOME i.e. the directory containing the fdb configuration is:
<prefix>/fdbThus, the following should be added to your .bashrc file to use MARS/fdb on EuroHPC:
...
export PATH=<prefix>/bin:$PATH # MARS script...
export PATH=<prefix>/mars/versions/current/bin:$PATH # FDB & other tools...