IFR cron jobs
- Fast monitoring (Enrico): runs on
babarifr. You can enable/disable it modifying the trscrontab file. Are 5
different jobs that run at different time. ( /afs/slac.stanford.edu/g/babar/detector/ifr/bin/runFMon.auto
- Efficiency History ( Diego & Riccardo):runs
on babarifr. There are 2 jobs: one on trscrontab and the second one on crontab
bbr-dev118. Again you can easily disable them modifying the trscrontab
and the crontab file.
A brief documentation is available at the address:
- Dark currents and single rates history
(Chiara): the script /afs/slac.stanford.edu/u/ec/babarifr/ifr/monitor/makemonplots runs from bbr-dev118as babarifr at 4am daily.
- FEC history (Chiara):running from bbr-farm04 as babarifr every 10 minutes.
The script is /afs/slac.stanford.edu/u/ec/babarifr/DetectorAnal/monitorjobs/feclog-auto.sh
and uses the kumac fechistory.kumac located in the same directory.
An automated mail message is sent to babarifr whenever the number of new silent or hot fecs
in the checked run (wrt a reference) is more that 5 in any crate.
- Bubblers history (Chiara): the script /afs/slac.stanford.edu/u/ec/babarifr/ifr/monitor/makemonplots-bubblers runs from bbr-dev118 as babarifr at 6am daily.
- IFR Quality Assurance:
(Chiara) DQA is performed on a weekly basis.
The RQM will post a HN pointing to the list of processed runs that needs to be checked for that week.
For the IFR the script /afs/slac.stanford.edu/u/ec/babarifr/DetectorAnal/monitorjobs/IFRQA-auto.sh
runs as a cron job every Wednsday at 4:00am.
The script verifies that a new list of runs is present and performs few checks
on the existence and validity of the ER hbook files which are used to produce
A mail is sent as summary report upon completition of the job.
To see scheduled jobs: trscrontab
-l (crontab -l)
To edit trscrontab
trscrontab -e (crontab -e)
07 December 2004, 23:43:27
For any question, please contact: