1 / 8

Simulation Tasks  Understanding Tracking  Understanding Hardware

Simulation Tasks  Understanding Tracking  Understanding Hardware. Two types of tasks: Implementing known functions in ATLAS framework Understanding their limits  new algorithms  understanding hardware We need a new training:

waseem
Télécharger la présentation

Simulation Tasks  Understanding Tracking  Understanding Hardware

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. Simulation Tasks  Understanding Tracking  Understanding Hardware • Two types of tasks: • Implementing known functions in ATLAS framework • Understanding their limitsnew algorithms  understanding hardware • We need a new training: • Too many pairs of close-hits  software problem?  good to go to V12 • Too many pairs of near-hits  2nd pixel layer will help. Now is missing • Too many pairs of near-hits  clustering/space point problem? Stop space point use? Dump raw hits, now they are missing • The more tracking users we have  the more we understand about detector/FTK. Meena work is a good example, very useful work, weak points found. Area (b) could be shared by CMS-ATLAS.

  2. FTKsim/FTK STATUS summary • FTKsim efficiency/resolution is similar to Ipatrec efficiency/resolution BUT… • Long story about reducing RW-Ghosts (~Done in Pisa): • RW-Ghosts due to overlap regions solved with new digitization of training samples in Pisa. Detectorinefficiency and noise turned off as much as possible (to our knowledge). • Selective RW balanced by a track fitter that performs all the 5/6 fits if the 6/6 fit doesn’t pass the c2 cut. • Long story about reducing duplicated tracks, generic ghosts (in progress in Pisa): • Many tracks too near (used z, phi, eta, Pt to judge the distance - not IP) • How to replace the Ghost Buster function inside SVT (duplicate clean up)? • Hit Warrior under test  least c2if many tracks share 10-8 meas. over 12 • HW works inside a road, should work on roads that differ for 1 SS ?

  3. WHAT COULD BE DONE IN PARALLEL-1FTKsim V12 GO TO V12 – New FtkSimWrap – New training (yellow box) Pattgen: creates patternbank Corrgen: generates fit costants Ftksim – simulation training Francesco Crescioli

  4. WHAT COULD BE DONE IN PARALLEL-2FTKsim V12 (a) has the highest priority!! • Update FtkSimWrap to produce from Athena V12FTKsim input file format • Activate the 2nd pixel layer and dump all the layers • Dump raw hits (R-PHI Layers and stereo Layers) in addition to space points • Ipatrec Dump: is it possible to run IpatRec without TRT information? • Study again FTK performances on fakes using raw hits: • Not use any clustering and use only clean up after TF. Processing time? Track resolution? • Develop & include in FTKsim an FTK clustering algorithm thinking to the hardwareimplementation (DATA-FORMATTER in the next slide)? • Which is the pattern bank (road) size ? Inside the proposal: Which layers (& how many)? We know now it is better to reject the central ones. Which is the impact on fakes and processing time?

  5. Inside Fast-Track ~75 9U VME boards – 4 types Pixels & SCT PIPELINEDAM + RW overlap regions EVENT # 1 RODs EVENT # N NEW 50~100 KHz event rate AM-board HITS Data Formatter (DF) DO-board S-links SUPER BINS DATA ORGANIZER GigaFitter exGB: Hit Warrior? ROADS cluster finding split by layer ROADS + HITS 2nd step: track fitting ~Offline quality Track parameters Raw data ROBs Track data ROB

  6. WHAT COULD BE DONE IN PARALLEL-3use FTKsim • We planned to study the signal of each physics case on the full simulation. • This means to see FTKSIM performances for: • Bs  mm (done for V10-Francesco-Guido – redo it for V12) • uu, bb jets from SM WH (done for V10-Meena-Guido – redo it for V12) • taus ? • energetic u-b-jets? Supersymmetric Higgs at high masses? • other samples? • Different samples could require different FTK features ! • Taus or energetic b-jets can be more demanding than WH events ! • Produce new Physics samples and simulate FTK !

  7. CONCLUSIONs: work in parallel with Pisa that continues to optimize algorithms • HIGH PRIORITY: Link FTKsim with Athena V12 • Study FTKsim performances on different samples and give back informations to Pisa. • Developing FTK private clustering? • Study FTKsim as a function of possible options (which/how many layers…, clustering y/n…, which algorithms…). Give back informations to Pisa.

  8. Ghost handling Plan • Problems now: • Deletion of 5/6 by RW when a 6/6 is available produces small inefficiencies if the 5/6 was the real track reject all 5/6 and do 7 fits in parallel (6/6 and all 5/6 combination) to choose the best c2 • Deletion of 5/6 by RW not possible if the empty strips belong to different sectors • Training tracks passing through the overlap region producing many Ghost patterns not identified by the RW. Reduce the ghosts of type 2 due to overlap regions, generating a single pattern,

More Related