1 / 15

MuID Software Status/Future Plan

MuID Software Status/Future Plan. Yajun Mao (RIKEN/CIAE) PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000. m. +. m. -. MuID Reconstruction Overview. Raw Data. Cluster Finder. Road Finder I. Tracker Software.

ermin
Télécharger la présentation

MuID Software Status/Future Plan

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. MuID Software Status/Future Plan Yajun Mao (RIKEN/CIAE) PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  2. m + m - MuID Reconstruction Overview Raw Data Cluster Finder Road Finder I Tracker Software Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000 Road Finder II Muon Identification DST

  3. Status of Phase I Road Finder •  Parameterized cluster size • Multiple seed gaps • Changeable search orders • Steered search window • Accept closest cluster within the window • Weighted line fit when projection • High muon reconstruction efficiency achieved • Basically done, more work are need to optimiz parameters Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  4. Status of Phase II Road Finder • Check track identity to remove ghost roads • Re-find by accept all clusters within search window (with ghost hit check) • Calculate road-track match quality • Calculate discriminant variables • Basically done, evaluation work are need for refinement Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  5. Status of Muon Identification • Currently 2D lookup table is used which is based on momentum-depth study on muons and pions • Extended lookup table is undergoing • Discriminant function analysis is undergoing Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  6. Status of Geometry & Database • Fixed geometry version swapped problem • Fixed database/text file access problem • Used time stamp to access different version • Put reconstruction control parameters to database • facility to read database and convert to hex file Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  7. Status of Event Display • Use the same framework as in central arm • Display entire cluster rather than centroid • Show associated clusters for a given road • Display GEANT tracks (not finished yet) • The event display works fine, some good features in UT event • display will be immigrated and accessible an extra small • window. Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  8. Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  9. Muon ID Software Evaluation • Compare GEANT track with reconstructed road in Muon ID (include comparison between Ghit position and road plane intersection, ratio of matched hits to hits in GTrack and in road) • Deff. between reconstructed track and road at MuTR station 3 (displacement and direction difference) • Muon efficiency for road finder I/II • Ghost/event for road finder I/II • Pion rejection rate for road finder I/II Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  10. Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  11. Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  12. Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  13. The Result of Evaluation # of selected found by matched identified apply Muonevent tracks finder 1 with tracker as muon finder2 2GeV 5000 3730 3269 973 967 967 3GeV 5000 4771 4686 3153 3066 3064 4GeV 5000 4863 4843 3598 3514 3507 5GeV 5000 4913 4902 3749 3648 3637 10GeV 5000 4989 4981 3981 3894 3880 20GeV 5000 4998 4992 4062 3978 3939 Pion 2GeV 10000 11 9 3 2 2 3GeV 10000 48 43 23 21 21 4GeV 10000 67 55 35 23 22 5GeV 10000 104 85 50 37 32 10GeV 10000 180 133 84 35 21 20GeV 10000 778 556 338 168 67 Au+Au MB 750 825 391 234 177 139 Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  14. Future Plan for Reconstruction • Revise Evaluation Software • Tune Parameters for Reconstruction • Develop Muon Identification Software • Use Packet ID rather than Module ID to extract arm and orientation from DCM • Study Road/Track match for ghost drop • Use pMonitor • Use pDST Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

  15. Future Plan for Event Display • Add more diverse event selection capability. • Display GEANT hits and tracks. • Add multiple simultaneous fixed views. • Allow the same object to be displayed differently in different view • Indicated depth of tubes (with color?) • Have variable prominence for geometry outlines. • Saveable preferences for colors, views ... • DST as input Yajun Mao , RIKEN/CIAE PHENIX Muon Collaboration Meeting, BNL, Dec. 16, 2000

More Related