...
| 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 Data 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:
...
retrieve action class=od stream = oper, identification of archive expver = 1, date = -1, date and time related type = analysis, levtype = model levels, levelist = 1/to/91, param = temperature, grid = 2.5/2.5, post-processing area = Europe, use = infrequent, execution control target = analysis.12 storage
Retrieve requests have to specify, at least, directives to identify the data and directives for storage of the retrieved data. The ones to identify fields can be found in the MARS Catalogue. Data manipulation (post-processing) directives and execution control directives are optional, depending on your needs.
...
read can be used to filter or manipulate data already retrieved into a file.
write is mainly used to save data from fieldsets, a temporary storage, into files, see keyword fieldsets.
...