Other output files depend on the Driver Table, specifically on the Flags enabled in the *FLG section of the driver table. The available output options can be limited by other flags, usually because the type of output is not meaningful with a particular type of calculation - see under individual output flags for details.
Spectral Files
The main purpose of the RFM is to generate spectral files,
written either as ASCII (default) or Binary (BIN flag) files, in Single (default)
or Double (DBL flag) precision.
A separate file is generated for each spectral range, label [s] (as defined in the *SPC section) and tangent height/viewing geometry [t] (as defined in the *TAN section).
| Flag | Description | Units | Filename | |||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
ABS
| Absorption (=1-transmission) Spectrum
| [none]
| abs_[s][t].asc
| BBT
| Brightness Temperature Spectrum
| [K]
| bbt_[s][t].asc
| COO
| Cooling Rate Spectrum (with FLX Flag)
| [K/day/cm-1]
| coo_[s][t].asc
| OPT
| Optical Depth (=-ln(transmission)) Spectrum
| [none]
| opt_[s][t].asc
| RAD
| Radiance Spectrum, or
| [nW/(cm2.st.cm-1)]
| rad_[s][t].asc
|
| (with FLX flag)
Radiance Flux Spectrum
| [W/(m2.cm-1)]
| TRA
| Trasmission Spectrum
| [none]
| tra_[s][t].asc
| |
Diagnostic Files
Additional diagnostic information (ASCII files only) can be produced
for the internal profile,
ray-tracing and line-by-line
calculations, with separate files generated for different
line-of-sight angles [l] (as specified in the
*ATM section
if GRA
flag selected), tangent height/viewing geometry [t]
(as specified in the *TAN section) and
spectral range [s] as specified in the *SPC section) respectively.
| Flag | Description | Filename | ||||||
|---|---|---|---|---|---|---|---|---|
PRF
| Atmospheric Profile
| prf_[l].asc
| PTH
| Ray Path Diagnostics
| pth_[t].asc
| WID
| Widemesh Diagnostics
| wid_[s].asc
| |
Lookup Tables
The RFM can generate lookup tables of absorption coefficient tabulated
as functions of pressure, temperature and wavenumber. One table is
generated for each spectral range [s] (as defined in the
*SPC section) and absorbing species
[g] (defined in the *GAS section).
These can be used as input files (LUT
flag) as a faster alternative to line-by-line calculations.
| Flag | Description | Units | Filename |
|---|---|---|---|
TAB
| Absorption Coefficient table
| [m2/mole]
| tab_[s][g].asc
| |
The RFM has default filename templates for each class of output file, as
listed in the tables above, which
will create the files in the user's directory. The actual filenames as
they are opened are listed
in the rfm.runlog file.
The simplest way to modify the output filename (eg to distinguish the output
from similar runs) is to enter characters in response to the
Run ID prompt.
For more radical changes, including redirecting to different directories,
it is possible to alter the default templates
by adding optional sections to
the driver table. These optional section match the flag which creates
the output.
If multiple files are created, it is necessary for the template to contain
a wildcard character '*' which will be expanded to provide a unique
spectral_range/gas/tangent_height identifier.
For example, if the user specifies output filenames for transmission files
by adding a section to the Driver Table:
Changing Output Filenames
Then, for tangent heights 20, 25 km and spectral ranges labelled 'a' and 'b',
4 files will be created with filenames:
*TRA
./out/rfm_*.tra
rfm_a20000.tra
rfm_a25000.tra
rfm_b20000.tra
rfm_b25000.tra
Other Output Options
Flag Description Effect
BIN
Write spectra and LUTs as Binary files rather than
ASCII files
Generates smaller files and faster I/O, but more difficult to read
LUN
Reuse Logical Unit Numbers for output files rather than
maintain a separate open LUN for each
Avoid exceeding limited number of available LUNs on some machines,
at expense of slighlty slower write time
NEW
Open output files with STATUS='NEW' in FORTRAN OPEN
statement rather than STATUS='UNKNOWN'
Avoids overwriting any existing files of the same name (resulting
in a fatal error condition)