1 / 34

Motivation

Motivation. Find useful projections which help to debug the reconstruction algorithms. Event display useful to look for the unexpected. VELO RZ view. RZ projection: R = sqrt(x 2 + y 2 ), x>0 R = -sqrt(x 2 + y 2 ), x<0 Scale: R:Z = 1:8.4

jamesmullins
Download Presentation

Motivation

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. Thomas Ruf VELO RZ Projection February 2005

  2. Motivation • Find useful projections which help to debug the reconstruction algorithms. • Event display useful to look for the unexpected. Thomas Ruf VELO RZ Projection February 2005

  3. VELO RZ view • RZ projection: • R = sqrt(x2 + y2), x>0 • R = -sqrt(x2 + y2), x<0 • Scale: R:Z = 1:8.4 • Tracks crossing VELO halves might look strange, however less busy plot compared to +RZ projection • Projection only makes sense around VELO • R-strips  points • Phi-strips  vertical lines • Selected MCParticles can be displayed in 3d with corresponding detector hits and reconstructed track(s) Thomas Ruf VELO RZ Projection February 2005

  4. Extrapolations Modifications to SoMCParticleCnv and SoTrStoredTrackCnv not directly related to RZ projection • MCParticles: • Production vertex inside Velo and decay vertex outside VELO:Straight line defined by momentum vector • Production vertex outside Velo and decay vertex outside VELO:Straight line connecting production vertex and decay vertices • Production vertex inside Velo and decay vertex inside VELO:Straight line connecting production vertex and decay vertex • Tracks: • Use of parabolic extrapolator if states with momentum information available, otherwise straight line between states Thomas Ruf VELO RZ Projection February 2005

  5. Associations Modifications to SoEvent/Types.cpp, Panoramix/Callback.cpp and Onx/Pages.onx • New Associations entered: • MCParticle_Clusters • VeloCluster_MCParticles • Would be nice to have a generic cluster object. Doesn’t exist at the moment, therefore association needs to be implemented for every cluster type. In picking mode, selecting object and clicking right mouse button: Thomas Ruf VELO RZ Projection February 2005

  6. Display • Vertices: • Production vertex: • Interaction vertex: • MCParticles: • e,u,p,k,p from B : red • Other particles associated to tracks : golden Thomas Ruf VELO RZ Projection February 2005

  7. Display • VELO clusters: • Used R-clusters : red • Unused R-clusters : white • Phi clusters: magenta • Tracks: • VELO back : green yellow • VELO : green • VELO-TT : cyan • Forward : blue • Match : skyblue VELO back Velo-TT Match VELO Forward Thomas Ruf VELO RZ Projection February 2005

  8. Examples All events are from B  D*pNo trigger applied • Tracks crossing detector halves Why does x-slope changes ? Problem with extrapolator ? Thomas Ruf VELO RZ Projection February 2005

  9. Missing b-tracks I • KL decay Velo noise ? b-track, non-reconstructed  go to 3d view Thomas Ruf VELO RZ Projection February 2005

  10. 3d View Thomas Ruf VELO RZ Projection February 2005

  11. Missing b-tracks Ib Thomas Ruf VELO RZ Projection February 2005

  12. 100 mm Missing b-tracks II Thomas Ruf VELO RZ Projection February 2005

  13. 100 mm Missing b-tracks IIb Not enough hits ? decay Thomas Ruf VELO RZ Projection February 2005

  14. Ghosts and Clones Match track and forward track Downstream, 3d Forward track is ghost, however  Thomas Ruf VELO RZ Projection February 2005

  15. Ghosts and Clones, cont. Upstream, 2d However, match track badly extrapolated to primary vertex Thomas Ruf VELO RZ Projection February 2005

  16. 100 mm Precise tracking Thomas Ruf VELO RZ Projection February 2005

  17. Converted Photons Thomas Ruf VELO RZ Projection February 2005

  18. Converted Photons cont. Thomas Ruf VELO RZ Projection February 2005

  19. Conversion reconstructed g conversion Thomas Ruf VELO RZ Projection February 2005

  20. 100 mm K short Ks Thomas Ruf VELO RZ Projection February 2005

  21. 100 mm Pile Up • 3 primary vertices Thomas Ruf VELO RZ Projection February 2005

  22. 100 mm Busy Event I Busy EventBackward Velo trackscleaner than forward ? Thomas Ruf VELO RZ Projection February 2005

  23. Busy Event II Backward Velo trackscleaner than forward ? Thomas Ruf VELO RZ Projection February 2005

  24. Clean Event I Clean EventHowever all B-decay tracksoutside acceptance Thomas Ruf VELO RZ Projection February 2005

  25. 100 mm Clean Event II Another Clean Eventwith most B-decay tracksoutside acceptance Thomas Ruf VELO RZ Projection February 2005

  26. MC Truth Need scale ! Select D* decay tracks and display in 3d  Thomas Ruf VELO RZ Projection February 2005

  27. To reconstruction Thomas Ruf VELO RZ Projection February 2005

  28. Random Observations I Forward track with only 1 r-cluster ? Thomas Ruf VELO RZ Projection February 2005

  29. Random Observations II Velo-TT tracks, extrapolation ?, 0 charge Thomas Ruf VELO RZ Projection February 2005

  30. Random Observations III Not all Velo hits are used Thomas Ruf VELO RZ Projection February 2005

  31. Random Observations IIIa Not all Velo hits are used Kaon decay Thomas Ruf VELO RZ Projection February 2005

  32. Code Modifications • SoEvent/Types.cpp • Added bcflag property • Associations • SoEvent/SoMCParticleCnv.cpp • Display of vertices • Support for RZ projection, more straight line segments inside VELO • SoEvent/SoTrStoredTrackCnv.cpp • Support for RZ projection, more straight line segments inside VELO • SbProjector.cxx: • Added –ZR projection • Temporarily moved to SoEvent/src • Several Python scripts: truf_xxx.py Thomas Ruf VELO RZ Projection February 2005

  33. Interactivity and Python • If Panoramix is started from Python, you can exit Panoramix temporarily and access the event information directly using Python • Example: Access to objects in any keyed container: • After you finished, type to return to Panoramix • Also possible to execute any Python script from Panoramix command line using sys_import(‘myscript’) Thomas Ruf VELO RZ Projection February 2005

  34. End Thomas Ruf VELO RZ Projection February 2005

More Related