CVTFOF

This process is stage 4 in the ODR Pipeline. It is an OSF triggered process and its purpose is to convert Merged-All-Points FOF files transferred from CCS into the Change-Only Telemetry Subset Files and Telemetry Error files that are required by the OMS Pipeline. When a FOF Class OSF is set to "W" in the CV stage column, the CVTFOF process is triggered.

Be aware that there is a "GAP_TOLERANCE" mnemonic in the CVTFOF resource file that determines if BGAP/EGAP messages are written to Telemetry Error Files; i.e., .ER* files. Telemetry Gaps having a duration less than or equal to the value of the GAP_TOLERANCE mnemonic will not have BGAP/EGAP messages written to their respective .ER file. If a GAP_TOLERANCE mnemonic is not specified in the resource file, a default value of 5 seconds will be assumed.

For additional information on the CVTFOF process, reference the ODR Pipeline Reference Manual

CVTFOF Process Modes

Interactive Mode

       CVTFOF i -f Tyyyydddhhmmss.mrg    (typed into command line)

              where: CVTFOF = command name
                          i = denotes interactive processing
                         -f = denotes file specification of FOF file to convert
                              follows
         Tyyyydddhhmmss.mrg = naming convention for decompressed FOF files 

      *** Note *** - Interactive commands assume that the mnemonics assigned in the
                     OPUS_DEFINITIONS_DIR:NULL.PATH file will be used.

Pipeline Mode

       CVTFOF -p opus_definitions_dir:your.path  (in task line of resource file)

              where: CVTFOF = command name
                         -p = denotes path file specification follows

                     opus_definitions_dir:your.path = path file to use

CVTFOF Process I/O

       INPUT:
          ODR_FOF_DIR: Tyyyydddhhmmss.mrg - decompressed FOF files 

       OUTPUT:
          OMS_DATA_DIR: - Symdhhmm.vc*_new - Intermediate Change-Only Telemetry
                                             Subset Files while a FOF file is
                                             being processed.  These are renamed when
                                             FOF file processing is complete
                          Symdhhmm.er*_new - Intermediate Telemetry Error Files
                                             while a FOF file is being processed. 
                                             aThese re renamed when FOF file processing 
                                             is complete
                          Symdhhmm.vc*_fof - Final Change-Only Telemetry Subset
                                             Files when FOF file processing is
                                             complete
                          Symdhhmm.er*_fof - Final Telemetry Error Files when
                                             FOF file processing is complete

CVTFOF Process Error Handling

Any errors that occur while converting a FOF file cause the FOF OSF to be set to "F" in the CV stage column. Error messages are also posted to the CVTFOF Process Log File in the OPUS_HOME_DIR. Even though a FOF file may be partially processed and produce valid Telemetry Subset files and Telemetry Error files, processing of the file is not considered successful unless the whole file is processed. In scenarios where valid Telemetry Subset files and Telemetry Error files have been generated from a FOF file but an error occurs in later processing of the file, none of the Telemetry Subset files or Telemetry Error files generated will be renamed from the _new extionsion to the _fof extension. Also, records will not be inserted into the FOFSUB_TABLE table for any of the Telemetry Subset files that were generated.