...
The so called tigge_check tool is a part of GRIB-API package. It should be used to validate all GRIB2 files prepared for UERRA (the option -u). The tool is checking all encoding details so that only fully compliant UERRA files following exactly required definitions would pass. It can check also allowed value ranges for each parameter if used with the option -v. These ranges have not been fully defined for all UERRA parameters yet e.g. for radiation fluxes. Sometimes warnings about values exceeding expected limits do not mean error in the checked data but only model specific correct values.
Warning | ||
---|---|---|
| ||
During the development phase there will be always the latest version of tigge_check tuned on the latest full sample data from providers available on ecgate: /tmp/marm/uerra/bin/tigge_check After the end of the development phase (when full samples for more days/weeks are available from all expected models) that last version of tigge_check will be added to the next closest official GRIB-API release. |
Examples of tigge_check usage:
...
*disregard data values in this grib (some step/level values were created artificially as real data has not been available yet)
Examples of encoding for various parameter validity types
Instantaneous
This example describes an instantaneous field valid on 20120103 00Z from a forecast starting on 20120101 00Z (time step=48 hours) .
- In bold, the values are fixed. They are meant to be used by all partners
- In green, these are the values for the example.
Time ( instantaneous ) | ||||
---|---|---|---|---|
Start of forecast ( section 1 ) | ||||
Octets | values | Meaning of values | Grib_api values | |
12 | Significance of Reference Time | 1 | Start of forecast | |
13-14 | Year (four digits) | 2012 | year of start of forecast |
dataDate=20120101 dataTime=0 |
15 | Month | 01 | month of start of forecast | |
16 | Day | 01 | day of start of forecast | |
17 | Hour | 00 | hour of start of forecast | |
section 4 e.g. template 4.1 | ||||
18 | Indicator of unit of time range | 1 | Hour | |
19-22 | Forecast time | 48 | Forecast step | stepType=instant, step=48 |
Accumulations
This example represents a 54 hour accumulation of a field produced by a forecast started on 20120101 00Z.
- In bold, the values are fixed. They are meant to be used by all partners
- In green, these are the values for the example.
Time ( accumulated ) | ||||
---|---|---|---|---|
Start of forecast ( section 1 ) | ||||
Octets | Values | Meaning of values | Grib_api key | |
12 | Significance of Reference Time | 1 | Start of forecast | |
13-14 | Year (four digits) | 2012 | year of start of forecast | dataDate=20120101 dataTime=0 |
15 | Month | 01 | month of start of forecast | |
16 | Day | 01 | day of start of forecast | |
17 | Hour | 00 | hour of start of forecast | |
Accumulation ( section 4 e.g. template 4.11 ) | ||||
18 | Indicator of unit of time range | 1 | Hour | |
19-22 | Forecast time | 0 | Accumulation starts at step=0 | startStep=0 |
38-39 | year of end of overall time interval | 2012 |
End of accumulated period, 20120103 06Z |
endStep=54
|
40 | month of end of overall time interval | 01 | ||
41 | day of end of overall time interval | 03 | ||
42 | hour of end of overall time interval | 06 | ||
45 | number of time ranges | 1 | Only one type of time statistics used (accumulation) | |
46-49 | total number of data values missing in statistical process | 0 | ||
50 | Statistical process used to calculate the processed field from the field at each time increment during the time range | 1 | Accumulation | stepType=accum |
51 | Type of time increment between successive fields used in the statistical processing | 2 | Successive times processed have same start time of forecast, forecast time is incremented | |
52 | Indicator of unit of time for time range over which statistical processing is done | 1 | Hour | |
53-56 | Length of the time range over which statistical processing is done, in units defined by the previous octet | 54 |
| |
57 | Indicator of unit of time for the increment between the successive fields used | 255 | Missing | |
58-61 | Time increment between successive fields, in units defined by the previous octet | 0 | 0 |
Maximum since the previous post-processing
This example represents a maximum since the previous post-processing of a field valid on 20120103 00Z produced by a forecast started on 20120101 00Z . In this example, the maximum is the 6-hourly maximum in the time interval: steps 42 to 48.
- In bold, the values are fixed. They are meant to be used by all partners
- In green, these are the values for the example.
Time (Maximum over the last 6 hours ) | ||||
---|---|---|---|---|
Start of forecast ( section 1 ) | ||||
Octets | values | Meaning of values | Grib_api keys | |
12 | Significance of Reference Time | 1 | Start of forecast | |
13-14 | Year (four digits) | 2012 | year of start of forecast |
dataDate=20120101 dataTime=0 |
15 | Month | 01 | month of start of forecast | |
16 | Day | 01 | day of start of forecast | |
17 | Hour | 00 | hour of start of forecast | |
Maximum ( section 4 e.g. Template 4.11) | ||||
18 | Indicator of unit of time range | 1 | Hour | |
19-22 | Forecast time | 42 | Step at the beginning of the 6-hourly interval | startStep=42 |
38-39 | year of end of overall time interval | 2012 |
End of maximum period |
endStep=48 |
40 | month of end of overall time interval | 01 | ||
41 | day of end of overall time interval | 03 | ||
42 | hour of end of overall time interval | 00 | ||
45 | number of time ranges | 1 | Only one time statistics applied (maximum) | |
46-49 | total number of data values missing in statistical process | 0 | ||
50 | Statistical process used to calculate the processed field from the field at each time increment during the time range | 2 | Maximum | stepType=max |
51 | Type of time increment between successive fields used in the statistical processing | 2 | Successive times processed have same start time of forecast, forecast time is incremented | |
52 | Indicator of unit of time for time range over which statistical processing is done | 1 | Hour | indicatorOfUnitForTimeRange=1 |
53-56 | Length of the time range over which statistical processing is done, in units defined by the previous octet | 6 | 6-hourly maximum | lengthOfTimeRange=6 |
57 | Indicator of unit of time for the increment between the successive fields used | 1 | Hour | indicatorOfUnitForTimeIncrement=1 |
58-61 | Time increment between successive fields, in units defined by the previous octet | 0 | Maximum computed continuously in the 6 hourly interval | timeIncrement=0 |
Minimum since the previous post-processing
This example represents a minimum since the previous post-processing of a field valid on 20120103 00Z produced by a forecast started on 20120101 00Z . In this example, the minimum is the 6-hourly minimum in the time interval: steps 42 to 48.
- In bold, the values are fixed. They are meant to be used by all partners
- In green, these are the values for the example.
Time (Minimum over the last 6 hours ) | ||||
---|---|---|---|---|
Start of re-forecast ( section 1 ) | ||||
Octets | Fixed | Meaning of values | Grib_api keys | |
12 | Significance of Reference Time | 1 | Start of forecast | |
13-14 | Year (four digits) | 2012 | year of start of forecast |
dataDate=20120101 dataTime=0 |
15 | Month | 01 | month of start of forecast | |
16 | Day | 01 | day of start of forecast | |
17 | Hour | 00 | hour of start of forecast | |
Minimum ( section 4 e.g. Template 4.11) | ||||
18 | Indicator of unit of time range | 1 | Hour | |
19-22 | Forecast time | 42 | Step at the beginning of the 6-hourly interval | startStep=42 |
45-46 | year of end of overall time interval | 2012 |
End of minimum period |
endStep=48 |
47 | month of end of overall time interval | 01 | ||
48 | day of end of overall time interval | 03 | ||
49 | hour of end of overall time interval | 00 | ||
52 | number of time ranges | 1 | Only one time statistics applied (minimum) | |
53-56 | total number of data values missing in statistical process | 0 | ||
57 | Statistical process used to calculate the processed field from the field at each time increment during the time range | 3 | Minimum | stepType=min |
58 | Type of time increment between successive fields used in the statistical processing | 2 | Successive times processed have same start time of forecast, forecast time is incremented | |
59 | Indicator of unit of time for time range over which statistical processing is done | 1 | Hour | indicatorOfUnitForTimeRange=1 |
60-63 | Length of the time range over which statistical processing is done, in units defined by the previous octet | 6 | 6-hourly minimum | lengthOfTimeRange=6 |
64 | Indicator of unit of time for the increment between the successive fields used | 1 | Hour | indicatorOfUnitForTimeIncrement=1 |
65-68 | Time increment between successive fields, in units defined by the previous octet | 0 | Minimum computed continuously in the 6 hourly interval | timeIncrement=0 |