Difference between revisions of "BCAL hadronic efficiencies"
From GlueXWiki
(→Analysis Procedure) |
|||
| Line 3: | Line 3: | ||
== Analysis Procedure == | == Analysis Procedure == | ||
| − | The code is located on [https://github.com/JeffersonLab/halld_recon/tree/master/src/plugins/monitoring/BCAL_Hadronic_Eff Github]. The user will be mainly interested in the scripts contained in the folder ''ROOT_macros | + | The code is located on [https://github.com/JeffersonLab/halld_recon/tree/master/src/plugins/monitoring/BCAL_Hadronic_Eff Github]. The user will be mainly interested in the scripts contained in the folder ''ROOT_macros. |
| − | Steps to extract the BCAL Hadronic Efficiencies: | + | Steps to extract the BCAL Hadronic Efficiencies (see README file on Github): |
| − | + | # Generate the root trees using the BCAL_Hadronic_Eff plugin. This is usually completed as part of the routine GlueX monitoring launches. | |
| − | + | #* The output trees are located in files such as /cache/halld/offline_monitoring/RunPeriod-2019-11/ver12/tree_bcal_hadronic_eff/merged/tree_*.root | |
| − | + | # Run python script Read_bcal_hadronic_eff2.py. Edit the file as needed to point to the correct directories. | |
| − | + | #* Create directories with the names of 'root', 'dat' and 'pdf' | |
| − | + | #* This script iteratively executes the Read_bcal_hadronic_eff2.C script on each of the root trees. | |
| − | + | #* The ROOT output files will be placed in the 'root/' subdirectory. | |
| − | + | #* Summaries of the efficiencies are stored in the 'dat/' subdirectory. These will be used later for plotting summaries | |
| − | + | #* Output plots with details of the efficiency systematics are placed in the 'pdf/' subdirectory. These can be checked for problem. | |
| − | + | # Run python script plot_bcal_hadronic_eff.py. Edit the file as needed to point to the correct directories. | |
| − | + | #* The output of this script is just a file called plot_bcal_hadronic_eff.list, which contains the list of run numbers obtained from the 'dat' subdirectory. | |
| − | + | # Run the ROOT script plot_bcal_hadronic_eff.C, Edit as needed to produce useful output. | |
| − | + | #* The output of this script is the file bcal_hadronic_eff.pdf file with various plots of efficiency vs run number. | |
| − | + | ||
| − | + | ||
| − | + | ||
== Data Studies == | == Data Studies == | ||
Revision as of 11:28, 8 July 2020
Description of Method
Analysis Procedure
The code is located on Github. The user will be mainly interested in the scripts contained in the folder ROOT_macros.
Steps to extract the BCAL Hadronic Efficiencies (see README file on Github):
- Generate the root trees using the BCAL_Hadronic_Eff plugin. This is usually completed as part of the routine GlueX monitoring launches.
- The output trees are located in files such as /cache/halld/offline_monitoring/RunPeriod-2019-11/ver12/tree_bcal_hadronic_eff/merged/tree_*.root
- Run python script Read_bcal_hadronic_eff2.py. Edit the file as needed to point to the correct directories.
- Create directories with the names of 'root', 'dat' and 'pdf'
- This script iteratively executes the Read_bcal_hadronic_eff2.C script on each of the root trees.
- The ROOT output files will be placed in the 'root/' subdirectory.
- Summaries of the efficiencies are stored in the 'dat/' subdirectory. These will be used later for plotting summaries
- Output plots with details of the efficiency systematics are placed in the 'pdf/' subdirectory. These can be checked for problem.
- Run python script plot_bcal_hadronic_eff.py. Edit the file as needed to point to the correct directories.
- The output of this script is just a file called plot_bcal_hadronic_eff.list, which contains the list of run numbers obtained from the 'dat' subdirectory.
- Run the ROOT script plot_bcal_hadronic_eff.C, Edit as needed to produce useful output.
- The output of this script is the file bcal_hadronic_eff.pdf file with various plots of efficiency vs run number.
Data Studies
- Log book entry for Spring 2020 data Log Entry 3812382
- Log book entry for 2018 Log Entry 3642018
- Log book entry for 2017 tracking improvements (comparison between versions 19 and 21) Log Entry 3486656
- Log book entry for 2016 and 2017 efficiency studies Log Entry 3478578. Shows comparison of data and MC and including inefficient channels into the CCDB database.
