- 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
Manual generation of QA histograms
Updated on Tue, 2015-04-14 11:44. Originally created by genevb on 2008-02-18 01:32.
Under:
When there is a need or other interest in generating the Fast Offline QA histograms by hand, these are the steps to follow. You will need an account on rcf, the exact path to the hist.root files of the data you want.
webmaster Created: Fri April 21 13:54:24 EDT 2006; Last modified Tue March 10 12:30 EDT 2015
To create a graphics output from a hist.root file (see note at bottom if you do not have a hist.root file), you will want to use the macro found here: $STAR/StRoot/macros/analysis/bfcread_hist_to_ps.C This macro is already in a path that will automatically be found when running root4star. The macro's arguments which may need attention are: - MainFile: the full path name for hist.root file you want. FastOffline hist.root files can typically be found on the disks /star/data09,10,11,12. - psFile: you can use the default of "QA_hist.ps", but customizing this will avoid overwriting if you want to make multiple sets of plots. A PDF can be obtained by using a filename ending in ".pdf" . - PrintList: for the short QA histogram output insert "qa_shift" in the argument of PrintList. If you want the full 100+ page output just leave the default, i.e. PrintList="" . Here's an example of what your executed macro could look like: root4star -l 'bfcread_hist_to_ps.C(\ "/star/data08/reco/cu62productionMinBias/FullField/dev/2005/077/st_physics_6077050_raw_1010009.hist.root",\ "EventQA",\ "bfcTree",\ "st_physics_6077050_raw_1010009.ps",\ "",\ "qa_shift",\ 2,3)' Running the macro in batch mode (root4star's "-b" option) will help it run more quickly by not showing the plots as they are generated. That's all there is to it. View the QA histos however you wish and your in business. If you want to combine statistics from multiple histogram files, you can add them together using the bfcread_hist_files_add.C macro first. Here is an example of doing so: ls /star/data{09,1[012]}/reco/production_15GeV_2014/ReversedFullField/dev/2014/054/15054005/st_physics*.hist.root > filelist root4star -b -q -l 'bfcread_hist_files_add.C(1000,"filelist","run15054005")' root4star -b -q -l 'bfcread_hist_to_ps.C("run15054005.hist.root")' _________________ If you do not have a hist.root file, you can process a DAQ file by any usual receonstruction chain (you can check that the 'EventQA' chain option gets used), or you can process an existing event.root file with the macros: bfcread_event_QAhist.C (skips hist.root file and draws plots) or bfcread_event_QA_outhistfile.C (creates a hist.root file) (both are in $STAR/StRoot/macros/analysis)
webmaster Created: Fri April 21 13:54:24 EDT 2006; Last modified Tue March 10 12:30 EDT 2015
»
- Printer-friendly version
- Login or register to post comments