Daily jobs

• Check calibrations for the most recent runs
• Monitor usage of the Oracle DB (Once every hour)
• Monitor data handling operation (Beginning, middle, and end of shift)
• Monitor physics output of the detector (once a day)
• Respond to emails to CDF_SOFTWARE_HELP.
  Either answer the question yourself , reply to the email by asking for more information such as node name, release number, full path of executable and tcl file (see How to report a problem ), or ask an expert on the Run II mailing list to respond.
  Give the experts 24 hours to respond before bugging them, many times Pasha or Liz or one of the other experts will respond on their own.
• Bookkeeper for CDF_SOFTWARE_HELP.
  You will need to logon cdfsga as cdf-bugs (using ssh -l cdf-bugs cdfsga AFTER having obtained a kerberos ticket as yourself on a fnal.gov machine) and cd to bug_tracking. It is mostly about keeping track of the different mail treads for open cases and filing finished cases in their appropriate area. Follow the white rabbit to get instructions on what you should do.

Record all the actions in CDF offline e-log

Other jobs

• Building patched version of the Production Executable.
• Running the 10K Production Executable Test Run and checking the results
• Bilding the ProductionExe tarball
• Summarizing results of 100K tests
• Testing binaries with Purify
• Debugging Crashes from Farm
• keep the documentation up-to-date.
  The html's in the Farmtools/doc area should be reposited in cvs from the cdfopr@cdfsga account by issuing cvs commit FarmTool from the 'cd /cdf/www/internal/upgrades/computing/operations/offline_shifts' area. You need to first "ssh -l cdfopr fcdflnx3", then "~/ticket" to get a kerberos ticket as cdfopr, then "ssh -l cdfopr cdfsga" and you will have the cdfopr ticket on cdfsga.

---

Last updated by Pasha Murat