Versions Compared

Old Version 5

changes.mady.by.user Maria Elena Monzani

Saved on

compared with

New Version 6

changes.mady.by.user Maria Elena Monzani

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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 )

  1. Data monitoring folks make a CCB request to deploy new limits. Wait for that to be approved.
  2. Figure To 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 job9)
    2. grep alarmCfgBase config.py (currently /afs/slac/g/glast/ground/releases/volume11/AlarmsCfg)
  3. Go there, then AlarmsCfgCheck out the codeCurrently in CVS at /nfsto the location of alarmsCfg (currently /afs/slac/g/glast/ground/releases/volume11/AlarmsCfg)
  4. Check out the code from github:
      Code Block
      /cvscvs co -r AlarmsCfg-07-00-10 -d AlarmsCfg-07-00-10 dataMonitoring/AlarmsCfg (or whatever the current tag is)
  5. Remove the current links for test, dev, and prod, and replace them with the new version
  6. If possible, switch the links in between deliveries. It is acceptable to have a mix of old and new configs for a run
  7. Update the CCB request
...