| Table of Contents |
|---|
:MARS command
The mars command can accept a request file as a parameter or read the MARS request from standard input.
...
| MARS command line options | |
| Option | Meaning |
| -d | switches debug information on (same as MARS_DEBUG=1) |
| -h | prints help information |
| -p | to use the previous MARS binary. If you suspect a new version of MARS may yield different results (including errors, crashing, etc...) this is the first thing to try. If the previous version of MARS works, then contact the CallDesk to report the problem you've found. |
In addition, the behaviour of MARS can be changed via various environment variables:
...
| MARS environment variables | |
| Environment variable | Usage |
| MARS_COMPUTE_FLAG | if set to 0, the model identification number is preserved. When using compute, GRIB headers of resulting fields are changed to reflect fields have been created by MARS. In particular, model identification number is set to 255. With this env. variable, the model identification of the first field is copied onto the result. |
| MARS_DEBUG | if set to a value different from 0, additional output will be generated |
| MARS_MULTITARGET_STRICT_FORMAT | if set to 1, 'consistent' file naming will be applied for multi targets, seeData storage keywords |
| GRIB_API_DEBUG | If set to 1, it will enable debug level logging messages to be displayed by the library. |
| MIR_DEBUG | If MIR_DEBUG and MARS_DEBUG are set to 1, debug information for interpolation with MIR will be generated. |
| JDCNDBG | if set to 1, debug information for interpolation with EMOSLIB will be generated (values 2, 3 ... give progressively more detailed diagnostics) |
Request syntax
A MARS request is the way to specify an action on a set of fields or observations. The directives specified in a MARS request have the following syntax:
...