- General information
- Data readiness
- Calibration
- Databases
- Quality Assurance
- Online QA
- Proposal and statements
- Offline QA
- QA Shift Report Instructions
- STAR QA Documentation
- Configuring AutoQA for subsystems
- Fast Offline QA Histogram References and Descriptions
- Fast Offline QA Shift Report Preparation and Instructions for Run 8
- Fast Offline QA Shift Report Preparation and Instructions for Run 9
- Information for Fast Offline QA Shifts - Run 8
- Information for QA Shifts
- Integrating QA Histograms into Makers
- Manual generation of QA histograms
- Offline QA Histogram Trigger Types
- Offline QA Shifts (Y2000 run)
- Other Expert contacts and links
- QuickStart Instructions for the Auto QA Browser - Run 8
- QuickStart Instructions for the Auto QA Browser - Run 9
- STAR QA Documentation
- STAR QA for Offline Software
- STAR QA links and contacts
- Summary of Fast Offline QA Shift Duties - Run 8
- Summary of Fast Offline QA Shift Duties - Run 9
- Technical Documentation of the Auto-Combine Function
- Technical Documentation of the Offline QA Browser
- Technical Documentation of the Offline QA Shift Reports
- Reconstruction Code QA
- Run QA
- Grid and Cloud
- Infrastructure
- Machine Learning
- Offline Software
- Production
- S&C internal group meetings
- Test tree
Summary of Fast Offline QA Shift Duties - Run 10
Updated on Tue, 2009-12-15 13:10. Originally created by ray on 2009-12-15 13:10.
Under:
- Review in detail the set of histograms for the Offline QA Shifts for Fast Offline Data Production (highest priority); the minimum requirement is 1-2 file sequences or 'jobs' per Experiment Run ID number and trigger collection, e.g. st_physics, st_mtd, st_upsilon, minbias, high tower, etc.
- Note that for Au-Au one file sequence is usually sufficient however you may need to use the "combine several jobs together" option in order to get enough statistics.
- Write a useful and informative Offline QA Shift report using a web-based form noting especially any and all suspected problems with the detectors, calibrations, and reconstruction. The report will be archived and the summary sent to 'starqa-hn' hypernews automatically.
- Press the "MARK" button for all fast offline data runs you examined while on shift.
- Review the Online Run Log information and comments for each real data production job you examine and summarize the Run/Data Quality status based on the Run Log information and the QA examination results by marking the job as "Good" or "Bad." Jobs will normally be considered "Good" even when there are hardware outages or calibration/reconstruction issues. Please check with the QA experts before marking jobs as "Bad."
- Notify the appropriate experts and/or the QA contacts for any and all suspected problems with the detectors, calibrations, or fast-offline reconstruction.
- Check the Online-to-Offline data base migration using the "Database Migration Monitor" link on the first page of the QA browser after you login. When data are being taken the first several tables should appear in green font. If no data have been acquired for a day or so then all the tables should be in red. If there are any red fonts in the first several tables labelled "RunLog_onl" while data are being taken then this may indicate a problem and you should notify starqa-hn explicitly.
»
- Printer-friendly version
- Login or register to post comments