Best practise to iterate over all hindcastDates of several hindcastYears for CMA
Info |
---|
At this point you may wish to check CMA availability and to view a CMA request |
Info |
---|
for hindcastYear in hindcastYears |
Web-API examples:
A CMA reforecast request for all the available hindcastDates
Info |
---|
Please note:
|
Code Block | ||
---|---|---|
| ||
#!/usr/bin/env python
import calendar
from ecmwfapi import ECMWFDataServer
server = ECMWFDataServer()
origin = "babj"
modelVersionDate = "2014-05-01"
def retrieve_cma_reforecast():
"""
A function to demonstrate how to iterate efficiently over all hindcastYears, hindcastMonths etc
for a particular cma_reforecast_request.
Change the variables below to adapt the iteration to your needs
"""
hindcastYearStart = 1994
hindcastYearEnd = 2014
hindcastMonthStart = 1
hindcastMonthEnd = 12
for hindcastYear in list(range(hindcastYearStart, hindcastYearEnd + 1)):
for hindcastMonth in list(range(hindcastMonthStart, hindcastMonthEnd + 1)):
numberOfDays = calendar.monthrange(hindcastYear, hindcastMonth)[1]
for hindcastDay in list(range(numberOfDays)):
hindcastDate = '%04d%02d%02d' % (
hindcastYear, hindcastMonth, hindcastDay + 1)
target = "%s%s.grb" % (origin, hindcastDate)
cma_reforecast_request(hindcastDate, target)
def cma_reforecast_request(hindcastDate, target):
"""
A CMA reforecast request. Change the keywords below to adapt it to your needs.
"""
server.retrieve({
"class": "s2",
"dataset": "s2s",
"date": modelVersionDate,
"expver": "prod",
"hdate": hindcastDate,
"levtype": "sfc",
"origin": origin,
"param": "165/166",
"step": "24/to/1440/by/24",
"stream": "enfh",
"target": target,
"time": "00",
"number": "1/2/3",
"type": "pf",
})
if __name__ == '__main__':
retrieve_cma_reforecast() |
Useful links
Info |
---|
Table of Contents
This page is under construction!
...
Info | ||
---|---|---|
| ||
A good understanding of the MARS efficiency issues is essential especially for users that are interested in downloading large amounts of data. The aim of this page is to help users to improve their MARS requests performance focusing in CMA reforecast MARS requests. |
How the S2S data is organised in general?
...
First you need to understand how the S2S data is organised in MARS.
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)
- dates (2015-01-01 or 2015-01-05 or 2015-01-08, ...)
- time-steps
- members (for perturbed forecast)
- levels (for pl or pt)
- parameters
- levels (for pl or pt)
- members (for perturbed forecast)
- time-steps
- dates (2015-01-01 or 2015-01-05 or 2015-01-08, ...)
- type of level (single level or pressure level or potential temperature)
- type of data (control forecast or perturbed forecast)
- realtime or reforecast
...
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 dates and hincast-dates for a CMA request?
Info | ||
---|---|---|
| ||
for date in date-list for hindcast in hindcast-list |
An example to request Control forecast, pressure levels, for years 2010-2014 for 2 months (eg April and June)
Info | ||
---|---|---|
| ||
for each year from 2010 to 2014 for months April, June |
...
title | The main idea in brief: |
---|
...
old below:
---------------
...
title | The objective: |
---|
...