As the instrument evolves, alarm limits for data monitoring sometimes have to be changed. New limits are developed by the data monitoring team in cooperation with the subsystem experts, and deployed by the L1 maintainers. 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 request to 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 out where the limits are:
Go to the L1 install directory (currently /afs/slac.stanford.edu/g/glast/ground/PipelineConfig/Level1/5.9)
grep alarmCfgBase config.py (currently the current location is /afs/slac/g/glast/ground/releases/volume11/AlarmsCfg)