*.tmc files

Description:

I won't fully define what a *.tmc file is, because I don't actually know, and it's probably already done in nort's DAS docs. But I will define the run-type commands that the Kinetics tmc files will need to support. The basic syntax is as follows:

For test runs:

run Test [subtype] [algorithm]

Calibration runs have the following syntax:

run Calibration [caltype] [algorithm]

(subtype either needs to be on the command line or in run.schedule or run.defaults)

Spectra runs have the following syntax:

run Spectra [manifold] [molecule] [IRdetector] [algorithm]

Required either on line or in file: manifold, molecule, IRdetector

Product studies have the following syntax:

run ProductStudy [manifold] [molecule] [radical] [IRdetector] [RadDetector] [algorithm]

Required either on line or in file: manifold, molecule, radical, IRdetector, RadDetector

Kinetics studies have the following syntax:

run Kinetics [manifold] [molecule] [radical] [XSdetector] [RadDetector] [flowtype] [algorithm]

Required either on line or in file: manifold, molecule, radical, IRdetector, RadDetector, flowtype

Details:

manifold is a number, which will be used to select the correct line in molecule.list. subtype is arbitrary for tests, but should be in the tmc file for calibrations. molecule is also used to select a line in molecule.list, but it can either be a number or a word. radical is an arbitrary word, but should correspond (eventually) to directories on the Linux side. The various detectors are arbitrary, but perhaps mattson, LIF, bruker, ringdown, and UV should autocomplete. flowtype is either "recirc" or "singlepass". The algorithm just allows runtime specification of the algorithm.

Examples:

run Test OH_plume run.alg
run Calibration zero zero.alg
run Spectra 3 ethane OH mattson run.alg
run ProductStudy 2 ethane OH mattson LIF run.alg
run Kinetics 1 cyclohexane OH ringdown LIF singlepass run.alg

See also:

• molecule.list
• run.schedule
• interact
• dataRecv