As the instrument evolves, alarm limits for data monitoring sometimes have to be changed. The New limits are developed by the data monitoring team in cooperation with the subsystem experts, and deployed by the L1 maintainersdo this. L1 uses symbolic links with fixed names pointing to the current version so they can be changed without changing L1.
Step-by-step guide (updated on )
Data monitoring folks make a CCB requestto deploy new limits. Wait for that to be approved..
The following steps MUST be performed from a rhel6 node (do NOT attempt to deploy alarms on the S3DF).
To figure Figure out where the limits are:
Go to the L1 install directory (currently /afs/slac.stanford.edu/g/glast/ground/PipelineConfig/Level1/5.6, look for L1ProcROOT in the environment dump in the log file for any L1 job9)
grep alarmCfgBase config.py (currently the current location is /afs/slac/g/glast/ground/releases/volume11/AlarmsCfg)
Go
there, then AlarmsCfg
to the location of AlarmsCfg and check out the code from github:
Code Block
language
bash
export tag=AlarmsCfg-07-00-37 #or whatever your tag is
cd /afs
Check out the codeCurrently in CVS at /nfs
/slac/g/glast/ground
/cvs
cvs co -r AlarmsCfg-07-00-10 dataMonitoring/AlarmsCfg (or whatever the current version is)