1 / 17

TPC status report

Marian Ivanov. TPC status report. Outline. Planning tool Savannah bugs concerning TPC TPC reconstrunction status (Thursday 25 June 2009) ‏ TPC calibration/alignment using Kalman Filter ( Thursday 25 June 2009) ‏. Planning tool.

gayle
Download Presentation

TPC status report

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. Marian Ivanov TPC status report

  2. Outline • Planning tool • Savannah bugs concerning TPC • TPC reconstrunction status (Thursday 25 June 2009)‏ • TPC calibration/alignment using Kalman Filter ( Thursday 25 June 2009)‏

  3. Planning tool • 2471 – New OCDB entry – time dependent gain added and used in the reconstruction – Calib/TimeGain (To be added also to the OFFLINE OCDB)‏ • 2468 – New OCDB entry for drift velocity • Array of spline fits (corrections) (data volume ~ 1 Kby)‏ • Different fits for each trigger mask (identified by strings) + one for all trigger+ one for calibration using laser • Not yet in OCDB • 2468 b - New OCDB Entry for space point correction (array of Transformations) (Thursday presentation)‏ • 2468 – Work in progress (special TPC HLT/OFFLINE meeting on Thursday)

  4. Drift velocity correction • Correction using tracks crossing central electrode • Data corrected for P/T • Open issue – P and T in Online (HLT) different time granularity than in OFFLINE • Verification of procedure using laser • Not yet done • Not overlap between cosmic and usable laser tests • Calibration using ITS/TPC matching as AnalysisTask – Work in progress Relative correction

  5. Planning tool / Simulation • 2454 – 2455 - Done • 2456 – To be done (before 03.07)‏ • 2458 – Working • 2459 – Time stamp for simulated events missing – potential problems to apply calibration parameters changing during the run (e.g. drift velocity, gain)‏

  6. Gain calibration

  7. Planning tool • 2460 • 2461 – Stored in the OCDB • Procedure to be tested in P2 (Christian Lippmann)‏ • 2462 – New RCU data format used in Das, usage in the reconstruction to be tested/commited (Jens Wiechula)‏

  8. Planning tool - Reconstruction • 2077 – Cuts to be tuned in the analysis • 2309, 2463 – Done, to be verified in July • 2464-2467 – AliExternalTrackParam::Propagate doesn't take into account Br and Brfi – to be fixed by Jouri Belikov • Preliminary tests with exact MC references - improvement in pt, but not in theta/z • 2465 – Time dependent gain correction in OCDB, position dependend correction also implemented used (small mismatch between simulated and real data)‏

  9. Planning tool. • 2477 – To be tested at Point 2 • Other not yet finished – (Peter Christiansen)‏ • QA checker for TPC simulation/reconstruction implemented in parallel in PWG1- expert mode (see Jacek Otwinoski talk)‏ • QA for the detector matching – expert mode – to be added

  10. Online Calibration • Ø Any news/updates on the procedures? • Drift velocity and gain gain calibration (HLT)‏ • DA using raw data- Drift velocity calibration to be commited soon • Ø Is everything properly integrated in the Shuttle framework? • Not the case for prevously mentioned entries • Ø For which run type would you need the GRP object (in order to be able to reconstruct the run)? • Laser run in addition • Ø Are any updates necessary in the Shuttle code running at P2? • See above

  11. Alignment/Calibration offline procedures • Ø If you did not mention this during the review, do you foresee any offline procedure especially as far as alignment is concerned? • Yes • Ø Does your procedure comply with the Framework? • See presenetation on Thursday (Kalman filter)‏ • In case of filtering the ESD friends: • Ø What is the size of the fraction you would need to store (compared to the present size/ to the ESDs size; depending on the type of collision, energy...)? • Pt cut, all cosmic, sample of all data (1-5 %)‏ • Ø Would you need to store any other object? • Calibration components (drift, gain)‏ • Ø What are the specific requirements of your task, if any? • 2 kind of tasks – light (to run on full statistisitc), heavy (to run on filtered ESD friends) – special calibration train

  12. Alignment/Calibration offline procedures • Ø What is the foreseen size of the object you will need to store? (depending on the type of collision, energy...)‏ • ~1-10 MBy • Ø Is the memory consumption of your procedure under control? • Gain correction calibration, PID calibration, Alignment – ThnSparse used • Ø Is the AnalysisTask to compute the alignment/calibration constants already defined? • 2 implementations – one inside of the framework, combined calibration/alignment – not Analysis task (yet?)‏ • Ø Would you need manual intervention before writing the object in the OCDB? Do you foresee to have it automatic? • Manual intervention needed for everything except of the gain and drift velocity calibration • Ø What are the specific requirements of your task, if any?

  13. Savannah • Ø Is your detector concerned by any important Savannah report? • Yes • Ø If yes, does this affect the quality of the physics results? • Pt, theta, z shift influence physical result • Ø What are the current actions to solve these problems? • Taking into acount Br and Brfi component of the magnetic field

  14. Test with new propagation inside of the TPC (Jacek)‏

  15. Test with new propagation inside of the TPC (Jacek)‏

  16. Savannah

  17. Performance issues • Ø Is your detector affecting the overall CPU and memory (resident and virtual) consumption in the simulation (including the expert QA mode)? • Ø Is your detector affecting the overall CPU and memory (resident and virtual) consumption in the reconstruction (including the expert QA mode)? • No in reconstruction. • Expert QA mode affected • Ø If yes, what are the current actions to solve these problems? • Expert mode to be done in Performance train on filtered ESD friends

More Related