Page History
...
- Data monitoring folks make a CCB request to deploy new limits. Wait for that to be approved.
- 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 job)
- grep alarmCfgBase config.py (currently /afs/slac/g/glast/ground/releases/volume11)
- Go there, then AlarmsCfg
- Check out the code
- Currently in CVS at /nfs/slac/g/glast/ground/cvs
- cvs co -r AlarmsCfg-07-00-10 -d AlarmsCfg-07-00-10 dataMonitoring/AlarmsCfg (or whatever the current tag is)
- Remove the current links for test, dev, and prod, and replace them with the new version
- If possible, switch the links in between deliveries. It is acceptable to have a mix of old and new configs for a run
- Update the CCB request
| Info |
|---|
Related articles
| Content by Label | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| hidden | true |
|---|
...
Overview
Content Tools