test
CMS 3D CMS Logo

 All Classes Namespaces Files Functions Variables Typedefs Enumerations Enumerator Properties Friends Macros Pages
Classes | Functions
geometryXMLparser Namespace Reference

Classes

class  Alignable
 
class  CSCAlignable
 
class  DTAlignable
 
class  MuonGeometry
 
class  Operation
 

Functions

def cscorder
 
def dtorder
 

Function Documentation

def geometryXMLparser.cscorder (   a,
  b 
)

Definition at line 36 of file geometryXMLparser.py.

References list(), and archive.zip.

36 
37 def cscorder(a, b):
38  for ai, bi, name in zip(list(a) + [0]*(5 - len(a)), \
39  list(b) + [0]*(5 - len(b)), \
40  ("endcap", "station", "ring", "chamber", "layer")):
41  exec("a%s = %d" % (name, ai))
42  exec("b%s = %d" % (name, bi))
43 
44  if astation == 1 and aring == 3: return cmp(a, b)
45 
46  elif aendcap == bendcap and astation == bstation and aring == bring and achamber != bchamber:
47  if achamber == 0: return -1 # upper hierarchy comes first
48  if bchamber == 0: return 1 # upper hierarchy comes first
49  if achamber % 2 == 1 and bchamber % 2 == 0: return -1 # odds come first
50  elif achamber % 2 == 0 and bchamber % 2 == 1: return 1 # evens come after
51 
52  return cmp(a, b)
53 
# External libraries (standard in Python >= 2.4, at least)
tuple zip
Definition: archive.py:476
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 geometryXMLparser.dtorder (   a,
  b 
)

Definition at line 15 of file geometryXMLparser.py.

References list(), and archive.zip.

15 
16 def dtorder(a, b):
17  for ai, bi, name in zip(list(a) + [0]*(5 - len(a)), \
18  list(b) + [0]*(5 - len(b)), \
19  ("wheel", "station", "sector", "superlayer", "layer")):
20  exec("a%s = %d" % (name, ai))
21  exec("b%s = %d" % (name, bi))
22 
23  if awheel == bwheel and astation == bstation:
24 
25  if asector != bsector:
26  if astation == 4: sectororder = [0, 1, 2, 3, 4, 13, 5, 6, 7, 8, 9, 10, 14, 11, 12]
27  elif awheel == 0: sectororder = [0, 1, 5, 9, 2, 6, 10, 3, 7, 11, 4, 8, 12]
28  else: sectororder = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12]
29  return cmp(sectororder.index(asector), sectororder.index(bsector))
30 
31  elif asuperlayer != bsuperlayer:
32  superlayerorder = [0, 1, 3, 2]
33  return cmp(superlayerorder.index(asuperlayer), superlayerorder.index(bsuperlayer))
34 
35  return cmp(a, b)
tuple zip
Definition: archive.py:476
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