RFM Runlog File

06AUG17

Every run of the RFM will create a file rfm.runlog (changed to rfm.log from RFM v5 onwards) (plus any specified Run ID). This file logs all details of the particular run.

The file contains 3 types of record: Status Messages, File Header Records and Section Header Records.

Status Messages

Message Meaning
R-RFM: ... General status (also printed to terminal)
I-ABCDEF: ... Info from subroutine ABCDEF
W-ABCDEF: ... Warning from subroutine ABCDEF
F-ABCDEF: ... Fatal Error in subroutine ABCDEF (also printed to terminal)

File Header Records

Whenever an
input file is opened, first a info status message is printed to the rfm.runlog file giving the name of the file about to be opened, then, if opened successfully, the first record of the file is also printed to the rfm.runlog file.

For this reason, the first record of each input file should contain some meaningful information (preceded by !, indicating a comment).

Section Header Records

Each driver table record containing a section header (eg *HDR ... ) is also printed in the rfm.runlog. Similarly the profile identifiers (eg *HGT) from atmospheric profiles loaded in the *ATM section (these are indented a couple of spaces to distinguish them from Driver Table sections).

Example

A run with the
example Driver Table would generate the file rfm.runlog starting as follows:
R-RFM:    Program RFM v4.25
I-OPNFIL: Opening file: rfm.drv
  ! 01AUG05 Example Driver Table
*HDR                
    RFM run using Driver Table v.01AUG05
*FLG
I-INPFLG: Enabled flags: fov ils rad
...etc