technical detail for p12

• The z primary vertex finder tool has an extra parameter (UsePt):
  L3TCFTVertex
  TRACKER (no default)
  ptcut 1.0 0.5 10.0
  UsePt FALSE
  tooltype "data"
  
• The standalone track filter L3FTrack has an extra parameter (MinZHits):
  L3FTrack
  key
  refset
  number 0 0 100
  MinPt 1.0 0.0 100.0
  MaxDCA 1.0 0.0 10.0
  MinXYHits 0 0 16
  MinZHits 0 0 16
  Stream NULL
  
• The electron tool has an extra parameter (CALUNP) and the type of the parameter CHI2 has changed from tool to float:
  L3TEle
  CAL (no default)
  EMFR .9 0. 1.
  Cal_Cps_dphi 0.1 (no range)
  Cal_Cps_dz 100. (no range)
  Cal_Cps_deta 0.1 (no range)
  Cal_Cps_dcut 0.06 (no range)
  Cps_Track_dphi 0.1 (no range)
  Cps_Track_dz 5.0 (no range)
  Cps_Track_dcut 0.5 (no range)
  Cal_Track_dphi 0.1 (no range)
  Cal_Track_deta 0.1 (no range)
  Cal_Track_dcut 0.06 (no range)
  CALUNP NONE
  TRACK NONE
  CPS NONE
  CHI2 -100.0 (no range)
  EMSEED NONE
  isolation -1.0 -2.0 10.
  ConeSize -1.0 -2. 5.
  Width_EM1 -1.0 -2.0 100.
  Width_EM2 -1.0 -2.0 100.
  Width_EM3 -1.0 -2.0 100.
  tooltype "physics"
• Technical changes for p12.04.00:

  l3chunk: storage of the L3PhysicsResults classes was changed from std::map > to std::map > >

  This allows d0om to load the derived L3PhysicsResults classes into memory and write them out again without having to be linked against the relevant libraries - this means that someone wanting to access the L3Chunk - say to get filter statistics information - but not the PhysicsResults does not need to link against the entire L3 subsystem to avoid wiping the L3PhysicsResults from the output.

  The changes were made such that old data will still be valid and readable with the new code. However, it does mean that if you try to read data written with the new code with an older release then there will be no physics results.

• Technical changes for p12.05.00:
  • i) the L3chunk has been modified again, this time to remove the LogicalStream member and add a list of the physical stream names. The LogicalStream is only used internally by L3 and once we move to a scheme where L3 does no validation on the names of the primitive streams then the LogicalStream will have no real meaning outside of the L3 context.

    The list of physical streams was requested by the luminosity group and will allow them to do an extra series of cross checks to make sure that data were streamed to the correct places. It can be accessed via the method:

    const std::vector & getPhysicalStreamNames() const;

  • ii) the functionality changes required to perform inclusive streaming for MONITOR and ERROR streams has been introduced. In its current form all events when the writeDebug flag is set - ie. L3 unbiased events will be inclusively streamed to the stream MONITOR.

    Currently the names of the streams are hardwired into the code as MONITOR and ERROR. ERROR streaming is disabled for the moment.

  • iii) fixes have been made to the stream override mechanism to make the syntax identical to that for assigning a stream to a filter - this just avoids confusion when trying to write trigger lists