Difference between revisions of "Analysis Actions"
From GlueXWiki
(Created page with "== Summary == * It is often desirable to place cuts and make histograms of the data in JANA prior to making a ROOT TTree. ** For example: data monitoring, cuts to reduce the # of...") |
(→Summary) |
||
| Line 2: | Line 2: | ||
* It is often desirable to place cuts and make histograms of the data in JANA prior to making a ROOT TTree. | * It is often desirable to place cuts and make histograms of the data in JANA prior to making a ROOT TTree. | ||
** For example: data monitoring, cuts to reduce the # of kinematic fits, cuts on the pid or kinematic fit confidence levels, comparison of mass distributions before/after the kinematic fit, skim cuts, etc. | ** For example: data monitoring, cuts to reduce the # of kinematic fits, cuts on the pid or kinematic fit confidence levels, comparison of mass distributions before/after the kinematic fit, skim cuts, etc. | ||
| − | * DAnalysisAction objects enable users to easily integrate these tasks into an analysis: they encapsulate the setup and execution of a given action. | + | * <span style="color:#0000FF">DAnalysisAction</span> objects enable users to easily integrate these tasks into an analysis: they encapsulate the setup and execution of a given action. |
| − | * These actions can be executed directly, but if they are added to the DReaction they will be executed sequentially by the DAnalysisResults_factory. | + | * These actions can be executed directly, but if they are added to the <span style="color:#0000FF">DReaction</span> they will be executed sequentially by the <span style="color:#0000FF">DAnalysisResults_factory</span>. |
| − | ** Actions will be executed on a given DParticleCombo object until it fails a cut, after which the remaining actions won't be executed on that object. | + | ** Actions will be executed on a given <span style="color:#0000FF">DParticleCombo</span> object until it fails a cut, after which the remaining actions won't be executed on that object. |
| − | * Many common actions have been pre-defined in DHistogramActions.* and DCutActions.* | + | * Many common actions have been pre-defined in DHistogramActions.* and DCutActions.*, located in sim-recon/src/libraries/ANALYSIS/ |
* Additional, custom actions can be created in any plugin. | * Additional, custom actions can be created in any plugin. | ||
Revision as of 14:26, 17 February 2013
Summary
- It is often desirable to place cuts and make histograms of the data in JANA prior to making a ROOT TTree.
- For example: data monitoring, cuts to reduce the # of kinematic fits, cuts on the pid or kinematic fit confidence levels, comparison of mass distributions before/after the kinematic fit, skim cuts, etc.
- DAnalysisAction objects enable users to easily integrate these tasks into an analysis: they encapsulate the setup and execution of a given action.
- These actions can be executed directly, but if they are added to the DReaction they will be executed sequentially by the DAnalysisResults_factory.
- Actions will be executed on a given DParticleCombo object until it fails a cut, after which the remaining actions won't be executed on that object.
- Many common actions have been pre-defined in DHistogramActions.* and DCutActions.*, located in sim-recon/src/libraries/ANALYSIS/
- Additional, custom actions can be created in any plugin.
