Difference between revisions of "Analyze Analysis Trees"
From GlueXWiki
(→Analyze Analysis Trees) |
(→Using DSelector) |
||
(3 intermediate revisions by one other user not shown) | |||
Line 2: | Line 2: | ||
== General == | == General == | ||
− | There are several methods to analyze an analysis tree which is an output root file from the [https://halldweb.jlab.org/wiki/index.php/ReactionFilter Reaction Filter]. One of them is using a [https://halldweb.jlab.org/wiki/index.php/DSelector ''' | + | There are several methods to analyze an analysis tree which is an output root file from the [https://halldweb.jlab.org/wiki/index.php/ReactionFilter Reaction Filter]. One of them is using a [https://halldweb.jlab.org/wiki/index.php/DSelector '''''DSelector''''']. This link will give a short introduction about its usage. A more in detail documentation can be found here: [https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4607 '''''DSelector Documentation'''''] which is a pdf file on our DocDB based on an overleaf document that is updated from time to time to reflect additions and improvements to the '''DSelector''' software. |
− | There are various approaches when using a DSelector: | + | There are various approaches when using a '''DSelector''': |
− | * using a DSelector once over the full analysis root trees and only save those events that contain a combo that survives all analysis cuts (lose cuts). And then in subsequent analysis steps using the same DSelector code running over these new much smaller data files. | + | * using a '''DSelector''' once over the full analysis root trees and only save those events that contain a combo that survives all analysis cuts (lose cuts). And then in subsequent analysis steps using the same DSelector code running over these new much smaller data files. |
− | * alternatively the DSelector code is used only in the first step writing out combos that survive all analysis cuts into a flat tree, again with rather lose cuts. This flat tree is then subsequently analyzed using custom python code for systematic studies. | + | * alternatively the '''DSelector''' code is used only in the first step writing out combos that survive all analysis cuts into a flat tree, again with rather lose cuts. This flat tree is then subsequently analyzed using custom python code for systematic studies. |
+ | |||
+ | == Using DSelector == | ||
+ | * [https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4111 '''''Analyzing MC data'''''] with the '''DSelector''' | ||
+ | * Alternative: [https://github.com/JeffersonLab/gluex_root_analysis/wiki gluex_root_analysis wiki] | ||
== Analysis Topics == | == Analysis Topics == | ||
Line 12: | Line 16: | ||
* Accidental scaling factor | * Accidental scaling factor | ||
* Uniqueness Tracking | * Uniqueness Tracking | ||
+ | * Q-factor analysis |
Latest revision as of 11:06, 21 August 2024
General
There are several methods to analyze an analysis tree which is an output root file from the Reaction Filter. One of them is using a DSelector. This link will give a short introduction about its usage. A more in detail documentation can be found here: DSelector Documentation which is a pdf file on our DocDB based on an overleaf document that is updated from time to time to reflect additions and improvements to the DSelector software.
There are various approaches when using a DSelector:
- using a DSelector once over the full analysis root trees and only save those events that contain a combo that survives all analysis cuts (lose cuts). And then in subsequent analysis steps using the same DSelector code running over these new much smaller data files.
- alternatively the DSelector code is used only in the first step writing out combos that survive all analysis cuts into a flat tree, again with rather lose cuts. This flat tree is then subsequently analyzed using custom python code for systematic studies.
Using DSelector
- Analyzing MC data with the DSelector
- Alternative: gluex_root_analysis wiki
Analysis Topics
- Accidental Subtraction
- Accidental scaling factor
- Uniqueness Tracking
- Q-factor analysis