You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

This page is under construction!


What is the objective of this page?

The objective:

To help users to improve S2S CMA MARS requests performance.

(lightbulb) 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 general it is organised, as a huge tree, with the indentation below, showing different levels down that tree:

  • centre (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)
          • Hdates (2015-01-01 or 2015-01-05 or 2015-01-08, ...)
            •  time-steps
              • members (for perturbed forecast)
                • levels (for pl or pt)
                  • parameters


(lightbulb) The idea is to have in the same tape file, all time-steps, all members, all parameters for a type of level, a type, a Hdate

What would be the natural way to group requests?

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

(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 Hdates in one go, since the overall request will not be so big.

 What is the best approach to loop over several Hdates  for a CMA request?

The main idea in brief:

for Hdate in Hdate-list
     your-s2S-request(Hdate)

An example to request Control forecast, pressure levels from 2010-03-01 to 2010-03-31

The main idea in brief:

for each Hdate from 2010-03-01 to 2010-03-31
call your-s2s-request(Hdate)

An example of  "your-API-S2S-request"

Retrieving  1 field (10m U wind) for all time steps

What is the best approach to get all Hdays for several Hyears ?

The main idea in brief:

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.

for Hyear in Hyears
for Hmonth in Hyear
for Hdays in Hmonth
Hdate = Hyear-Hmonth-Hday
                 your-s2S-request(Hdate)

What is the best approach to get all Hdays for several Hyears and Hmonths  and for several hindcasts ?

The main idea in brief:

for Hyear in Hyears 
for Hmonth in Hyear
for Hdays in Hmonth
             Hdate = Hyear-Hmonth-Hday
             your-S2S-request(Hdate)
 

An example to request Control forecast, sfc, for Hyears 2010-2014 for 2 Hmonths  (eg April and June)

The main idea in brief:

for each Hyear from 2010 to 2014
    for Hmonth in April, June
        for Hday in Hmonth
             Hdate = Hyear-Hmonth-Hday
             your-S2S-request(Hdate)



 



  • No labels