ManPage: ISM - ISM_dat2vec.com

Name

ISM_dat2vec.com - Convert Data files to Vector files

Synopsis

@slc_ism:ISM_dat2vec dpath /opath=op
		/rmin=rmi /rmax=rma /tmin=tmi /tmax=tma
		/runmerge /droprun0 /itrace /otrace /summary
		/jbus

Description

ISM_dat2vec.com reads selected data files from the directory dpath and produces a set of vector files in the directory given with the /opath qualifier.

Parameters and qualifiers:
dpath Directory specification for data files. Required parameter.
/opath=op Directory specification for vector files. If omitted, all vector files will be created in the current working directory.
/rmin=rmi Lowest run number to accept (given as up to 4 digit integer).
/rmax=rma Highest run number to accept.
/tmin=tmi Earliest time stamp to accept.
/tmax=tma Latest time stamp to accept.
/runmerge All entries for a given run in the data files are merged into one entry for this run in the vector files. The time stamp reflects the latest time stamp. Only consecutive entries for a given run number are merged, so a sequence of entries for run 0 interruped by a some entries with a non-zero run number will cause two entries for run 0 in the vector files. This qualifier is therefore often used together with /droprun0.
/droprun0 All entries for run 0 are dropped, thus all entries produced when the data recording of off are removed from the vector files. This produces together with /runmerge a pure run statistic.
/itrace Lists the name of all input data files to standart output as they are processed.
/otrace Lists the name of all output vector files to standart output as they are written.
/summary Lists a sumary of the found information (and written vector files). For detector monitoring data the is arranged as a ring/module matrix like
                            1                   2
          1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
   i 1 :  . . . . . . . . . . . . . . . . . . . . . . . .
   i 2 :  * . * . * . * . * . * . * . * . * . * . * . * .
   i 3 :  . . . . . . . . . . . . . . . . . . . . . . . .
   i 4 :  * . * . * . * . * . * . * . * . * . * . * . * .
   i 5 :  . . . . . . . . . . . . . . . . . . . . . . . .
   i 6 :  * . * . * . * . * . * . * . * . * . * . * . * .
   i 7 :  . . . . . . . . . . . . . . . . . . . . . . . .
  
   ...

indicating for each signal, ring and module whether data has been found and a vector file has been written. The symbols mean
    .    No data, no expected
    *    Data, where data was expected
    M    No data, where some was expected   (MISSING)
    E    Data, where none was expected      (EXTRA)
    L    no physcis counts, only Pulser/Laser
    P    no pulser/laser, only physics
The 'M' and 'E' symbols are highlighted in red, 'L' and 'P' in blue, for easier recognition.
/jbus Process JBus data rather than detector monitoring data.

The values for the /tmin and /tmax qualifier can be in any of the VMS time formats, either as absolute, delta or combination time.

Type Format Example
absolute dd-mmm-yyyy:hh:mm:ss 19-jan-1998:12:00
delta dddd-hh:mm:ss -2-0
combination absolute_time - delta_time today-2-0

Please keep in mind the following oddities when specifying a time:

Examples

$ set def slc_ism: $ @ISM_dat2vec slc_save: /opath=slc_tmp: will process all files in slc_save: and produce a set of vector files in slc_tmp: which cover the whole available time interval. $ @ISM_dat2vec slc_save: /opath=slc_tmp: /runmerge/droprun0/rmin=4000/rmax=5000 selects in slc_save: the data corresponding to runs 4000 to 5000, combines all entries for a given run and drops all entries produced when the data recording was off (indicated by a run number of 0). $ @ISM_dat2vec slc_save: /opath=slc_tmp: /tmin=-1-0 $ @ISM_dat2vec slc_save: /opath=slc_tmp: /tmin=-1-0 /jbus selects in slc_save: the data taken during the last 24 hours and produces the vector files for detector and JBus data.

See also

ISM_v1s_data,

Back to INDRA Slow Monitoring


Last update: 13-Jun-1998
Walter F.J. Müller