Changes between Version 12 and Version 13 of UM/MesoscaleModelling
- Timestamp:
- 26/06/19 10:01:25 (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
UM/MesoscaleModelling
v12 v13 4 4 5 5 = Mesoscale Modelling = 6 7 8 6 9 7 This section provides information specific to the mesoscale weather modelling community. … … 18 16 = Getting Initial Data = 19 17 20 Start dumps, LBCfiles and ensemble data can be obtained from the Met Office archive system (MASS). This is accessed using the MOOSE client. This covers the latest five years. Start dumps from earlier periods can be constructed as GRIB files from ECMWF data.18 Start dumps, lateral boundary condition (LBC) files and ensemble data can be obtained from the Met Office archive system (MASS). This is accessed using the MOOSE client. This covers the latest five years. Start dumps from earlier periods can be constructed as GRIB files from ECMWF data. 21 19 22 20 To get the data, create a help desk ticket providing the following information, … … 85 83 === UKV start dumps === 86 84 87 The UKV start dumps are in MASS with path names of the type:85 The UKV start dumps are in MASS with path names like, 88 86 89 `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv03.T+1`87 * `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv03.T+1` 90 88 91 `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv06.T+1` etc. 89 * `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv06.T+1` 90 * etc. 92 91 93 92 94 93 === UKV forecasts and analyses === 95 94 96 The UKV forecasts and analyses are in the MASS with path names of the type95 The UKV forecasts and analyses are in the MASS with path names like, 97 96 98 97 `moose:/opfc/atm/ukv/prodm/YYYY.pp/prodm_op_ukv_YYYYMMDD_AA_NNN.pp` for the multilevel fields and … … 100 99 `moose:/opfc/atm/ukv/prods/YYYY.p/prods_op_ukv_YYYYMMDD_AA_NNN.pp` 101 100 102 where YYYY = year e.g. 2011, MM = month e.g. 05, DD = day e.g. 21 AA = analysis time = 03, 09, 15 or 21 NNN = the part of the forecast - goes up in two's from 000 to 036. e.g. 000, 002, 004 .... 036 101 where 102 * YYYY = year e.g. 2011, 103 * MM = month e.g. 05, 104 * DD = day e.g. 21 105 * AA = analysis time = 03, 09, 15 or 21 106 * NNN = the part of the forecast - in steps of two from 000 to 036. e.g. 000, 002, 004 ... 036 103 107 104 108 … … 111 115 where YYYY = year e.g. 2011, MM = month e.g. 07. 112 116 113 At minimum, to re-run MOGREPS-R you need the analysis files in the mogreps-r path : E.g. 20110722_qwqy06.T+0.18km 20110722_qwqy18.T+0.18km, and all the perturbations files E.g. `20110722_perts.qwey06.oper??.pp1` where ?? goes from 00 to 23 members.117 At minimum, to re-run MOGREPS-R you need the analysis files in the mogreps-r path e.g. `20110722_qwqy06.T+0.18km 20110722_qwqy18.T+0.18km,` and all the perturbations files e.g. `20110722_perts.qwey06.oper??.pp1` where ?? goes from 00 to 23 members. Also in the mogreps-g path, you need the boundary files e.g. `20110722_qweg00.oper??.FRAMES.EY.tar.gz`. 114 118 115 Also in the mogreps-g path, you need the boundary files e.g. `20110722_qweg00.oper??.FRAMES.EY.tar.gz`.116 117 118 119 119 120 == Getting data from ECMWF == 120 The standard data I provideis from ECMWF's operational data. It is a deterministic forecast from the atmospheric model, version 1, analysis. It is not ERA.121 The standard data provided is from ECMWF's operational data. It is a deterministic forecast from the atmospheric model, version 1, analysis. It is not ERA. 121 122 Data prior to X is in GRIB1 format, after that it is GRIB2. The GRIB start dumps are created by concatenating the following fields: 122 123 … … 129 130 * U and V wind velocities 130 131 131 In contrast a UM dump contains typically a hundred fields. So the GRIB start dumps need to be reconfigured132 In contrast, a UM dump contains typically a hundred fields, so the GRIB start dumps need to be reconfigured. 132 133 133 134