Versions Compared

Old Version 34

changes.mady.by.user Richard Mladek

Saved on

compared with

New Version Current

changes.mady.by.user Richard Mladek

Saved on

Key

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

Find in this page technical specification of the required input data and processing workflow.

Table of Contents

Parameters

  • Output type:  forecast

    • only one forecast product per centre is expected for verification - the best available one for the common inter-comparison

  • Output time: 00, 6, 12, 18 UTC (depending on availability)

  • Output frequency: between 1 and 6 hours (including step 0 encoded as forecast type as well)

    frequency: 
    • the model output steps should be
    between 1 and 12 hour
  • Output types:  forecasts and analysis
    • the shortest available
  • Wave parameters should be obtained from the full 2-D spectrum (we stress this fact as there seems to be some confusion about wave parameters' names and definitions even in the latest WMO GRIB2 code tables)


Atmospheric forcing:

nameunitsparamId*1shortName*1

Atmospheric forcing

 Nameunits

10 metre U wind componentm/s16510u
10 metre V wind componentm/s
Wave Fields:

Significant height of combined wind waves and swell

m
16610v
Wave fieldsMean wave directiondegree true140230mwd

Peak wave period

s
Mean zero-crossing wave periods

Mean wave direction

140221mp2
Peak wave periods140231pp1d
Significant height of combined wind waves and swellm140229swhdegree true
  • Follow the links for exact GRIB2 WMO compliant definitions

...

  • *1 valid in ECMWF's ecCodes only

Encoding

...

All details about the required input files including examples can be found here

...

data format can be found in the page Encoding details.

Sample data

  • Providers are asked to provide full sample data from one model run containing all expected parameters, steps, forecast types etc.
  • Naming convention for sample data:
    wave_<centre WMO origin>_<YYYYMMDDRR>_<prod/test>_fc.grib2
    prod/test ... production or test version of the data
    fc ... forecast (step 0 should be also encoded as of forecast type)
  • Merge all parameters from all steps for given model run and output type into one file:
    e.g. wave test forecasts from ECMWF on the 1st of September 2017, 12Z  => wave_ecmf_2017090112_test_fc.grib2
  • Put sample data on ecgate to a directory with reading permission
    • alternatively use any other downloadable location (e.g. google drive)

    • alternatively use this ftp:

      Show If
      special@anonymous


      Alert

      Log in to see ftp details



      Show If
      special@authenticated


      Code Block
      host: ftp.ecmwf.int 
user: observations 
passwd: observations2013 
directory: wave



  • The naming convention for future production data might change

Production data acquisition

  • The data will be pulled via ftp from an agreed server location at the data producer's site.
  • The ECMWF's acquisition system will be used for handling the production data exchange.
  • Participants are committed to guarantee a steady and reliable provision of their data and to communicate any relevant changes.

...

  • .
  • The support mailing list on provider's side will be required to allow smooth communication related to common production issues in the future.

Contact

Show If
special@authenticated

Contact Richard Mladek for any further details, sample data exchange etc.


Show If
special@anonymous

Contact Richard Mladek for any further details, sample data exchange etc.