RFM v4.35 onwards: this can be either
an RFM output Spectral file or
.grd file defining the range and
regular/irregular grid for the output.
The LABSPC spectral range labels can contain up to 8
characters (no internal spaces). These are case-sensitive and
appear as part of the
so labels are compulsory if more than one spectral
range is required (so that the different output files are
It is possible to have different LABSPC labels identifying
the same upper
and lower limits provided the resolution is different.
RFM v4.35 onwards: same resolution
allowed, but why would you want to do this?)
Predefined LABSPC labels may be redefined
(with a warning in the
rfm.runlog file), but
once the resolution has been
set the label may not be further redefined.
(RFM v4.35 onwards: predefined labels
RESSPC values < 1 are interpreted as resolution in
[cm-1] while values > 1 (integers)
are interpreted as 'number of points
per wavenumber' (ie reciprocal of the resolution). If the
GHZ Flag is selected, the value is
always interpreted as GHz.
Setting RESSPC = 0 is the method for
predefining a range without actually initiating a calculation.
This would normally only be done in a
To activate it, the LABSPC is quoted again, but with a
non-zero resolution (using a 2-field record)
(RFM v4.35 onwards:
RESSPC=0 not supported)
The RESSPC resolution applies to the output spectra -
if an ILS convolution
is required the RFM by default performs internal calculation at
0.0005 cm-1 resolution
(use the FIN Flag to alter this)
or the closest sub-multiple of the output
A warning message is printed in the rfm.runlog file if spectral lines at
required tangent level are unlikely to be unresolved at the
resolution selected for the fine-mesh calculation (ie
RESSPC in the absence of any ILS convolution).
The maximum resolution RESSPC is determined
by the value of MAXFIN parameter
(RFM v5 has no such limit)
The limiting values for LOWSPC and UPPSPC are
set in spcchk.for
(spcchk_sub.f90 in RFM v5)
and are basically just sanity checks
(although a value 0cm-1 causes problems).
If the GHZ Flag is enabled the
requested spectral range and resolution are converted to wavenumber
internally using the VLIGHT value in phycon.inc
(phycon_dat.f90 for RFM v5)
(30GHz approx 1cm-1)
and the calculation proceeds in the same way.
RFM v4.35 onwards:
irregular output grids can be specified (although not for spectrally
convolved outputs - ILS or
AVG flags) using FILSPC as
either a .grd file or a precalculated
RFM output spectral file
already on the irregular grid.
This is a single, user-specified, unlabelled spectral range
This is a pair of labelled spectral ranges @ 40pts/wno.
1020 1030 0.01 ! 1020-1030 cm-1 @ 0.01 cm-1 resolution
The next example uses files to specify range/resolution
BandA 685 970 0.025 ! Band A
BandB 1215 1500 0.025 ! Band B
See Example in Spectral Files for
structure of bspc.grd.
A rad_10000.asc ! Clone range/res from previous RFM output
B bspc.grd ! Irregular grid output