...
The MARS syntax relevant in this context is:
mars [-t] [-p|-n] <request_file>Configuration (prod and test)
...
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:
...
Version of the binaries (prev, current and next)
Current The current deployment support supports versioning. MARS and FDB binaries are installed in:
<prefix>/mars/versions/<version_number>/bin
The MARS script calling the MARS client is installed in:
<prefix>/mars/binMARS 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 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
...
| 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
The current deployment supports versioning. FDB binaries are installed in
<prefix>/mars/versions/<version_number>/binFDB is configured to use a single current version. This is the supported production version and is installed in:
<prefix>/mars/versions/current/binOther versions of the FDB binaries can be used by specifying the appropriate version number.
Note however that only the production version will be supported in case of issues.