Versions Compared

Old Version 74

changes.mady.by.user Matthew Manoussakis

Saved on

compared with

New Version 75

changes.mady.by.user Matthew Manoussakis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

Following the previous paragraph,  the natural way to group requests would be:
all parameters, all levels, all members, all time-steps for 1 hindcast date.

(warning) Note the following:

  1. 'all' means 'all' that the user wants. It doesn't have to be all parameters.
  2. If a user is interested only on z500,  he may request more hindcast dates in one go, since the overall request will not be so big.

Best practices:

To loop over several hindcastDates for a CMA request

...

Info
titleThe main idea in brief:

for hindcastDate in hindcastDateList (eg, 2010-03-01 to 2010-03-31)
     S2S-request(hindcastDate)

(lightbulb) You may wish to have a look on some CMA re-forecast examples or to visit the ECMWF Web API Home

To get all

...

hindcastDates for several hindcastYearsfor a CMA request

Info
titleThe main idea in brief:

(lightbulb) The best approach is to iterate over the hindcastYears. For each hindcastYear iterate over all the available hindcastMonths and for each hindcastMonth iterate over all the available hindcastDays.

(warning) At this point you may wish to check CMA availability and to view a CMA request

...