Python interface to FWLite LuminosityBlock
Definition at line 140 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 210 of file __init__.py.
References KineDebug3.count(), reco.if(), join(), list(), and split.
211 """Calls FWLite's getByLabel. Called: 212 getByLabel (moduleLabel, handle) 213 getByLabel (moduleLabel, productInstanceLabel, handle), 214 getByLabel (moduleLabel, productInstanceLabel, processLabel, handle), 216 getByLabel ( (mL, pIL,pL), handle) 219 if length < 2
or length > 4:
221 raise RuntimeError(
"Incorrect number of arguments")
223 argsList = list (args)
224 handle = argsList.pop()
225 if len(argsList)==1 :
226 if( isinstance (argsList[0], tuple)
or 227 isinstance (argsList[0], list) ) :
228 if len (argsList[0]) > 3:
229 raise RuntimeError(
"getByLabel Error: label tuple has too " \
230 "many arguments '%s'" % argsList[0])
231 argsList =
list(argsList[0])
232 if( type(argsList[0])
is str
and ":" in argsList[0] ):
233 if argsList[0].
count(
":") > 3:
234 raise RuntimeError(
"getByLabel Error: label tuple has too " \
235 "many arguments '%s'" % argsList[0].
split(
":"))
236 argsList = argsList[0].
split(
":")
237 while len(argsList) < 3:
239 (moduleLabel, productInstanceLabel, processLabel) = argsList
240 labelString =
"'" +
"', '".
join(argsList) +
"'" 241 if not handle._wrapper :
242 handle._resetWrapper()
243 handle._setStatus ( self._lumi.getByLabel( handle._typeInfoGetter(),
245 productInstanceLabel,
247 handle._addressOf() ),
249 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