MORSE Input Files

09APR18

When MORSE is run, certain input files are always required: the driver table (morse.drv) and files associated with mandatory sections of the driver table. Additional files may be required by optional sections of the driver table. Click on File column in the table below for details of a particular file.

MORSE Input Files
Driver File
morse.drv Driver Table
Mandatory Sections
Section File Description Limb Only Nadir Only
*L1C *.l1c Level 1C Data (apodised spectra)
*.noi Noise data (Nadir)
*.swp Retrieved pointing (Limb, optional)
*MWL *.lst Microwindow List
*MDB MW*.DAT MIPAS Microwindow Database (optional)
*ATM *.atm Climatological or Colocated profile Data
*ILS *.ils (Apodised) Instrument Line Shape
*FOV *.fov Field of View (Limb)
Optional Sections
Section File Description
*HIT *.bin HITRAN Binary File
*LUT *.tab Look-Up Tables
*SVD CS*DAT MIPAS SVD-compressed Look-Up Tables
*XSC .xsc Molecular Cross-Sections

Notes

  1. Most input files start with an arbitrary number of optional comment records, identified by the first character being '!'
  2. Blank records are ignored
  3. Numerical data are read free format unless otherwise specifed and text data is read either from specific positions within record or using spaces to distinguish fields (effectively free-format but without any requirement for quote marks).
The rest of this document describes each input file in detail

morse.drv (mandatory)

Description
Driver Table
Controls operation of MORSE

Specified
Fixed filename (see Note 1)

Format
See Driver Table

Notes
  1. The filename morse.drv is hard-wired in subroutine msedrv.for.

Examples
morse_pt.drv for pT retrieval
morse_h2o.drv for H2O retrieval

L1C* (mandatory)

Description
MIPAS L1C Data
Apodised spectra for selected microwindows

Specified
Filename specified in *L1C section

Format
See L1C Format

Notes
  1. L1C data can be generated from ESA L1B spectra by the IDL program l1c.pro

Example
L1C_02081_SCAN#13 (Scan#13, Orbit 2081)

*.swp (optional)

Description
Retrieved Sweep tangent altitudes

Specified
Filename specified in *L1C section

Format
Same as MORSE .swp output

Notes
  1. New to MORSE v3: previously the sweep altitudes were updated via the .atm file in the *L2P section.
  2. Only the *SWEEP and *HGT_RTV profiles are read from the .swp file when used as input.

Example
L1C_02081_SCAN#13 (Scan#13, Orbit 2081)

*.lst (mandatory)

Description
List(s) of microwindows to be used in retrieval.

Specified
Filename(s) specified in *MWL section

Format
Records up to C*120
!CMNT [optional comment records]
ISEQ LAB WNOL WNOU ALTL ALTU [ ABS(1) ABS(2) ...etc] [1 record per microwindow]
[eof]
FieldTypeDescriptionRange
!CMNT C*120 Comment record(s) (optional) Record starts with '!'
ISEQ I Sequence Number (Dummy/Optional) eg 1
LAB C*8 Microwindow Label eg PT__0001
WNOL R*8 MW Lower Wavenumber Boundary [cm-1] eg 686.400
WNOU R*8 MW Upper Wavenumber Boundary [cm-1] eg 689.400
ALTL R*4 MW Lower Tangent Altitude [km] eg 30
ALTU R*4 MW Upper Tangent Altitude [km] eg 68
ABS(i) I HITRAN Index of absorber#i (Optional) eg 2 (=CO2)

Notes
  1. The first 4 characters of a non-comment record normally contain the number ISEQ of the microwindow in order of selection, however these are not used by MORSE. Microwindows are processed in the order in which they appear in the .lst file rather than selection sequence.
  2. The Microwindow Label LAB is assumed to occupy positions 5:12 in the record. All subsequent data is read free-format.
  3. If any absorber indices ABS are specified in the .lst file these will override the list of absorbers in the Microwindow Database File
  4. Unlike MORSE, the L1C program requires a single list file in order to extract microwindows from L1B data. However this can be created from different microwindow lists (eg different species) simply by concatenating the individual files, eg
    cat pt_mws.lst h2o_mws.lst > all_mws.lst

Examples
pt_000.lst Microwindows for pT retrieval
h2o_000.lst Microwindows for H2O retrieval

MW*DAT (mandatory-ish)

Description
Microwindow Database file(s)
File containing, amongst other things, the spectral masks, irregular grids and absorber lists associated with each microwindow.

Specified
Filename(s) specified in *MDB section

Format
These are ASCII files whose format is too complicated to detail here, but is described in ESA documents
The Revised Microwindow Database Format
Tech Note PO-TN-IMK-GS-0002 (April, 1999)
ASCII Input Data Interface Control Document (DD53)
PO-IF-DOG-GS-0002 (April, 1999)

Notes
  1. The *.imk microwindow files generated by mwmake program are in fact single microwindow versions of the MW*DAT files, minus the irregular grids which are derived by a separate process - see PO-MA-OXF-GS-0019.pdf

Examples
Directory ./MW contains Microwindow Database Files for various species and spectral resolutions.
See ./MW/README.txt for further details.

*.atm (mandatory)

Description
Climatological profiles
Used as both a priori and initial guess.

Specified
Filename(s) specified in *CLI section

Format
RFM .atm file format

