The MARS syntax relevant in this context is:
mars [-t] [-p|-n] <request_file>
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 database=databridge database=databridge-fdb 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:
|
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
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.sh
The fdb syntax can be found at the documentation here.
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 FDB_HOME=<prefix>/databridgeIn 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:
|