Python interface to FWLite LuminosityBlock
Definition at line 141 of file __init__.py.
def python.Lumis.getByLabel |
( |
|
self, |
|
|
|
args |
|
) |
| |
Calls FWLite's getByLabel. Called:
getByLabel (moduleLabel, handle)
getByLabel (moduleLabel, productInstanceLabel, handle),
getByLabel (moduleLabel, productInstanceLabel, processLabel, handle),
or
getByLabel ( (mL, pIL,pL), handle)
Definition at line 211 of file __init__.py.
References KineDebug3.count(), join(), list(), and split.
212 """Calls FWLite's getByLabel. Called: 213 getByLabel (moduleLabel, handle) 214 getByLabel (moduleLabel, productInstanceLabel, handle), 215 getByLabel (moduleLabel, productInstanceLabel, processLabel, handle), 217 getByLabel ( (mL, pIL,pL), handle) 220 if length < 2
or length > 4:
222 raise RuntimeError(
"Incorrect number of arguments")
224 argsList = list (args)
225 handle = argsList.pop()
226 if len(argsList)==1 :
227 if( isinstance (argsList[0], tuple)
or 228 isinstance (argsList[0], list) ) :
229 if len (argsList[0]) > 3:
230 raise RuntimeError(
"getByLabel Error: label tuple has too " \
231 "many arguments '%s'" % argsList[0])
232 argsList =
list(argsList[0])
233 if( isinstance(argsList[0], str)
and ":" in argsList[0] ):
234 if argsList[0].
count(
":") > 3:
235 raise RuntimeError(
"getByLabel Error: label tuple has too " \
236 "many arguments '%s'" % argsList[0].
split(
":"))
237 argsList = argsList[0].
split(
":")
238 while len(argsList) < 3:
240 (moduleLabel, productInstanceLabel, processLabel) = argsList
241 labelString =
"'" +
"', '".
join(argsList) +
"'" 242 if not handle._wrapper :
243 handle._resetWrapper()
244 handle._setStatus ( self._lumi.getByLabel( handle._typeInfoGetter(),
246 productInstanceLabel,
248 handle._addressOf() ),
250 return handle.isValid()
def getByLabel(self, args)
static std::string join(char **cmd)
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