Notes
  1. Profiles have to be supplied for temperature, pressure and every absorbing species (including aerosol if Continuum is retrieved).

Examples
ESA 'Initial Guess' Climatology, as created by U.Leicester are in directory ./IG - see ./IG/README.txt
Also http://www.atm.ox.ac.uk/RFM/rfm_downloads.html#atm for other 'atmospheres'.
aerosol.atm 'zero' aerosol profile.

*.ils (mandatory)

Description
(Apodised) Instrument Line Shape file(s)

Specified
Filename(s) specified in *ILS section

Format
RFM .ils file format.

Notes
  1. Every microwindow has to have a single, valid ILS function assigned to it, although the same function can be assigned to more than one microwindow.

Examples
ofm.ils Idealised AILS for 0.025cm-1 sampling, Norton Beer Strong Apodisation, applicable over whole range.
mipas_a.ails Pre-launch computation of the MIPAS A-band AILS.

*.fov (mandatory)

Description
Field of View file

Specified
Filename specified in *FOV section

Format
RFM .fov file format.

Notes
  1. Only a single FOV function is used for all microwindows.
  2. The FOV tabulated as a function of relative altitude refers to the geometric projection on to the limb - by default the ray-tracing will allow for the expansion due to refraction (unless the FVZ Flag is set in the *FLG section)
  3. No FOV is required for nadir-viewing spectra.

Examples
rfm_1km5.fov Field of View represented as 5 points with 1.5km spacing

*.acv (optional)

Description
A Priori Covariance Matrix

Specified
Filename specified in *ACV section

Format
Same as morse.cov output file.
!CMNT [optional comment records]
N M
SA(1,1) SA(2,1) ...
... SA(N,M)
[eof]
FieldTypeDescriptionRange
!CMNT C*80 Comment record(s) (optional) Record starts with '!'
N I First dimension of matrix eg 36
M I Second dimension of matrix same as N
SA R*8 Covariance Matrix elements eg 0.151308903009384

Notes
  1. Although covariance matrices are always square, the file format is intended to be used for any matrix, so both dimensions N, M are specified (it is checked that these are both the same when the file is read).

Examples
morse.cov

*.bin (optional)

Description
Binary form of HITRAN (-type) line parameter data

Specified
Filename specified in *HIT section

Format
RFM .hit file format

Notes
  1. HITRAN ASCII data converted into a direct-access binary file using the RFM program hitbin.for (this doesn't yet work for the new HITRAN 2004 format - see www.hitran.com)
  2. The same binary files can be used on most unix and linux systems, although for Windows and Sun machines it may be necessary to regenerate the file using hitbin since the byte-ordering appears to be different.
  3. There is a MIPAS-specific database in HITRAN ASCII format - see http://www.ifac.cnr.it/retrieval/database.html. Once you have obtained the necessary permission we can give you the binary version for use with MORSE.

Example
File hitran_dummy.bin in directory ./bin (just H2O lines from 791-808cm-1)

*.atm (optional)

Description
Previously retrieved profiles from the same L1B scan

Specified
Filename(s) specified in *L2P section

Format
RFM .atm file format.

Notes
  1. These are intended to be the MORSE .atm output files from previous retrievals on the same vertical grid - see *L2P section for usage
  2. In MORSE v3, any *SWEEP data is ignored - altitudes are now updated in the *L1C section.

Examples
morse_pt.atm
morse_h2o.atm

CS*DAT (optional)

Description
SVD-compressed Look-Up Tables of absorption coefficients

Specified
Directories specified in *LUT section
Filenames are constructed in the form: CS_[LAB]_[ii].DAT
[LAB] A8 Microwindow Label eg H2O_0001
[ii] I2.2 HITRAN Index of the absorber eg 02 (=CO2).

Format
RFM .lut file format
Also described in PT-TN-OXF-GS_0011.txt

Notes
  1. The SVD-compressed LUTs are those used in the ESA retrieval, generated as part of the microwindow processing suite mwproc (see PO-MA-OXF-GS-0019.pdf)
  2. In theory, instead of the SVD-compressed LUTs, the LUTs generated directly by the RFM using the TAB option can also be used (provided they have the same filenames), however this hasn't been tested.
  3. SF6: although SF6 cross-section data (HITRAN ID=64) is usually used, for historical reasons MORSE assumes that the CS*DAT file has the ID ii=30.
  4. Isotopes: the HITRAN Isotope ID is inserted as a decimal digit after the Gas ID, eg CS_H2O_0001_01.4.DAT for H2O (ID=01) isotope#4 (=HDO).

Examples
In directory ./CS (see ./CS/README.txt)

*.nte (optional)

Description
Vibrational Temperatures (non-LTE calculations)

Specified
Filename(s) specified in *NTE section

Format
RFM .nte file format.

Examples

*.xsc (optional)

Description
Heavy Molecule Cross-Section data

Specified
Directories specified in *XSC section
Filenames are constructed in the form: [gas].xsc
[gas] A7 Name of the molecule eg f12

Format
RFM .xsc file format, except restricted to one molecule per file.

Notes
  1. Molecule names are expected to be lower case and using the F.. codes for CFCs eg f11 for CFCl3

Examples
See http://www.atm.ox.ac.uk/RFM/rfm_downloads.html#xsc
aerosol.xsc flat aerosol spectrum.