Difference between revisions of "Analysis Launch Plugin Requirements"
From GlueXWiki
(→Cut Requirements) |
(→Cut Requirements) |
||
| Line 18: | Line 18: | ||
** Kinematic fit converges (if any). | ** Kinematic fit converges (if any). | ||
* These cuts must be placed before the kinematic fit is performed (except kinfit confidence level, of course). | * These cuts must be placed before the kinematic fit is performed (except kinfit confidence level, of course). | ||
| + | ** The kinematic fit is performed as soon as the fit results (e.g. 4-vectors, pulls, etc.) are requested. | ||
Revision as of 11:58, 13 July 2016
To make sure everything works, and to save memory and speed up the analyses, the following restrictions are placed:
General Requirements:
- Plugins must be checked into your home area in: https://halldsvn.jlab.org/repos/trunk/home/
- Plugins and DReactions must have unique names: No one else can use the same names (we can't run 4 plugins named "omega"), so try to do something unique (e.g. "omega_pmatt").
Memory Requirements
- Maximum of 5 DReactions per user.
- Don’t use a ton of memory (e.g. many DHistogramActions).
Cut Requirements
- All analyses (i.e. DReactions) must use an EventStore skim.
- All channels must have at least the following cuts:
- Pre-combo loose mass cuts around peak
- Loose PID cuts (each particle & detector)
- Kinematic fit converges (if any).
- These cuts must be placed before the kinematic fit is performed (except kinfit confidence level, of course).
- The kinematic fit is performed as soon as the fit results (e.g. 4-vectors, pulls, etc.) are requested.
