tri_logr_spec.12

Purpose:

Generates a CyFlex logr_spec file. The spec file will contain all the data from the logr_spec_in file + if any ECM_DATA_SOURCES are specified within the tri_specs.dat file,
the @CSAR_LABEL keyword will be added with the appropriate keyword + all tri_specs.dat DATA_CHANNELS in the scan list + list of pnp logical variables if pnp subsystems are specified + list of variables for each specified subsystem from the subsystems file

Enter:

tri_logr_spec.12 <logr_spec_out=logr_specO> <logr_spec_in=logr_specI> <tri_specs=tri_specs_file>

Where:

logr_spec_out

Specify the pathname of the logr spec output file.

logr_spec_in

Specify the pathname of the logr spec input file.

tri_specs

Specify the pathname of the tri specs file.

Example:

tri_logr_spec.12 logr_spec_out=/esvd_data/CTH_EUL/logr_spec_12.dat  
                       logr_spec_in=/esvd_data/specs/logr_spec.base 
                       tri_specs=/esvd_data/CTH_EUL/tri_specs.dat  

Notes: 

       – /e/<t>/          ‘logr_spec_12.dat’  
      – /e/<s>/          ‘logr_spec.base’
      – /e/<t>/          ‘tri_specs.dat’  
 
      where:  

e esvd_data
t test plan id of test
s specifications that apply
‘ ‘ Contains specifications that apply to all tests ultimately replaced by the actual filename when the script ‘tri_file_name.12’ is run.

Ensure all file paths are valid and accessible as the program will exit on file open errors.

See Also: