1 / 8

Some Topics

Some Topics. TKR Geometry Status Xml Database TkrGeometrySvc TKR Calibration – hot and dead strips Algorithms exist New database (Joanne). TKR Geometry Status. Most of flight geometry implemented, see: GLAST Ground Software page -> Software Cantons -> Geometry -> TKR Diagrams

nmarion
Download Presentation

Some Topics

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Some Topics • TKR Geometry • Status • Xml Database • TkrGeometrySvc • TKR Calibration – hot and dead strips • Algorithms exist • New database (Joanne) Tracker Software Week – Pisa

  2. TKR Geometry Status • Most of flight geometry implemented, see:GLAST Ground Software page -> Software Cantons -> Geometry -> TKR Diagrams • Average TKR walls • Detailed tray, with average MCM boards • Upgrades needed to handle BTEM/BFEM geometry • Incomplete trays • Different wafer sizes • TKR code runs from geometry database Tracker Software Week – Pisa

  3. Geometry – xmlGeoDbs(See: cvsweb: xmlGeoDbs/xml/flight) • flightTKRCountPrim.xml <prim name="numTrays" value="19" uType="count">number of trays (one more than number of x-y planes)</prim>   <prim name="numNoCnvTrays" value="3" uType="count">number of trays with no converter.  These trays have the lowest tray number</prim>   <prim name="numSuperGlast" value="4" uType="count">number of trays with super-Glast thickness converter.  These are immediately above    the no-lead trays</prim> • flightTKRDimPrim.xml <!-- Fundamental Z dimensions in tracker -->   <prim name="TKRTransverseStayClear" value="372.0">Tranverse dimension of TKR Stay Clear envelope from LAT-DS-00038-2</prim>   <prim name="TKRVertStayClear" value="640.0">Z dimension of TKR Stay Clear envelope from LAT-DS-00038-2</prim>         <prim name= "SiThick" value= "0.4" >Si thickness</prim>         <prim name="coreThick" value="27.92">Thickness of core material in all trays except the bottom and top</prim> Tracker Software Week – Pisa

  4. Geometry – xmlGeoDbs, cont. • flightTKRMatPrim.xml <prim name="TKRDetMat" value="Si" type="string" uType="mat">Material of tracker detector elements</prim>   <prim name="coreRegMat" value="Al_1lb" type="string" uType="mat"> • flightTKROneTkr.xml <!-- Make a stack for the bottom tray.  It's rotated, so use SiLayerYMeas -->     <stackZ name="trayBot" >     <axisPos volume="TKRFaceMin" >   <idFieldname="fTKRTrayCmp"valueREF="eTKRBotFace"/>     </axisPos>       <axisPos volume="TKRCoreOuterBottom" >         <idField name="fTKRTrayCmp"valueREF="eTKRCoreClose”/>       </axisPos>       <axisPos volume="TKRTopFaceReg" > <idField name="fTKRTrayCmp" valueREF="eTKRTopFace" /> </axisPos>       <axisPos volume="SiLayerYMeas" >  <idField name="fTKRTrayCmp" valueREF="eTKRSiTop" />   </axisPos>     </stackZ> Tracker Software Week – Pisa

  5. Geometry - TkrGeometrySvc • Interface to GlastDetSvc • Runs entirely from xmlGeoDb • Except connection between (tray, botTop) and (layer, view) • Supplies needed constants • Calculates insideActiveArea() • Uses constants from xmlGeoDb, plus code • Distance to nearest edge of wafer, negative if outside Currently seems overly complicated: • TkrGeomSvc -> GlastDetSvc -> SiPlaneGeometry • Need better scheme to connect TkrGeomSvc where needed… singleton? Tracker Software Week – Pisa

  6. Calibration -- Algorithm • Algorithm exists • Two versions (Leon, Taka), very similar • Use general trigger events • Compare number of hits on each strip with average for tray • Simple criteria for “hot” and “dead” • Needs some refinement • Define levels of hot and dead • Trigger, noise, pattern recognition, fitting, etc. • Compare to hit profile, not average value in tray • Different triggers for hot, dead? • Define number of events needed Tracker Software Week – Pisa

  7. Hit Profiles Tracker Software Week – Pisa

  8. TKR Bad-Strips Database Joanne has a prototype Tracker Software Week – Pisa

More Related