class SegGener : public DatEnv, TrigClient

Generate segment database entries from OSC conditions.
SegGener generates entries to the segment meta-database table based on conditions evaluated by the OperStateCond (OSC) class. The user specifies one or more segment types to be evaluated in a configuration file. The segment may be asserted either at all times that a condition is true, or from the onset of a start condition to the onset of a stop condition. A segment table row is generated each time a stretch of data is observed where the specified condition is true. SegGener will optionally split the segments into spans of a given maximum length. This allows the segment to be generated before the condition returns to false in cases where the condition remains asserted over long periods of time.

Running SegGener

The SegGener command line is as follows:

      SegGener -conf <config-file> -osc <osc-defs> [+seg] [-htfile <report>] 
     

where:
<config-file> Configuration file name
<osc-defs> OSC definition file name
<report> Html report file name
+seg Write segment to LDAS meta-database (via TrigMgr).

The SegGener configuration file

Each line of the SegGener configuration file defines one segment to be evaluated and (optionally) written. Each configuration file line has the following format:

      <segment-name> <segment-version> <start-cond> [<stop-cond>] \
                     [-limit <max-time>] [-file <seg-file>]
     

where <segment-name> is the segment name, <segment-version> is the segment version number. The segment condition is defined by <start-cond> and <stop-cond>. If <stop-cond> is defined, the Segment is asserted from the onset of <start-cond> to the onset of <stop-cond>. If <stop-cond> is not defined, the segment lasts as long as <start-cond> is asserted. The -limit argument specifies the maximum time (<max-time>, in seconds) for a single segment table entry. If a segment condition lasts longer than the specified time, SegGener will write multiple segment table rows after the segment rows with durations less than or equal to the specified maximum. The -file argument specifies a file name (default directory is $DMTHTMLOUT) to which one line will be appended for each segment.

SegGener outputs

Web readable report file

SegGener produces a web readable report file with a table containing the current segment definitions and a statistical summary of the meta-database rows produced by each segment type. The segment report is in html format and is written to $DMTHTML/Segment_List.html. The segment statistics table has the following entries:
Column Contents
Segment Group Name of the segment group to be written
In Segment Indicates whether the segment condition was true at the time the report was written
Start Condition OSC condition marking the start or duration of the segment.
Stop Condition OSC condition marking the end of the segment (or '-' if the segment is defined by a single condition)
Live Fraction of the time that the segment is asserted (in \%)
Segments Generated Number of segments that have been generated.
Time Limit Maximum time of a single segment entry.

Segment metadata

Each detected segment is sent to the Trigger Manager to be written to the LDAS meta-database if the +seg command line argument is specified.

Segment list file

In addition to the metadata, the segment may be optionally written to an ascii segment list file. Each line in the list file contains the line number, sstart time, stop time and duration for a single segment or segment fragment. The line is appended to the file at the same time the segment info is sent.

Author:
John Zweizig
Version:
1.1; Last modified June 10, 2002

alphabetic index hierarchy of classes


generated by doc++