5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter.

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson 5. Data Manager 1

1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  The LHCb Shift Crew training consists of several courses 1.Introduction 2.Safety 3.Basic Concepts 4.Running LHCb 5.Data Manager 6.Shift Leader  All of these course are subjects to changes  This course is intended to describe the work of the Data Manager Tasks Tools  Judging data quality is a difficult but VITAL task requiring experience  Consult with people for any anomaly you observe or doubt you have  Make sure you are aware of the known problems when arriving for a batch of shifts  Your job is the basis for rating the files/runs for physics analysis!  Please comment on missing or unclear topics, errors. Don’t hesitate to ask questions 2

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Assist Shift Leader Watch his displays, learn also how to monitor the DAQ and Slow Controls, Detector Safety System Follow experimental conditions on permanent displays Calling experts In case of crisis, like Safety Alarm or DAQ troubles, the DM can replace the SL at the Run Meeting  As Data Manager you will mainly use the following tools Histogram Presenter Trending Tool Event Display Run Database Problem Database (Report problems together with expert if possible)  Repository for problems affecting the data quality Elog  Make sure you feedback anything that is not understandable or unclear, absolutely vital  Don’t ignore something because you don’t understand it! Contact Online Data Quality Coordinator (Olivier Callot) or Run Coordinator daytime 3

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  This is of vital importance during the ramp and adjust for physics as some detectors are switched on already and during the first minutes of a Physics fill, as you can immediately detect major disasters before the automatic tasks check the data  During Physics Runs Look at histograms by regularly browse through the pages in the “Shift” folder pages in the Histogram Presenter to spot abnormal distributions as soon as possible  Non working part of a detector, noisy channel are easy  Strange distribution, in particular in the trigger, are less easy. Look at the recorded events on the Event Display. Spot basic problems such as large background, or parts of the detector not responding or noisy. Look at trends of rates and detector conditions using Trending Tool  “Shift” folder with well-documented trends not yet in place  End of Run A Run might be restarted for a variety of reasons Check writing of files and data transfer to Offline and Castor (permanent storage) using the Run Database display  If there are problems, contact (after checking with your SL) the offline control room where a production shift is monitoring the data processing. 4

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Make sure you don’t ignore a problem because you don’t understand it Don’t be afraid to ask: “Gas flow seems to be stopped in the VELO?!....”  Reporting steps 1. Consult with Shift Leader and other experts that may be around 2. Make sure it is not a know problem or a consequence of some special run settings 3. Contact the relevant expert including Run Chief to discuss the severity and how to solve it 4. Make an entry in the logbook preferably with a screen shot 5. Register problem in Problem Database with link to ELOG entry  Reporting from Presenter allows both making an ELOG entry with screen shot of the erroneous plot and an entry in the Problem Database with your comment automatically. 6. If problem just occurred, restart Run (CHANGE_RUN) as soon as possible to isolate the problem as much as possible 5

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Monitoring jobs run on dedicated Monitoring Farm/Reconstruction Farm Event Spying is on best effort, not all events pass there Monitoring tasks can crash/hang  No entries at all in a histogram is not necessarily bad data  Consult with Shift Leader 6

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Allows you to view histograms produced by the various tasks. There is normally a copy running permanently, on a dedicated terminal, for regular checks.  Presenter is started with the command presenter. Presenter should normally run in the ONLINE mode. It can also run in a HISTORY mode, displaying histograms from a given run, fill or time interval.  Be sure you are in the ONLINE mode... Histograms in the “Shift” folder has descriptions and instructions  Histograms should be compared to the reference histograms bearing in mind factors such as Recent and temporary faults that have appeared since the creation of the reference histograms. Known detector problems Any run specific problems which may temporarily alter the appearance of the histograms such as high backgrounds from LHC, etc.  Learning how to use the Presenter will be one of the main goals of your first shifts. 7

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Login to ‘plus’  /group/online/presenter/run_presenter.sh 8 Load previous/ Next page Start/stop page refresh Report to Log Clear histograms Partition

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson 9

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Reference histograms 10

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Example of problem registered in ProblemDB as ‘OK’ 11

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Example of problem reported in ProblemDB as ‘Severe’ 12

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  No “Shift” folder yet with documented trends 13

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Useful for checking the coherence of the complete detector response. Check for noise in the sub-detectors  Started on a ‘plus’ node with the display on a dedicated terminal with command evdisp  The standard display mode is AUTOMATIC, i.e. a new event is displayed every 5 seconds. You can then click on the pause button to keep any specific event. You can also select a MANUAL mode where you click on a button to see the next event. There are options to select events to be displayed by type, trigger mask, etc...  Be sure that the display is running in ONLINE mode during data taking. Report all problems and suggestions to Philippe Ghez 14

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Screen shots! 15

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Check that the ‘real’ runs are closed and sent to Offline 16

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Web link for Problem DB: http://lbproblems.cern.ch/http://lbproblems.cern.ch/  It consists of a list of problems potentially affecting data quality Title is a short text, used later to list problems and should be concise and meaningful. System is selected from a predefined list and is mainly the list of LHCb sub-systems. Severity is selected from a predefined list, and defaults to 'unknown'. Time Range is defined as time Comment is text information including Author and optional Weblink. This is a write-once comment in the sense that the text can't be modified, only a new text can be added to correct it. Be careful and proofread your input before committing. Note that the database can be edited by managers in case of serious need. Please contact Olivier Callot, Jose Caicedo or Run Coordinator  History of entries displayed 17

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Web link to logbook from Problem Report 21

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter 8. Event Display 9. Run & File Status 10. Problem Database 11. Logbook R. Jacobsson  Alright, you are now graduated Data Managers!  Thanks for volunteering! You are invaluable for Our Physics Goal! 25

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter.

Similar presentations

Presentation on theme: "5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter.

Similar presentations

Presentation on theme: "5. Data Manager 1. Introduction 2. Data Manager Duties 3. Quality Checking 4. Problem Reporting 5. Data Monitoring 6. Histogram Presenter 7. Trend Presenter."— Presentation transcript:

Similar presentations

About project

Feedback