search

wmo-im / GRIB2

GRIB2
MIT License
24 stars 9 forks source link

Updates to facilitate needs in modelling for nuclear protection #173

Closed amilan17 closed 8 months ago

amilan17 commented 2 years ago

Initial request

updated 18 October 2023, v0.7

In nuclear protection activity cloud arrival and departure are useful output from atmospheric transport models. A reference date is then needed in order to arrive at the calendar date-time for each cell value. There is also a need for metadata related to what transport model that has been used, what entity that requested the results, the scenario basis for the results and what NWP data that was used.

We propose new templates "issue 173.a, issue 173.b, issue 173.c and issue 173.d" that are based on templates 4.76 to 4.79 for chemical constituents and the major differences are the following meta data extensions: • Reference date and time for the radionuclide release start. This date is used as reference for cloud arrival/departure fields. • Time when model simulation was executed. • Transport model used. • Requested by entity (CCT-11 table) • Scenario origin. • NWP data used. Additional descriptive tables are proposed for these metadata in tables 4.333 to 4335.

New templates:

New tables:

Updates

Requestor(s)

Tom Kralidis, ECCC Lennart Robertson, SMHI Yves Pelletier, ECCC

Stakeholder(s)

National Radiation Protection Agencies, National Meteorological Institutes, PDC ARGOS (Decision support system for crisis and emergency management).

Publication(s)

Manual on Codes (WMO-No. 306), Volume I.2, FM 92 GRIB

Expected impact of change

Medium

Collaborators

PDC ARGOS

References

Validation

Amendment details

**Update Code table 4.0: Product definition template number** Code figure | Meaning   -- | -- 173a |Analysis or forecast at a horizontal level or in a horizontal layer at a point in time for radionuclides 173b |Average, accumulation, extreme values or other statistically processed values at a horizontal level or in a horizontal layer in a continuous or non-continuous time interval for radionuclides 173c |Percentile forecasts at a horizontal level or in a horizontal layer at a point in time for radionuclides 173d |Probability forecasts at a horizontal level or in a horizontal layer at a point in time for radionuclides TBD-253|Reserved
New template 173a - Analysis or forecast at a horizontal level or in a horizontal layer at a point in time for radionuclides | Octet No. | Contents | | --------- | --------------------------------------------------------------------------- | | 10 | Parameter category: Radio nuclide constituents (see Code table 4.1) | | 11 | Parameter number (See Code table 4.2.0.18) | | 12-13 | Constituent type (See Code table 4.230.table) | | 14 | Source-Sink (See Code table 4.238.table) | | 15-16 | Transport model used (See Code table 4.333) | | 17-18 | Requested by entity (See Code table 4.334) | | 19-20 | Scenario origin (See Code table 4.335) | | 21-22 | NWP used (See Code table 4.336) | | 23-24 | Release start year | | 25 | Release start month | | 26 | Release start day | | 27 | Release start hour | | 28 | Release start minute | | 29- | Release start second | | 30-31 | Wall clock initial time of execution (Year) | | 32 | Wall clock initial time of execution (month) | | 33 | Wall clock initial time of execution (day) | | 34 | Wall clock initial time of execution (hour) | | 35 | Wall clock initial time of execution (minute) | | 36 | Wall clock initial time of execution (second) | | 37 | Type of generating process (See Code table 4.3) | | 38 | Background generating process identifier (defined by originating centre) | | 39 | Analysis or forecast generating process identifier (defined by originating centre) | | 40-41 | Hours of observational data cut-off after reference time | | 42 | Minutes of observational data cut-off after reference time | | 43 | Indicator of unit of time range (see Code table 4.4) | | 44-47 | Forecast time in units defined by octet 43 | | 48 | Type of first fixed surface (see Code table 4.5) | | 49 | Scale factor of first fixed surface | | 50-53 | Scaled value of first fixed surface | | 54 | Type of second fixed surface (see Code table 4.5) | | 55 | Scale factor of second fixed surface | | 56-59 | Scaled value of second fixed surface |
New template 173b - Average, accumulation, extreme values or other statistically processed values at a horizontal level or in a horizontal layer in a continuous or non-continuous time interval for radionuclides | Octet No. | Contents | | --------- | --------------------------------------------------------------------------- | | 10 | Parameter category: Radio nuclide constituents (see Code table 4.1) | | 11 | Parameter number (See Code table 4.2.0.18) | | 12-13 | Constituent type (See Code table 4.230.table) | | 14 | Source-Sink (See Code table 4.238.table) | | 15-16 | Transport model used (See Code table 4.333) | | 17-18 | Requested by entity (See Code table 4.334) | | 19-20 | Scenario origin (See Code table 4.335) | | 21-22 | NWP used (See Code table 4.336) | | 23-24 | Release start year | | 25 | Release start month | | 26 | Release start day | | 27 | Release start hour | | 28 | Release start minute | | 29- | Release start second | | 30-31 | Wall clock initial time of execution (Year) | | 32 | Wall clock initial time of execution (month) | | 33 | Wall clock initial time of execution (day) | | 34 | Wall clock initial time of execution (hour) | | 35 | Wall clock initial time of execution (minute) | | 36 | Wall clock initial time of execution (second) | | 37 | Type of generating process (See Code table 4.3) | | 38 | Background generating process identifier (defined by originating centre) | | 39 | Analysis or forecast generating process identifier (see Code ON388 Table A) | | 40-41 | Hours of observational data cut-off after reference time | | 42 | Minutes of observational data cut-off after reference time | | 43 | Indicator of unit of time range (see Code table 4.4) | | 44-47 | Forecast time in units defined by octet 43 | | 48 | Type of first fixed surface (see Code table 4.5) | | 49 | Scale factor of first fixed surface | | 50-53 | Scaled value of first fixed surface | | 54 | Type of second fixed surface (see Code table 4.5) | | 55 | Scale factor of second fixed surface | | 56-59 | Scaled value of second fixed surface | | 60 | Type of ensemble forecast (See code table 4.6.table) | | 61 | Perturbation Number | | 62 | Number of forecasts in ensemble |
New template 173c - Percentile forecasts at a horizontal level or in a horizontal layer at a point in time for radionuclides | Octet No. | Contents | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 10 | Parameter category: Radio nuclide constituents (see Code table 4.1) | | 11 | Parameter number (See Code table 4.2.0.18) | | 12-13 | Constituent type (See Code table 4.230.table) | | 14 | Source-Sink (See Code table 4.238.table) | | 15-16 | Transport model used (See Code table 4.333) | | 17-18 | Requested by entity (See Code table 4.334) | | 19-20 | Scenario origin (See Code table 4.335) | | 21-22 | NWP used (See Code table 4.336) | | 23-24 | Release start year | | 25 | Release start month | | 26 | Release start day | | 27 | Release start hour | | 28 | Release start minute | | 29 | Release start second | | 30-31 | Wall clock initial time of execution (Year) | | 32 | Wall clock initial time of execution (month) | | 33 | Wall clock initial time of execution (day) | | 34 | Wall clock initial time of execution (hour) | | 35 | Wall clock initial time of execution (minute) | | 36 | Wall clock initial time of execution (second) | | 37 | Type of generating process (See Code table 4.3) | | 38 | Background generating process identifier (defined by originating centre) | | 39 | Analysis or forecast generating process identifier (see Code ON388 Table A) | | 40-41 | Hours of observational data cut-off after reference time | | 42 | Minutes of observational data cut-off after reference time | | 43 | Indicator of unit of time range (see Code table 4.4) | | 44-47 | Forecast time in units defined by octet 43 | | 48 | Type of first fixed surface (see Code table 4.5) | | 49 | Scale factor of first fixed surface | | 50-53 | Scaled value of first fixed surface | | 54 | Type of second fixed surface (see Code table 4.5) | | 55 | Scale factor of second fixed surface | | 56-59 | Scaled value of second fixed surface | | 60-61 | Year of end of overall time interval | | 62 | Month of end of overall time interval | | 63 | Day of end of overall time interval | | 64 | Hour of end of overall time interval | | 65 | Minute of end overall time interval | | 66 | Second of end of overall time interval | | 67 | n ― number of time ranges specifications describing the time intervals used to calculate the statistically-processed field | | 68-71 | Total number of data values missing in the statistical process | | | 60 - 71 Specification of the outermost (or only) time range over which statistical processing is done | | 72 | Statistical process used to calculate the processed field from the field at each time increment during the time range
(see Code [Table 4.10](https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-10.shtml)) | | 73 | Type of time increment between successive fields used in the statistical processing (see Code [Table 4.11](https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-11.shtml)) | | 74 | Indicator of unit of time range over which statistical processing is done (see Code [Table 4.4](https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-4.shtml)) | | 75-78 | Length of the time range over which statistical processing is done, in units defined by the previous octet | | 79 | Indicator of unit of time for the increment between the successive fields used (see Code [Table 4.4]) | | 80-83 | Time increment between successive fields, in units defined by the previous octet (see Note 3) | | | 84 - nn These octets are included only if n>1, where nn = 64 + 12 x n | | 84-95 | As octets 72 to 83, next innermost step of processing | | 96-nn | Additional time range specifications, included in accordance with the value of n, Contents as octets 68 to 79, repeated as necessary. |
New template 173d - Probability forecasts at a horizontal level or in a horizontal layer at a point in time for radionuclides | Octet No. | Contents | | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 10 | Parameter category: Radio nuclide constituents (see Code table 4.1) | | 11 | Parameter number (See Code table 4.2.0.18) | | 12-13 | Constituent type (See Code table 4.230.table) | | 14 | Source-Sink (See Code table 4.238.table) | | 15-16 | Transport model used (See Code table 4.333) | | 17-18 | Requested by entity (See Code table 4.334) | | 19-20 | Scenario origin (See Code table 4.335) | | 21-22 | NWP used (See Code table 4.336) | | 23-24 | Release start year | | 25 | Release start month | | 26 | Release start day | | 27 | Release start hour | | 28 | Release start minute | | 29- | Release start second | | 30-31 | Wall clock initial time of execution (Year) | | 32 | Wall clock initial time of execution (month) | | 33 | Wall clock initial time of execution (day) | | 34 | Wall clock initial time of execution (hour) | | 35 | Wall clock initial time of execution (minute) | | 36 | Wall clock initial time of execution (second) | | 37 | Type of generating process (See Code table 4.3) | | 38 | Background generating process identifier (defined by originating centre) | | 39 | Analysis or forecast generating process identifier (see Code ON388 Table A) | | 40-41 | Hours of observational data cut-off after reference time | | 42 | Minutes of observational data cut-off after reference time | | 43 | Indicator of unit of time range (see Code table 4.4) | | 44-47 | Forecast time in units defined by octet 43 | | 48 | Type of first fixed surface (see Code table 4.5) | | 49 | Scale factor of first fixed surface | | 50-53 | Scaled value of first fixed surface | | 54 | Type of second fixed surface (see Code table 4.5) | | 55 | Scale factor of second fixed surface | | 56-59 | Scaled value of second fixed surface | | 60 | Type of ensemble forecast (See code table 4.6.table) | | 61 | Perturbation Number | | 62 | Number of forecasts in ensemble | | 63-64 | Year of end of overall time interval | | 65 | Month of end of overall time interval | | 66 | Day of end of overall time interval | | 67 | Hour of end of overall time interval | | 68 | Minute of end overall time interval | | 69 | Second of end of overall time interval | | 70 | n - number of time ranges specifications describing the time intervals used to calculate the statistically-processed field | | 71-74 | Total number of data values missing in the statistical process | | | 63 - 74 Specification of the outermost (or only) time range over which statistical processing is done | | 75 | Statistical process used to calculate the processed field from the field at each time increment during the time range
(see Code [Table 4.10](https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-10.shtml)) | | 76 | Type of time increment between successive fields used in the statistical processing (see Code [Table 4.11](https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-11.shtml)) | | 77 | Indicator of unit of time range over which statistical processing is done (see Code [Table 4.4](https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-4.shtml)) | | 78-81 | Length of the time range over which statistical processing is done, in units defined by the previous octet | | 82 | Indicator of unit of time for the increment between the successive fields used (see Code [Table 4.4](https://www.nco.ncep.noaa.gov/pmb/docs/grib2/grib2_doc/grib2_table4-4.shtml)) | | 83-86 | Time increment between successive fields, in units defined by the previous octet (see Note 3) | | | 87 - nn These octets are included only if n>1, where nn = 64 + 12 x n | | 87-98 | As octets 75 to 86, next innermost step of processing | | 99-nn | Additional time range specifications, included in accordance with the value of n, Contents as octets 68 to 79, repeated as necessary. |
Update Code table 1.2 - Significance of reference time _Add code 5, Simulation start_ Code Figure | Meaning -- | -- 0 | Analysis 1 | Start of forecast 2 | Verifying time of forecast 3 | Observation time 4 | Local time **5** | **Simulation start (see note 1)** 6-191 | Reserved 192-254 | Reserved for local use 255 | Missing (1) For use with downstream models (from NWP) such as dispersion modeling or air quality.
Add codes to Code table 4.2: Product discipline 0 – Meteorological products, parameter category 18: nuclear/radiology _Time of arrival and departure are added together with effective and thyroid dose and activity emission. (The doses may be a bit ambiguous as one often differs between children and adult doses.)_ Number |Parameter  |Units   -- | -- | -- 19 | Deposition activity arrival (see note 1) |seconds 20 | Deposition activity ended (see note 1) |seconds 21 | Cloud activity arrival (see note 1) |seconds 22 | Cloud activity ended (see note 1) |seconds 23 | Effective dose rate: adult |nSv h-1 24 | Thyroid dose rate: adult |nSv h-1 25 | Gamma dose rate |nSv h-1 26 | Activity emission |Bq s-1 27-191 | Reserved | _(1) Use the radionuclide release start date as baseline to determine activity arrival or activity end._
Editorial update of existing entries in Code table 4.2: Product discipline 0 – Meteorological products, parameter category 18: nuclear/radiology _One becquerel (Bq) is defined as the activity of a quantity of radioactive material in which one nucleus decays per second. In the current table 4.2.0.18, entries with units containing Bq should contain in their definition the word activity. Activity concentration is conceptually different from other measures of chemical concentration such as those in table 4.2.0.20 (Atmospheric Chemical Constituents)._ Number | Parameter | Units -- | -- | -- 0 | Air **activity** concentration of Caesium 137 | Bq m-3 1 | Air **activity** concentration of Iodine 131 | Bq m-3 2 | Air **activity** concentration of radioactive pollutant | Bq m-3 3 | Ground deposition **activity** of Caesium 137 | Bq m-2 4 | Ground deposition **activity** of Iodine 131 | Bq m-2 5 | Ground deposition **activity** of radioactive pollutant | Bq m-2 6 | Time integrated air **activity** concentration of Cesium pollutant (See Note 1) | Bq s m-3 7 | Time integrated air **activity** concentration of Iodine pollutant (See Note 1) | Bq s m-3 8 | Time integrated air **activity** concentration of radioactive pollutant (See Note 1) | Bq s m-3 9 | Reserved |   10 | Air **activity** concentration (See Note 3) | Bq m-3 11 | Wet deposition **activity** | Bq m-2 12 | Dry deposition **activity** | Bq m-2 13 | Total deposition **activity** (Wet + Dry) | Bq m-2 14 | Specific **activity** concentration (See Note 3) | Bq kg-1 15 | Maximum of air **activity** concentration in layer | Bq m-3 16 | Height of maximum air **activity** concentration | m 17 | Column-integrated air **activity** | Bq m-2 18 | Column-averaged air **activity** concentration in layer | Bq m-3 19-191 | Reserved |
Update Code table 4.230 (CCT-14): Atmospheric chemical constituent type _Reference constituent H+1 representing activity one hour after nuclear detonation, commonly used for effect evaluations on different time scales. Some additional nuclides included_. | code | | | ----- | ----------------------------------------------- | | 30296 |  Lead Pb | | # | 30297-59999 Reserved | | | | | New | | | New | Activity relative to one hour after release H+1| | already exist | ~Silver 110 metastable Ag110m ~ | | New | Silver 112 Ag-112 | | New | Silver 115 Ag-115 | | New | Barium 139 Ba-139 | | New | Barium 141 Ba-141 | | New | Barium 142 Ba-142 | | New | Bromine 84 Br-84 | | New | Cadminum 115 Cd-115 | | New | Cadminum 117 Cd-117 | | New | Cadminum  117 metastable Cd-117m | | New | Cerium 145 Ce-145 | | New | Cerium 146 Ce-146 | | New | Cobalt 58 metastable Co-58m | | New | Ceasium 138 Cs-138 | | New | Ceasium 139 Cs-139 | | New | Iodine 130 aerosol I-130a | | New | Iodine 130 elementary  gaseous I-130e | | New | Iodine 130 organic bounded I-130o | | New | Iodine 132 metastable I-132m | | New | Iodine 134 metastable I-134m | | New | Indium 115 metastable In-115m | | New | Indium 117 metastable In-117m | | New | Krypton 83 metastable Kr-83m | | New | Lanthanum 142 La-142 | | New | Lanthanum 143 La-143 | | New | Manganese 56 Mn-56 | | New | Molybdenum 101 Mo-101 | | New | Molybdenum 102 Mo-102 | | New | Neodymium 149 Nd-149 | | New | Neodymium 151 Nd-151 | | New | Palladium 109 Pd-109 | | New | Palladium 112 Pd-112 | | New | Praseodymium 145 Pr-145 | | New | Praseodymium  146 Pr-146 | | New | Praseodymium  147 Pr-147 | | New | Rubidium 89 Rb-89 | | New | Rubidium 90 Rb-90 | | New | Rubidium 90 metastable Rb-90m | | New | Rhodium 105 metastable Rh-105m | | New | Rhodium 107 Rh-107 | | New | Antimony 120 Sb-128 | | New | Antimony 128 metastable Sb-128m | | New | Antimony 129 metastable Sb-129m | | New | Antimony 130 Sb-130 | | New | Antimony 130 metastable Sb-130m | | New | Antimony 131 Sb-131 | | New | Antimony 132 Sb-132 | | New | Antimony 132 metastable Sb-132m | | New | Antimony 133 Sb-133 | | New | Selenium 83 Se-83 | | New | Tin 127 Sn-127 | | New | Tin 127 metastable Sn-127m | | New | Tin 128 Sn-128 | | New | Tin 129 metastable Sn-129m | | New | Tin 130 Sn-130 | | New | Strontium 93Sr-93 | | New | Technetium 101 Tc-101 | | New | Technetium 102 Tc-102 | | New | Technetium 104 Tc-104 | | New | Technetium 105 Tc-105 | | New | Tellurium 133 Te-133 | | New | Tellurium 133 metastable Te-133m | | New | Tellurium 134 Te-134 | | New | Yttrium 93 metastable Y-93m | | New | Yttrium 94 Y-94 | | New | Yttrium 95 Y-95 | | New | Zirconium 96 Zr-96 | | # | YYY-59999 Reserved | | | | (1): Use the radionuclide release start date as the reference date for Time (of cloud arrival or leaving).
Update Code table 4.10: Type of statistical processing Add median. Code figure |Meaning -- | -- 12 | Return period *13* | *Median* 14-191 | Reserved
Update Code table 4.238 - Source or sink | code | meaning | | ---- | ----------------------- | | 26 | Road transportation | | 27 | Off-road transportation | | 28 | Nuclear power plant | | 29 | Nuclear weapon |
The following new tables are intended to provide meta data of the origin of the data such as: * transport dispersion model used * origin of emission scenario used * the NWP model used do drive the dispersion modeling **New table 4.333 - Transport dispersion model used** Code figure | Meaning -- | -- 1 | DERMA (Danish Emergency Response Model of the Atmosphere) 2 | E-EMEP (Emergency EMEP model) 3 | FLEXPART (Particle dispersion model) 4 | MLDP (Modèle lagrangien de dispersion de particules) 5 | MATCH (Multi-scale Atmospheric Transport Model) 6 | SILAM (System for Integrated modeLling of Atmospheric composition) 7 | SNAP (Severe Nuclear Accident Program) 8 | WRF-Chem (Weather Research and Forecasting Chemical model) 9 | Trajectoire (Trajectory model) **New table 4.335 - Emission scenario origin** Code figure | Meaning -- | -- 1 | ARGOS (Accident Reporting and Guiding Operational System) 2 | JRODOS (Java version of Real time Online Decision SuppOrt System) 3 | ASSIMILATED (Scenario retrieved from measurements) 4 | CENTRE (Scenario by originating centre) **New table 4.336 - NWP Model** Code figure | Meaning | - | -------------------------------------------------------------------- | | 1 | AROME (Meso scale NWP, Meteo-France) | | 2 | ARPEGE (Global scale NWP. Meteo-France) | | 3 | GFS (Global forecast system, NCEP) | | 4 | HARMONIE (HIRLAM-ALADIN Research on Mesoscale Operational NWP) | | 5 | HIRLAM (HIgh resolution Limited Area Model) | | 6 | IFS (Integrated Forecast System) | | 7 | GEM GDPS (Canadian Global Deterministic Prediction System) | | 8 | GEM RDPS (Canadian Regional Deterministic Prediction System) | | 9 | GEM HRDPS (Canadian High Resolution Deterministic Prediction System) | | 10| WRF (Weather Research and Forecasting)|
Update CCT-11 with national radiation agencies | Octet | Originating/generating centres | | ------------ | ------------------------------------------------------------------------- | | 291 | Alliance of International Science Organizations (Beijing, China) | | 292 | Helmholtz Centre for Environmental Research | | 300 | Greek Atomic Energy Commission (Greece) | | 301 | United Stated Envirnmental Agency (USA) | | 302 | Autralian radiation Protection and Nuclear Safety (Australia) | | 303 | Authority for Nuclear Safety and Radiation Protection (The Netherlands) | | 304 | Autorite de Surete Nucleaire (France) | | 305 | Bundesamt für Strahlenschutz (Germany) | | 306 | National Commission for Nuclear Activities Control (Romania) | | 307 | Consejo de Seguridad Nuclear (Spain) | | 308 | Danish Emergency Management Agency (Denmark) | | 309 | Norwegian radiation protection agency (Norway) | | 310 | Federal Agency for Nuclear Control (Belgium) | | 311 | Institute of Radiation Protection and Dosimetry (Barzilia) | | 312 | National Inspectorate for Nuclear Safety and Radiation Protection (Italy) | | 313 | Nuclear Regolatory Authority (Turkey) | | 314 | Nuclear Regulation Authority (Japan) | | 315 | Nuclear Regulatory Agency (Bulgaria) | | 316 | Ukrainien Radiation Protection Institute (Ukriane) | | 317 | Health Canada Radioprotection Bureau (Canada) | | 318 | Portuguese Society for Radiation Protection (Portugal) | | 319 | Swedish radiation safety authority (Sweden) | | 320 | Finnish radiation protection agency (Finland) | | 321 | State Office for Nuclear Safety (Czechia) | | 322 | Nuclear Regulation Authority (Slovakia) | | 65535: 65535 | Missing value |

Proposal_for_an_Amendment-v0.7.docx

sebvi commented 2 years ago

Thank you @tomkralidis , Lennart and Yves for submitting this proposal. It is quite complex and very dense with a lot of new tables. I would suggest a separate meeting between the proposers and those from @wmo-im/et-data interested in participating. I already have many questions and need for clarifications, I fear this comment area might not be the most efficient way to do this.

amilan17 commented 2 years ago

https://github.com/wmo-im/CCT/wiki/Teleconference-1-and-2.11.2022 notes:

amilan17 commented 1 year ago

removed table 4.336 and replaced with C-11 where applicable

cc' @lennart-grib2

amilan17 commented 1 year ago

https://github.com/wmo-im/CCT/wiki/Teleconference-21.11.2022 notes:

amilan17 commented 1 year ago

https://github.com/wmo-im/CCT/wiki/Teleconference-21.11.2022 notes continued: (@jbathegit) there's a local descriptor called 'generating application' in BUFR (@sebvi) refer to GRIB Product Definition template 4.73 for referring to local values.

lennart-grib2 commented 1 year ago

Dear Anna,

I have got an answer from my colleagues on the new item in Tabel 1.2 referred to in section 1 for significanceOfReferenceTime. This is there to point out that this is a downstream product and neither of the other elements in the table, as also noted in the footnote.

Best regards,

Lennart

Från: Anna Milan @.***> Skickat: den 21 november 2022 15:18:54 Till: wmo-im/GRIB2 Kopia: Robertson Lennart; Mention Ämne: Re: [wmo-im/GRIB2] Updates to facilitate needs in modelling for nuclear protection (Issue #173)

https://github.com/wmo-im/CCT/wiki/Teleconference-21.11.2022 notes continued: @.https://github.com/jbathegit) there's a local descriptor called 'generating application' in BUFR @.https://github.com/sebvi) refer to GRIB Product Definition template 4.73 for referring to local values.

— Reply to this email directly, view it on GitHubhttps://github.com/wmo-im/GRIB2/issues/173#issuecomment-1322133241, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3WGPBMFGMRH2XBGPXEJ3QDWJOAE5ANCNFSM6AAAAAARI6N7BE. You are receiving this because you were mentioned.Message ID: @.***>

amilan17 commented 1 year ago

updated issue summary with most recent revisions:  table 4.336 is back, references in templates 99-102 then altered, extended the list of nuclides in table 4.230.

lennart-grib2 commented 1 year ago

As template 99-102 are by now assigned I suggest labelling 113-116. I thought of following Sebastien's suggestion to use c-11 table instead of the new table 4.336 for description of NWP used. However as already in my table 4.336 the Canadian office is providing three different NWP models that c-11 would not resolve. The extended list of nuclides just came about by trying out a real world application. Are the top table version still 30 or should we consider 31?

amilan17 commented 1 year ago

@lennart-grib2 - The GRIB table versions change with every fast-track approval. version 31 will go operational in May. And if this is finalized for FT2023-2 then the new version will be 32.

I recommend that during the development that you use the following numbers for each template, because we have the same type of conflict as before with other GRIB templates in other proposals.

e.g. ~4.99~ issue173.a (Analysis or forecast for radionuclides) ~4.100~ issue173.b (Average, accumulation, extreme values for radionuclides) ~4.101~ issue173.c (Percentile forecasts for radionuclides) ~4.102~ issue173.d (Probability forecasts for radionuclides)

amilan17 commented 1 year ago

https://github.com/wmo-im/CCT/wiki/Teleconference.2&3May.2023 notes:

Lennart introduced changes from last meeting; team decided that new templates should be 

@sebvi will review the changes and update branch when decision is finalized by June

SibylleK commented 1 year ago

I got some comments from a colleague, who thoroughly reviewed the proposal.

  1. Regarding "Update Code table 4.230 (CCT-14):"
SibylleK commented 1 year ago

Sorry, next try:

I got some comments and hints from a colleague, who thoroughly reviewed the proposal.

Octet No. Contents
19 Scenario origin (See Code table 4.335)
20 - 21 Scenario index (identifier) (IScn = 1, …, NScn)
22 - 23 Total number of scenarios (NScn)
Octet No. Contents
17 Transport model used (See Code table 4.333)
There might be a large number of different transport models and even more to come in the future. Might it be worth considering to assign two octets (17 - 18)? The same argument applies to the following entries: Octet No. Contents
18 Requested by entity (See Code table 4.334)
19 Scenario origin (See Code table 4.335)
20 NWP model used (See Code table 4.336)
lennart-grib2 commented 1 year ago

Very good comments. I have made a new suggestion based on the templates 76-79. Observant that Te-131 is now already covered. There were also iodine isotopes duplicated. I follow your suggestion to make meta data such as "Transport model used" in two octets. But I have left your suggestion for Scenarios for the discussion.

In ECCODES the new meta data looks like

Info part

codetable[2] modelUsed ('4.333.table',masterDir,localDir) : dump; codetable[2] requestedBy ('4.334.table',masterDir,localDir) : dump; codetable[2] scenarioOrigin ('4.335.table',masterDir,localDir) : dump; codetable[2] nwpUsed ('4.336.table',masterDir,localDir) : dump;

Release date and time

unsigned[2] releaseYear = 1971 : dump; unsigned[1] releaseMonth = 1 : dump; unsigned[1] releaseDay = 0 : dump; unsigned[1] releaseHour = 0 : dump; unsigned[1] releaseMinute = 0 : dump; unsigned[1] releaseSecond = 0 : dump;

Wall clock initial time of execution

unsigned[2] executionYear = 1971 : dump; unsigned[1] executionMonth = 1 : dump; unsigned[1] executionDay = 0 : dump; unsigned[1] executionHour = 0 : dump; unsigned[1] executionMinute = 0 : dump; unsigned[1] executionSecond = 0 : dump;

The Template 173a is defined as:

include "grib2/template.4.parameter.def" include "grib2/template.4.chemical.def" include "grib2/template.4.source.def" include "grib2/template.4.generating_meta_data.def" include "grib2/template.4.generating_process.def" include "grib2/template.4.forecast_time.def" include "grib2/template.4.horizontal.def"

sebvi commented 1 year ago

@lennart-grib2 : could you explain why the requesting institution needs to be encoded in the GRIB2? Is it absolutely needed to know who request the simulation to be able to interpret the data? Are the results of the simulation different depending on the requestinf institution? If this is not useful to intepret the GRIB message it should not be encoded at all in the metadata. It could be part of the filename and associated documentation.

We have already in section 4 templates a way to specify an upstream model providing a background for the subsequent model. It can be seen for instance in template 4.73. The 3 keys available for this are "input process identifier", "input originating centre" and "type of postprocessing". The first key could be used to identify the upstream NWP model, it is its purpose. The second key would identify the producer of that upstream model. The third key is typically used to encode the type of downstream application, in this case it could be "dispersion modelling". After that, there are the traditional keys used in all section 4 templates to encode the model: background generating process identifier and forecast generating process identifier. I think we should try to reuse these keys where possible as they provide some of the functionality needed for this proposal.

lennart-grib2 commented 1 year ago

Comment 1: could you explain why the requesting institution needs ...

In crisis management we expect that transport calculations may be shared among nuclear protection agencies. The requesting institution of the results at hand is then vital information in the decision making. We simply suggest that the grib message should be self contained and not reside on odd file naming conventions.

Comment 2: We have already in section 4 templates a way to specify...

inputProcessIdentifier offers no table description inputOriginatingCentre refers to table common/c-11.def that "only" covers met-services and thus not valid here. typeOfPostProcessing offers no table description

In short: not fit for our purpose.

===== I will send an update to Anna Milan this morning where the table 4.230 is revised in terms of more found duplicates and all nuclides written out in full text like, Silver 110 metastable Ag-110m. WRF is added to the list of NWP models in table 4.336. Corrected the typing error Sibylle pointed out regarding Forecast time in units defined by octet xx.

sebvi commented 1 year ago

I still fail to see why the requesting institution is useful to interpret and use correctly the content of the data section. In my mind, this information is not critical to use the data and should not be part of the metadata. It seems to me that it is there for convenience to satisfy a local and internal data management within the involved institutions. If you absolutely want to have it encoded inside the GRIB message, that sort of information is typically added in the local section 2 of the message.

Regarding reusing the mechanism from template 4.73: There are tables associated with the keys I mentioned. These tables are not meant to be managed by WMO but left to be managed by each met services, agencies and research institutions. At ECMWF, and I suspect at other agencies, it is used to encode the NWP model and model versions/configurations. This is where ECMWF encodes which cycle version of IFS produced the data. It is then the responsibility of the agencies to publish their tables. It was designed this way recognising the difficulty to have a unique and central table to list all the models and model versions of all the WMO members.

I can give you a concrete example : 12-13 inputProcessIdentifier = 6 <- upstream NWP model, it could be what you have in the proposed 4.336 , here IFS 14-15 inputOriginatingCentre = 98 <- upstream NWP producer from CCT-11, here ECMWF 16 typeOfPostProcessing = 5 <- model used to produce our data, it could be any of your dispersion model from the proposed table 4.333, here MATCH 17 typeOfGeneratingProcess = 4 from code cable 4.3 18 backgroundProcess = 1 this is where you could encode the scenarii of the proposed table 4.335, here ARGOS 19 generatingProcessIdentifier = 1 this would be where you encode the version of the model specified in typeOfPostProcessing, so for instance MATCH cycle 1, but it could be an integer read from a table and 1 could mean "version 2.3".

Regarding your proposed table 4.334: We try to centralise all the met services, international agencies, research institutes ,etc. in one single table used by both GRIB and BUFR data format and I would strongly suggest to not create the proposed table 4.334 but instead to request new entries in Common Code Tables, then use these common tables when you need to reference these institutions.

amilan17 commented 1 year ago

I updated the issue summary.

amilan17 commented 1 year ago

https://github.com/wmo-im/CCT/wiki/Teleconference.6.7.June.2023 notes:

Lennart presented the recent changes; there was a conversation about including the model and version table and requesting institution;  validate in July; 

@SibylleK -- it would be great if you can help validate/review ;

@sebvi contact DWD colleague in the meantime

amilan17 commented 1 year ago

https://github.com/wmo-im/CCT/wiki/Teleconference.13.July.2023 notes:

Proposal is close to ready, but not quite mature enough. @marijanacrepulja will update branch, but it may be postponed to FT2024-1

amilan17 commented 1 year ago

@lennart-grib2 -- Is it ok if this proposal goes into FT2024-1 (for release in May 2024) rather than FT2023-2 (release in November 2023)?

lennart-grib2 commented 1 year ago

Dear Anna,

I have not got any response from Sebastien yet so there will most likely be some iterations to come. You do best judge what time it will take. Does this mean the fast track is starting or ending by the suggested dates?

Best regards,

Lennart

17 juli 2023 kl. 13:40 skrev Anna Milan @.***>:



@lennart-grib2https://github.com/lennart-grib2 -- Is it ok if this proposal goes into FT2024-1 (for release in May 2024) rather than FT2023-2 (release in November 2023)?

— Reply to this email directly, view it on GitHubhttps://github.com/wmo-im/GRIB2/issues/173#issuecomment-1637957465, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A3WGPBOGNTAWXE4K42IO75LXQUQD3ANCNFSM6AAAAAARI6N7BE. You are receiving this because you were mentioned.Message ID: @.***>

amilan17 commented 1 year ago

@lennart-grib2 Thank you I changed the fast-track milestone. The dates in the comment above indicates the expected final date WMO approval of proposals and publication of machine-readable codes for use.

amilan17 commented 1 year ago

https://github.com/wmo-im/CCT/wiki/Teleconference.17.18.October.2023 notes: Lennart introduced some of the recent changes in his document based on the last feedback; @sebvi will review this evening and we can discuss again if needed.

sebvi commented 1 year ago

@wmo-im/tt-tdcf and @lennart-grib2

I have reviewed the proposal in the word document attached in the original post (v0.7) and here are my comments/questions:

At the end I still struggle to see why the requesting agency is important. Who is receiving the data does not impact how the data is interpreted so I would think this could be omitted and placed in the documentation or the filename. If absolutely necessary for internal use by the RPA's, it could be place in the local part of section 2. Or you could use the mechanism centre + subcentre where the data producer is the "centre" and the receiving agency the "subcentre" of that centre.

amilan17 commented 1 year ago

https://github.com/wmo-im/CCT/wiki/Teleconference.17.18.October.2023 notes:

SibylleK commented 1 year ago

In addition to the comment, that it would be useful to include in the PDTs something like Reference incident (defined by originating centre) (2 or even 4 octetts) and Number of scenario update (2 octetts),

there are some additional entries for the new code tables 4.333, 4.335 and 4.336 proposed by DWD-colleagues:

New table 4.333 - Transport dispersion model used: ICON-ART (ICOsahedral Non-hydrostatic model Aerosols and Reactive Trace gases) LPDM-DWD (Lagrangian Particle-Dispersion-Model of the German Meteorological Service)

New table 4.335 - Emission scenario origin: IAEA (International Atomic Energy Agency)

New table 4.336 - NWP model: ICON (ICOsahedral Non-hydrostatic model)

IAEA can also be the requesting entitiy, therefore it is also proposed to include in CCT-11: 323 - International Atomic Energy Agency (IAEA)

lennart-grib2 commented 1 year ago

Thanks for the good suggestions. Concerning table 4.230 and "activity relative to one hour after release" I suggest "nuclide cocktail" or "user defined nuclide cocktail". The notation "one hour after release" implied that the most short lived nuclides have disappeared (from the cocktail) and no longer of interest for dose assessment. It is a good point to avoid this restrictive meaning.

It could also be good to have the current start number in table 4.230 for the added nuclides as well table version to be used now.

amilan17 commented 1 year ago

from email:

Sending over example data of the "final" suggestion.

http://exporter.nsc.liu.se/6a2e57d9577f49a69137f2a9834719d4 rsync://exporter.nsc.liu.se/6a2e57d9577f49a69137f2a9834719d4

The content is: readme.txt eccode_tables.tgz Proposal_for_an_Amendment-v0.8.docx data data/bomb_MATCH_coco data/bomb_MATCH_conc
data/bomb_MATCH_depo data/bomb_MATCH_dose data/bomb_MATCH_eofa data/bomb_MATCH_sofa data/bomb_MATCH_tofa data/bomb_MATCH_wetd

Best regards,

Lennart

amilan17 commented 11 months ago

https://github.com/wmo-im/CCT/wiki/Teleconference.21.22.November.2023 notes:

amilan17 commented 11 months ago

https://github.com/wmo-im/CCT/wiki/Teleconference.21.29.November.2023 notes:

still in progress; template numbers will probably be 124 +

amilan17 commented 10 months ago

https://github.com/wmo-im/CCT/wiki/Teleconference.10.January.2024 notes:

marijanacrepulja commented 8 months ago

@sebvi what is the status of this issue, is it ready for the FT2024-1? Thanks

lennart-grib2 commented 8 months ago

From my point of view I think we are ready. The issues left may be the numbering of templates and version.

sebvi commented 8 months ago

@sebvi what is the status of this issue, is it ready for the FT2024-1? Thanks

@marijanacrepulja I have started the branch but did not finish it. :/
I realized part of the proposal needs updating the CCT14 in the CCT repo so I need to create an issue there, create a branch, then add the nuclides. I will try to finish the work by the end of this week

marijanacrepulja commented 8 months ago

Thanks @sebvi

@amilan17 is this in time to be part of FT2024-1?

amilan17 commented 8 months ago

@marijanacrepulja @sebvi Actually yes, IF it's done by the end of this week.

sebvi commented 8 months ago

@lennart-grib2 : it turns out that silver 110 metastable is already in the table, it is entre 30106, did you, by any chance meant Silver 110 "unstable" then (the one with 24seconds half life)?

I have also corrected few typos in that table

sebvi commented 8 months ago

@amilan17 : branch should be ready but please check as it was a complex branch to update

amilan17 commented 8 months ago

@sebvi @marijanacrepulja @lennart-grib2 I'm trying to remember if we made a decision to change "Activity relative to one hour after release H+1". I'm copying two comments below (from above) that look unresolved.

amilan17 commented 8 months ago
  • change to "lumped radioactive material" and make "H+1" a parameter : 30299 | Activity relative to one hour after release (Bq) | H+1
amilan17 commented 8 months ago

Concerning table 4.230 and "activity relative to one hour after release" I suggest "nuclide cocktail" or "user defined nuclide cocktail". The notation "one hour after release" implied that the most short lived nuclides have disappeared (from the cocktail) and no longer of interest for dose assessment. It is a good point to avoid this restrictive meaning.

lennart-grib2 commented 8 months ago

I think "nuclide cocktail" is sufficient.

amilan17 commented 8 months ago

@sebvi The names of the templates have changed. I assume this was on purpose. Can you please confirm or correct the mapping below?

173a (Analysis or forecast for radionuclides) => 124 173b (Average, accumulation, extreme values for radionuclides) => 126 173c (Percentile forecasts for radionuclides) =>125? 173d (Probability forecasts for radionuclides) => 127? vs 124 Analysis or forecast at a horizontal level or in a horizontal layer at a point in time for radionuclides 125 Individual ensemble forecast, control and perturbed, at a horizontal level or in a horizontal layer at a point in time for radionuclides 126 Average, accumulation, and/or extreme values or other statistically processed values at a horizontal level or in a horizontal layer in a continuous or non-continuous time interval for radionuclides 127 Individual ensemble forecast, control and perturbed, at a horizontal level or in a horizontal layer in a continuous or non-continuous time interval for radionuclides

amilan17 commented 8 months ago

I think "nuclide cocktail" is sufficient.

@lennart-grib2 this is preferable to "lumped radioactive material"?

lennart-grib2 commented 8 months ago

It should be Antimony 128 Sb-128.

We should change from "nuclide cocktail" to "pseudo radionuclide".

sebvi commented 8 months ago

@sebvi The names of the templates have changed. I assume this was on purpose. Can you please confirm or correct the mapping below?

173a (Analysis or forecast for radionuclides) => 124 173b (Average, accumulation, extreme values for radionuclides) => 126 173c (Percentile forecasts for radionuclides) =>125? 173d (Probability forecasts for radionuclides) => 127? vs 124 Analysis or forecast at a horizontal level or in a horizontal layer at a point in time for radionuclides 125 Individual ensemble forecast, control and perturbed, at a horizontal level or in a horizontal layer at a point in time for radionuclides 126 Average, accumulation, and/or extreme values or other statistically processed values at a horizontal level or in a horizontal layer in a continuous or non-continuous time interval for radionuclides 127 Individual ensemble forecast, control and perturbed, at a horizontal level or in a horizontal layer in a continuous or non-continuous time interval for radionuclides

Yes, this is the changes I did as I mentioned earlier . The names of the of the templates do not match their content. That is, the templates, as they are defined in the word document, and in particular in the explicit key by key tables suggests the implementation of templates with the name I gave them. So the names I changed correspond to what is implemented in the various files I added/modified in the branch. If @lennart-grib2 really requires the percentiles and probability templates, then we need to create them but I suspect that this can not be done until next Fast Track although relatively straightforward to develop now the base keys and associated tables have been drafted for radionuclides.

Regarding activity/radionuclide cocktail and pseudo radionuclide, I do not have a strong opinion on this although I would prefer to be as explicit as possible. So if pseudo radionuclide is a proxy to represent all the radionuclides present, lets add something in the name to make it clear.

amilan17 commented 8 months ago

@sebvi @lennart-grib2 I updated part of the issue proposal to indicate the final codes and names of the templates

New templates: