Usage : BLMLOG is the Java Open Access Client (OAC) process which
logs Booster loss monitors across cycles and time.
You can view log files for BLMLOG in the directory
'daesrv\\engines\files\oac'.
Restart: BLMLOG is restarted when its DAE is restarted.
Beams document database:
http://beamdocs.fnal.gov/DocDB/0006/000667/001/BLMLog.pdf
Documentation from gov.fnal.controls.daq.oac.clients.blmlog:
This is the Booster event cycle loss monitor collection and logging module.
For Booster reset events, 11-17 and 19, 1c, 1d, 10 (sum) and an undefined (12
events) several devices support the collection of data across the cycle from
millisecond 1-40. A job is started to periodically collect the following: the
sum of resets by reset type, B:LMSCE the sum of charges across a 40 mSec
interval by reset type, B:LMSCHG 75 loss monitor sums by reset type and time
within the cycle (1-40) The raw, incrementing data is logged into array
elements 0-11 where resets 11-17 are in array elements 0-6, reset 19 is in
array element 7, reset 1c and 1d are in array elements 8 and 8 respectively,
and reset 10 (sum) is in array element 10 and array element 11's content is
undefined. The data is logged only when collection completes successfully and
different from the previous collection. The timestamps for all raw data are
identical and equal to the collection time. The raw data is also logged on
the first data collection after startup.
The difference data is logged only if after collecting all the data and
comparing it to the previous collection: the collection completed without
error a previous collection exists supporting delta calculations the sum of a
reset has increased and the charge for that reset has increased What is
logged is: the number of resets by reset since the last collection when
non-zero the increase in charge since the last collection by reset when
non-zero the loss monitor increase for each millisecond interval since the
last collection by reset, i.e. B:LMS021[11] would log 40 data values each a
millisecond apart for reset type 0x1d. The array elements used for the
difference data matches the reset number, i.e. resets 11-17(hexadecimal) are
logged into array elements 16-23. The timestamps for all difference data are
different by 1 mSec and begin at the collection time. Totals are also logged
using devices B:LMRSUM, B:LMCSUM, and B:LMLSUM for resets, charge, and loss
respectively. B:LMRSUM is a single element device, B:LMCSUM and B:LMLSUM each
have 40 elements. The reset events are also logged to device B:LMEVNT. The
reset event numbers will be logged by their count and all timestamps are at
the collection time.
The device Z:BLMLOG is logged with a value of 1.0 on each successful
collection and logged with a value of 0.0 when the collection was in error.
Java data loggers log doubles with millisecond timestamp resolution. When
sending data back to a VMS client, time is converted from Zulu time with
millisecond resolution (long) to local time with 1 second resolution (int)
and values are converted from IEEE doubles to VMS floats.
Keeper: Kevin Cahill
OAC Node: due06
Now: Fri Aug 29 01:53:30 2008