Page History

In general it is organised, as a huge tree, with the indentation below, showing different levels down that tree:

• centre (CMA, ECMWF, NCEP, JMA, ...)
  • realtime or reforecast
    •  type of data (control forecast or perturbed forecast)
      • type of level (single level or pressure level or potential  temperature)
        • ModelVersionDate (2014-05-01 or ...)
          
          • HindcastDates (2014-01-01 or 2014-01-02 or 2014-01-03, ...)
            •  time-steps
              • members (for perturbed forecast)
                • levels (for pl or pt)
                  • parameters

The idea is to request as much data as possible from the same tape file, all time-steps, all members, all parameters for a type of level, a type, a HindcastDate

for HindcastYear in HindcastYears
    for HindcastMonth in HindcastYearHindcastMonths        
        for HindcastDay in HindcastMonthHindcastDays             
            HindcastDate = HindcastYear-HindcastMonth-HindcastDaysHindcastDay               
                S2S-request(HindcastDate)

for HindcastYear from 2010 to 2014    
    for HindcastMonth in 04, 06        
        for HindcastDay in HindcastMonthHindcastDays             
            HindcastDate = HindcastYear-HindcastMonth-HindcastDay             
                S2S-request(HindcastDate) (see below an example)

#!/usr/bin/env python
from ecmwfapi import ECMWFDataServer
server = ECMWFDataServer()
server.retrieve({
    "class": "s2",
    "dataset": "s2s",
    "date": ModelVersionDate, (ie "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",
})