Changes between Version 12 and Version 13 of UM/MesoscaleModelling

Timestamp:

26/06/19 10:01:25 (4 months ago)

Author:

willie

Comment:

—

UM/MesoscaleModelling

@@ -4 +4 @@
 
 = Mesoscale Modelling =
-
-
 
 This section provides information specific to the mesoscale weather modelling community.
@@ -18 +16 @@
 = Getting Initial Data =
 
-Start dumps, 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.
+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.
 
 To get the data, create a help desk ticket providing the following information,
@@ -85 +83 @@
 === UKV start dumps ===
 
-The UKV start dumps are in MASS with path names of the type:
+The UKV start dumps are in MASS with path names like,
 
-`moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv03.T+1`
+ * `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv03.T+1`
 
-`moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv06.T+1` etc.
+ * `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv06.T+1` 
+ * etc.
 
 
 === UKV forecasts and analyses ===
 
-The UKV forecasts and analyses are in the MASS with path names of the type
+The UKV forecasts and analyses are in the MASS with path names like,
 
 `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`
 
-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
+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 - in steps of two from 000 to 036. e.g. 000, 002, 004 ... 036
 
 
@@ -111 +115 @@
 where YYYY = year e.g. 2011, MM = month e.g. 07.
 
-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.
+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`.
 
-Also in the mogreps-g path, you need the boundary files e.g. `20110722_qweg00.oper??.FRAMES.EY.tar.gz`.
-
- 
 
 == Getting data from ECMWF ==
-The standard data I provide is from ECMWF's operational data. It is a deterministic forecast from the atmospheric model, version 1, analysis. It is not ERA.
+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.
 Data prior to X is in GRIB1 format, after that it is GRIB2.  The GRIB start dumps are created by concatenating the following fields:
 
@@ -129 +130 @@
  * U and V wind velocities
 
-In contrast a UM dump contains typically a hundred fields.  So the GRIB start dumps need to be reconfigured
+In contrast, a UM dump contains typically a hundred fields, so the GRIB start dumps need to be reconfigured.