Table of Contents
This page is under construction!
What is the objective of this page?
Info | ||
---|---|---|
| ||
To help users to improve S2S CMA MARS requests performance via the WebAPI A good understanding of the MARS efficiency issues is essential especially for users that are interested in downloading large amounts of data. |
How the S2S data is organised in general in MARS?
Info |
---|
In general it is organised, as a huge tree, with the indentation below, showing different levels down that tree:
|
What would be the natural way to group requests?
Info |
---|
Following the previous paragraph, the natural way to group requests would be: Note the following:
|
What is the best approach to loop over several HindcastDates for a CMA request?
Info | ||
---|---|---|
| ||
for HindcastDate in HindcastDate-list (eg, 2010-03-01 to 2010-03-31) |
What is the best approach to get all HindcastDays for several HindcastYears ?
The best approach is to iterate over the Hyears you wish. For each Hyear iterate over all Hmonths and for each Hmonth iterate over all its Hdays.
Info | ||
---|---|---|
| ||
for HindcastYear in HindcastYears S2S-request(HindcastDate) |
An example to request Control forecast, single level, for HindcastYears 2010 to 2014 for 2 HindcastMonths (eg April and June)
Info | ||
---|---|---|
| ||
for each HindcastYear from 2010 to 2014 for HindcastMonth in 04, 06 for HindcastDay in HindcastMonth HindcastDate = HindcastYear-HindcastMonth-HindcastDay S2S-request(HindcastDate) (see below an example) |
An S2S-request example
Code Block | ||
---|---|---|
| ||
#!/usr/bin/env python from ecmwfapi import ECMWFDataServer server = ECMWFDataServer() server.retrieve({ "class": "s2", "dataset": "s2s", "date": "2014-05-01", "expver": "prod", "hdate": HindcastDate, (ie the selected HindcastDate eg "2014-04-01"), "levtype": "sfc", "origin": "babj", "param": "165", "step": "0", "stream": "enfh", "target": "CHANGEME", "time": "00", "type": "cf", }) |