...
- 1 file per month of Analysis (1 type of level, all times, levels, and parameters), for example, have a look inthe in the catalogue for February 2015 model level analysis
- 1 file per Forecast (1 type of level, all steps, levels and parameters), for example, have a look at in the catalogue for 1st February 2006 2015 model level forecast at 12 UTC in the catalogue.
- 1 file per Ensemble Forecast (1 type of level, all steps, members, levels and parameters), for example, have a look in the catalogue for 1st February 2006 2015 pressure level 50 member ensemble at 12 UTC in the catalogue.
Different projects have different needs, and therefore these rules may vary. Users You are encouraged to visit the MARS archive catalogue in order to inspect how much related data an archive object contains. The description above is the rule, but resources available at certain times might cause to break it, e.g. 1 month of Analysis may be in 2 files because at that particular month the MARS system was short of disk space and data had to be written to tape earlier than desired.
...
Any requested data manipulation or post-processing is carried out by the MARS client, except in the case of a local Member State's client where data is first processed at ECMWF prior to its transmission over the network. The post-processing is carried out by a set of routines present in the EMOSLIB library. Please, refer to the Field interpolation software routines for in-depth details about such post-processing.
Sub-area extraction
Most of the data at ECMWF is global. A sub-area can be created using the area keyword by defining its latitude and longitude boundaries: North/West/South/East.
...
Users wanting to post-process at the full archived resolution can specify resol = av in the request. Note that high resolutions might need more resources to carry out post-processing.
...
MARS does not perform any semantic check on the request. A MARS request can be syntactically correct but may not describe any archived data. Common problems are:
- Data not
...
- found
Usually means the MARS directives do not specify archived data. - Expected xx, got
...
- yy
The server transferred some data and the client failed; usually the client expected more fields than were sent by the server. Either some data do not exist, are missing on the server or a syntactically correct request asked for a parameter which is not in the archive. - Inconsistency in field
...
- ordering
This error occurs when a server sends a field which does not correspond to the MARS request. Operational servers are not likely to deliver inconsistent data, but it may well happen in test environments.
If you get this kind of error when retrieving monthly means , then setting the day to 00 (DATE=YYYYMM00) will solve the problem.
System limits
Some system resource limits can be controlled by the user (consult the man pages of your shell if running in interactive mode or documentation about the software used for batch mode).
Error writing to file
It usually indicates the user has exceeded his/her quota on the filesystem holding the target file or that filesystem became full.
Memory allocation failed
It usually indicates MARS needs more memory than the available for user processes in order to execute a request.
CPU time limit
It usually indicates the MARS process has exceeded the CPU time limit. The kind of post-processing and the number of fields retrieved have a direct implication of the CPU time needed by MARS to satisfy a request.
...