Definition at line 10 of file cosmicsHybrid.py.
| def Impl.cosmicsHybrid.cosmicsHybrid.__init__ |
( |
|
self | ) |
|
Definition at line 11 of file cosmicsHybrid.py.
12 cosmics.__init__(self)
13 self.
customs = [
"RecoLocalTracker/SiStripZeroSuppression/customiseHybrid.runOnHybridZS" ]
| def Impl.cosmicsHybrid.cosmicsHybrid.expressProcessing |
( |
|
self, |
|
|
|
globalTag, |
|
|
|
args |
|
) |
| |
Definition at line 30 of file cosmicsHybrid.py.
References Impl.cosmicsHybrid.cosmicsHybrid.customs, and list().
31 if not "customs" in args:
36 return cosmics.expressProcessing(self, globalTag, **args)
def expressProcessing(self, globalTag, args)
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run
| def Impl.cosmicsHybrid.cosmicsHybrid.promptReco |
( |
|
self, |
|
|
|
globalTag, |
|
|
|
args |
|
) |
| |
Definition at line 22 of file cosmicsHybrid.py.
References Impl.cosmicsHybrid.cosmicsHybrid.customs, and list().
23 if not "customs" in args:
28 return cosmics.promptReco(self, globalTag, **args)
def promptReco(self, globalTag, args)
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run
| def Impl.cosmicsHybrid.cosmicsHybrid.visualizationProcessing |
( |
|
self, |
|
|
|
globalTag, |
|
|
|
args |
|
) |
| |
Definition at line 38 of file cosmicsHybrid.py.
References Impl.cosmicsHybrid.cosmicsHybrid.customs, and list().
39 if not "customs" in args:
44 return cosmics.visualizationProcessing(self, globalTag, **args)
45
def visualizationProcessing(self, globalTag, args)
How EventSelector::AcceptEvent() decides whether to accept an event for output otherwise it is excluding the probing of A single or multiple positive and the trigger will pass if any such matching triggers are PASS or EXCEPTION[A criterion thatmatches no triggers at all is detected and causes a throw.] A single negative with an expectation of appropriate bit checking in the decision and the trigger will pass if any such matching triggers are FAIL or EXCEPTION A wildcarded negative criterion that matches more than one trigger in the trigger list("!*","!HLTx*"if it matches 2 triggers or more) will accept the event if all the matching triggers are FAIL.It will reject the event if any of the triggers are PASS or EXCEPTION(this matches the behavior of"!*"before the partial wildcard feature was incorporated).Triggers which are in the READY state are completely ignored.(READY should never be returned since the trigger paths have been run
| Impl.cosmicsHybrid.cosmicsHybrid.customs |
1.8.11
