Difference: DataQualityMinutes080822 (2 vs. 3)

Revision 32008-08-22 - unknown

Line: 1 to 1
 
META TOPICPARENT name="DataQuality"

Minutes of the Data Quality Meeting of Friday 22 August 2008

Line: 14 to 14
 
    • Once a problem is identified, an expert is asked to provide an updated Brunel or databse (who tags?) and a test job is submitted. Philippe offered to set up an infrastructure to do so.
  • The DQ shifter should be in charge of the day-to-day job: look at reconstruction histograms, make sure all is OK, follow up that calibration is done, submit and analyses control jobs.
    • The DQ shifter would have close contact with the offline shifters and work in the offline control room.
Changed:
<
<
  • A DQ expert on piquet should have the long term overview of what is hoing on. He would run the daily DQ meetings and be responsible for the decisions.
>
>
  • A DQ expert on piquet should have the long term overview of what is going on. He would run the daily DQ meetings and be responsible for the decisions.
 
  • The daily meetings should not be linked to run meetings as previously discussed. The DQ meetings would rather be in the afternoon, after the offline computing meetings, in the offline control room.
    • The DQ shifter and experts would either attend the run meeting, or be informed about the problems discussed. They would report at the DQ meeting for further discussion.
  • It is agreed that anyone should be allowed to report problems in the Problems Database. LHCb shifters should be encouraged to do so. Subdetector experts can also report problems, but it shuld be assumed that only experts would do so, as there would be a risk if having only the people reporting problems who would then be assigned it for solving.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback