...
- 1 file per month of Analysis (1 type of level, all times, levels, and parameters), for example, have a look in the catalogue MARS 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 in the catalogue MARS Catalogue for 1st February 2015 model level forecast at 12 UTC
- 1 file per Ensemble Forecast (1 type of level, all steps, members, levels and parameters), for example, have a look in the catalogue MARS Catalogue for 1st February 2015 pressure level 50 member ensemble at 12 UTC
Different projects have different needs, and therefore these rules may vary. You are encouraged to visit the MARS archive catalogueCatalogue to inspect how much related data a hypercube 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.
...
- 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 archiveMARS. - 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.
...
It is advisable to have a catalogue set of working requests and to re-use or modify them as needed.
...