Changes between Version 12 and Version 13 of UM/MesoscaleModelling


Ignore:
Timestamp:
26/06/19 10:01:25 (4 months ago)
Author:
willie
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • UM/MesoscaleModelling

    v12 v13  
    44 
    55= Mesoscale Modelling = 
    6  
    7  
    86 
    97This section provides information specific to the mesoscale weather modelling community. 
     
    1816= Getting Initial Data = 
    1917 
    20 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. 
     18Start 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. 
    2119 
    2220To get the data, create a help desk ticket providing the following information, 
     
    8583=== UKV start dumps === 
    8684 
    87 The UKV start dumps are in MASS with path names of the type: 
     85The UKV start dumps are in MASS with path names like, 
    8886 
    89 `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv03.T+1` 
     87 * `moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv03.T+1` 
    9088 
    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. 
    9291 
    9392 
    9493=== UKV forecasts and analyses === 
    9594 
    96 The UKV forecasts and analyses are in the MASS with path names of the type 
     95The UKV forecasts and analyses are in the MASS with path names like, 
    9796 
    9897`moose:/opfc/atm/ukv/prodm/YYYY.pp/prodm_op_ukv_YYYYMMDD_AA_NNN.pp` for the multilevel fields and 
     
    10099`moose:/opfc/atm/ukv/prods/YYYY.p/prods_op_ukv_YYYYMMDD_AA_NNN.pp` 
    101100 
    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 
     101where  
     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 
    103107 
    104108 
     
    111115where YYYY = year e.g. 2011, MM = month e.g. 07. 
    112116 
    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. 
     117At 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`. 
    114118 
    115 Also in the mogreps-g path, you need the boundary files e.g. `20110722_qweg00.oper??.FRAMES.EY.tar.gz`. 
    116  
    117   
    118119 
    119120== Getting data from ECMWF == 
    120 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. 
     121The 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. 
    121122Data prior to X is in GRIB1 format, after that it is GRIB2.  The GRIB start dumps are created by concatenating the following fields: 
    122123 
     
    129130 * U and V wind velocities 
    130131 
    131 In contrast a UM dump contains typically a hundred fields.  So the GRIB start dumps need to be reconfigured 
     132In contrast, a UM dump contains typically a hundred fields, so the GRIB start dumps need to be reconfigured. 
    132133 
    133134