Data Handling Monthly Meetings

Meetings are held monthly via teleconference on first Thursdays, 11:00 Pacific time in the Ballam Conference Room at SLAC. The meetings will also be broadcasted via EVO system. We do not use video.
Please avoid an open mike, which may cause echoes. See the evo help.  For further information be sure to have a look at the VRVS Etiquette page.

Previous Years

• 2009
• 2008
• 2007
• 2006
• 2005

July 19 2012

• Announcements
  • Please add computing outages to the List of upcoming outages

• Astroserver and run quality
  • Criteria to load data into the astroserver: how do we handle bad data?
  • Discrepancies from P120 and P130

• Review outstanding FDH JIRAs

• Hardware changes (Tom)
  • Update on NFS disk space upgrade
  • Update on glastlnx server replacement

• Support for DQM
  • Timeout for DQM application
  • Is it possible to have more meaningful messages from the log watcher?
  • Missing log watcher messages from tkrTrendAlarm and verifyComplete
  • Status of the Bad Time Intervals interface (unified timing convention, etc...).

June 14 2012

• Announcements
  • Please add computing outages to the List of upcoming outages
  • New JIRA project for Fermi Data Handling
  • Leap second June 30 -- do we need to do anything?

• Astroserver and run quality
  • Criteria to load data into the astroserver: how do we handle bad data?
  • Discrepancies from P120 and P130
  • Possible improvements to the run quality pages.

• Pass8 Dual Tuples (Alex)

• Hardware changes (Tom)
  • Update on NFS disk space upgrade
  • Update on glastlnx server replacement

• Support for DQM
  • Timeout for reports application
  • Is it possible to have more meaningful messages from the log watcher?
  • Missing log watcher messages from tkrTrendAlarm and verifyComplete
  • Status of automatic shift reminders.
  • Status of the Bad Time Intervals interface (unified timing convention, etc...).

May 10 2012

• Hardware
  • The plan to replace the sulkys.
    • Existing NFS server allocation
    • Strawman proposal for new allocation (version 0)
  • Ideas for replacing the glastlnx machines.
    • Summary of machine characteristics
    • Existing compute server allocation
    • Whether and how to consolidate?
      • A snapshot of usage
      • Some issues to consider
  • How should we organize ourselves for planned computing outages?

• Astroserver and run quality
  • Criteria to load data into the astroserver.
  • Possible improvements to the run quality pages(pic1, pic2).

• Support for DQM
  • Is it possible to have more meaningful messages (pic) from the log watcher (pic)?
  • Missing log watcher messages from tkrTrendAlarm and verifyComplete
  • Status of automatic shift reminders.
  • Status of the Bad Time Intervals (pic) interface (unified timing convention, fix plot axis, use normalized transient rate plot...).

• Miscellanea
  • Can we improve communication for pipeline work?
  • New JIRA project for Fermi Data Handling
  • Problems with the data catalog (see jira)
  • Any idea what happened with robots.txt? do we need to password-protect the pipeline web interface?