...
MARS can be called with the command line options listed in table 2the table below. Most of these options are particularly useful when problems arise.
| 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 a user suspects 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 MARS Analysts 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, see section 6.5 |
| GRIB_API_DEBUG | If set to 1, it will enable debug level logging messages to be displayed by the library. |
| JDCNDBG | if set to 1, debug information for interpolation will be generated (values 2, 3 ... give progressively more detailed diagnostics) |
...