Versions Compared

Old Version 27

changes.mady.by.user Matthew Manoussakis

Saved on

compared with

New Version Current

changes.mady.by.user Matthew Manoussakis

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Confirmed.

Table of Contents

How is the TIGGE data organised in MARS?

Info

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

  • type of level 
    •  date
      •  time
        • steps, origins (ie Centres), membersparameters, parameters (same tape file (star))  

Best practise to iterate over all dates and all times for for a particular level type (eg Pressure levels)

Info

(lightbulb) The idea is to request as much data as possible from the same tape file (star). 

  The best approach is to iterate over the dates and for each date iterate over the times. (warning) At this point you may wish to  check TIGGE availability.

...

Info
  • The objective of this example is to demonstrate how to iterate efficiently over some dates (eg '2014-10-01' and '2014-11-01')  two requests  for 'perturbed forecast', 'pressure' and 'sfc' level, for TIGGE, ECMWF Center.
  • It can be used as a starting point,however you need to   please keep in mind that you have to adapt it to your needseg to set the keyword, values according to your requirements ('param', 'levtype', 'step' etc).
  • In this way you can extend these requests to download more data or a longer period of TIGGE.

(thumbs up) Keep in mind that the The most efficient way to organise your requests is per dates and times

ie select a set of 'dates' and 'times' and add  the 'steps', 'origins', 'levels' and 'parameters' that you need.

(thumbs down)   It is not efficient to organise your requests per parameter, per  origin  or per step. (eg to submit a different request per parameter or per origin for a list of dates)

...

Info