Difference between revisions of "Analysis Launch Plugin Requirements"
From GlueXWiki
(→General Requirements:) |
(→General Requirements:) |
||
Line 9: | Line 9: | ||
* Plugins must be checked into your home area in: https://halldsvn.jlab.org/repos/trunk/home/ | * 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 | * Plugins and DReactions must have unique names: No one else can use the same names | ||
− | ** E.g.: We can't run 4 plugins named "omega," so try to do something unique (e.g. "omega_pmatt"). | + | ** E.g.: We can't run 4 plugins/reactions named "omega," so try to do something unique (e.g. "omega_pmatt"). |
=== Memory Requirements === | === Memory Requirements === |
Revision as of 18:56, 18 July 2016
To make sure everything works, and to save memory and speed up the analyses, the following restrictions are placed:
Contents
Example
- An example plugin that meets all of the requirements: Paul's γp→K+Λ
Requirements
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
- E.g.: We can't run 4 plugins/reactions named "omega," so try to do something unique (e.g. "omega_pmatt").
Memory Requirements
- Maximum of 10 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).
- Beam-RF Δt cut at +/- 0.5*dBeamBunchFrequency
- 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, confidence level, etc.) are requested.
Recommendations
Kinematic Fit
- The vertex-p4 kinematic fit appears to be behaving semi-reasonably, at least for charged tracks.
- If your channel doesn't have a detached vertex though, you may want to compare the signal & background losses against simply using a P4 fit.
- Be cautious about constraining masses: Once you do, you no longer have an unbiased handle on the background under the peak.
- Mass constraints are on when P4 is fit, unless explicitly disabled
Loose PID cuts
- These still let in a lot of background, but cut ~no signal
- Proton:
- TOF: +/- 2.5 ns
- BCAL: +/- 2.5 ns
- FCAL: +/- 3 ns
- π+, π-:
- TOF: +/- 2 ns (Wide to accept muons from pion decays)
- BCAL: +/- 2.5 ns
- FCAL: +/- 3 ns
- K+, K-:
- TOF: +/- 0.75 ns
- BCAL: +/- 2.5 ns
- FCAL: +/- 3 ns
- γ:
- BCAL: +/- 6 ns
- FCAL: +/- 10 ns