Changes between Version 10 and Version 11 of UM/MesoscaleModelling

26/06/19 09:49:34 (19 months ago)


  • UM/MesoscaleModelling

    v10 v11  
    55= Mesoscale Modelling = 
    7 {{{#!box type=information 
    8 This page is currently under construction. 
    9 }}} 
    11 This section provides information specific to the mesoscale weather modelling community. Suggestions for items to include are welcome. 
     9This section provides information specific to the mesoscale weather modelling community. 
    1311Mesoscale weather modelling support provides: 
    1816 * Analysis tools for diagnostics, such as NDdiag 
    20 The analysis tools and data are provided by NCAS-CMS. Please acknowledge NCAS-CMS if you have used tools or data provided through our auspices. The software tools are designed to operate under the Unix or Linux operating systems. 
     18= Getting Initial Data = 
    22 [wiki:GettingInitialData Getting Initial Data] 
     20Start 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. 
     22To get the data, create a help desk ticket providing the following information, 
     24 * dates and times required, 
     25 * project name, 
     26 * estimate of the data volume in GB, 
     27 * where in MASS the data is located if it is not one of the standard sets below. 
    25 == External Links == 
     30== Getting data from the Met Office == 
     31The start dumps are now stored in MASS, which can be accessed via MONSooN or JASMIN using the MOOSE interface. 
     33Instructions for setting up external access to MASS from JASMIN are available on the [ Collaboration Twiki]. 
     35To get data for 28/Sep/2011 we would type, 
     38moo get moose:/opfc/atm/global/rerun/201109.file/20110928_qwqg00.T+0 . 
     42(Note the dot).  This takes about 15 to 20 minutes. 
     44To find out whether the data exists, 
     47moo ls moose:/opfc/atm/global/rerun/201109.file 
     50Generally we prefer to get the output from the global runs - these have "qwqg" in the title; otherwise we get the global update - these have "qwqu" in the file name. 
     52For further information on using MOOSE on MONSooN and JASMIN see: [ Getting started with MOOSE on MONSooN and JASMIN]. 
     54=== Older files === 
     55Older files are stored in a packed archive format - these have the extension ".pax".  These usually contain several dumps and have names like, 
     57 coprr.udQU06.20060721.pax 
     60where the "ud" denotes "unified model dump" and QU06 denotes global update output at 06Z.  These have to be unpacked and the files relabelled.  There is a script to do this in 
     65# i will be like coprr.udQU06.20060725.pax 
     66for i in *.pax 
     68print $i 
     69dat=${i%.*}                   # take .pax off the end 
     70datestring=${dat##*.}        # remove bit to left of the rightmost dot 
     71pax -r -f $i 
     72cd opdaily/datawgl 
     73for j in * 
     75mv $j $TMPDIR/${datestring}_$j 
     77cd - 
     82This assumes a list of pax files and  unpacks, relabels and stores the results in $TMPDIR. 
     85=== UKV start dumps === 
     87The UKV start dumps are in MASS with path names of the type: 
     91moose:/opfc/atm/ukv/rerun/201108.file/20110810_qwqv06.T+1 etc...  
     94=== UKV forecasts and analyses === 
     96The UKV forecasts and analyses are in the MASS with path names of the type 
     98moose:/opfc/atm/ukv/prodm/YYYY.pp/prodm_op_ukv_YYYYMMDD_AA_NNN.pp for the multilevel fields and 
     102where 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 
     105=== MOGREPS-R files === 
     107Ensemble fields are in: 
     109moose:/opfc/atm/mogreps-g/rerun/YYYYMM.file moose:/opfc/atm/mogreps-r/rerun/YYYYMM.file 
     111Where YYYY = year e.g. 2011, MM = month e.g. 07 
     113At 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 
     115And all the perturbations files E.g. 20110722_perts.qwey06.oper??.pp1 where ?? Goes from 00 to 23 members. 
     117Also in the mogreps-g path you need the boundary files: E.g. 20110722_qweg00.oper??.FRAMES.EY.tar.gz. 
     121== Getting data from ECMWF == 
     122The 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. 
     123Data prior to X is in GRIB1 format, after that it is GRIB2.  The GRIB start dumps are created by concatenating the following fields: 
     125 * skin temperature, 
     126 * surface pressure, 
     127 * land-sea mask, 
     128 * geo-potential, 
     129 * temperature, 
     130 * specific humidity, 
     131 * U and V wind velocities 
     133In contrast a UM dump contains typically a hundred fields.  So the GRIB start dumps need to be reconfigured 
     136= External Links = 
    27138[ NCAS Climate and High Impact Weather] 
    31142[ Mesoscale Group, University of Reading] 
     145[wiki:WMcGinty W. McGinty] 
     14726 June 2019