You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

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

  1. Data monitoring folks make a CCB request to deploy new limits. Wait for that to be approved.
  2. Figure out where the limits are:
    1. 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 job)
    2. grep alarmCfgBase config.py (currently /afs/slac/g/glast/ground/releases/volume11)
  3. Go there, then AlarmsCfg
  4. Check out the code
    1. Currently in CVS at /nfs/slac/g/glast/ground/cvs
    2. cvs co -r AlarmsCfg-07-00-10 dataMonitoring/AlarmsCfg (or whatever the current version is)
    3. mv dataMonitoring/AlarmsCfg AlarmsCfg-07-00-10
  5. Remove the current links for test, dev, and prod, and replace them with the new version
  6. Update the CCB request

 

  • No labels