1 / 16

PMD Software Status: Zubayer Ahammed (For PMD) Tuesday, March 17, 2009

PMD Software Status: Zubayer Ahammed (For PMD) Tuesday, March 17, 2009. Geometry. Are any changes in the geometry and material descriptions expected/foreseen?

slade
Download Presentation

PMD Software Status: Zubayer Ahammed (For PMD) Tuesday, March 17, 2009

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. PMD Software Status: Zubayer Ahammed (For PMD) Tuesday, March 17, 2009

  2. Geometry • Are any changes in the geometry and material descriptions expected/foreseen? • The geometry part is being made more modular to enable switching on/off the individual modules of the PMD detector (both planes).Whole PMD geometry is created by two types of  shapes, box and polygon. There are total of 63 volumes The top volume is ‘ALIC’ and the five mother volumes are placed inside it. • ALICE • The PMD volume is divided into four quadrants EPM1, EPM2, EPM3 and EPM4. Each quadrant has two planes, one is PRESHOWER detector plane and other is Charge Particle Veto (CPV) plane.  In each plane of  quadrant, there are six unit modules along with SS supports and Lead (Pb) plates.EFGD is for girders along with their carriage, used to hang the detector. Geometry modification is complete. It will be in SVN by 15th May, 2009. EPM1 EPM2 EFGD EPM3 EPM4

  3. Geometry • Is the current situation satisfactory? • Yes, it is satisfactory . • Full/survey misalignment: is it possible to introduce full or survey misalignment without creating overlaps? • In the existing geometry, there are no issues about overlap. We did not have enough survey points for the 2008 setup. We will need to redo this after putting in the new geometry.

  4. Material Budget • Is the current step size good for the calculation of material budget and for energy loss correction? • Yes, it was taken care some years back when implemented the PMD geometry in geant.

  5. Simulation • Time information in simulation (needed for pileup sim and more realistic detector response) • Is step manager correctly storing the time of the hits • Does the digitization take into account the time of the hits • Does the digitization simulates correctly the time response of the readout (binning, time windows etc.) • As far as PMD is concerned we don’t record timing.

  6. Simulation • Is the memory and CPU consumption under control at each simulation step: hits, sdigits, digits? • Yes. • Labels: are the labels from the kinematics tree correctly propagated to hits, sdigits, digits? • Yes. • Track references: are the track references needed and if yes, are they correctly implemented in the step manager? • We need this track reference for our efficiency and purity.Work is going on in this regard. • Event merging: is the event merging correctly working for the detector? • Implemented and checked. • Embedding: is the track embedding foreseen in your detector? If yes, is it working correctly • We have not done embedding so far. We realize that it would be good to have embedding for our efficiency calculations. We’ll start on this.

  7. Raw Data • Is the raw data format already fixed, or additional changes are needed? • This is fixed and no changes currently foreseen. • There is an ongoing discussion about carrying the track references to the reconstruction routines (but this is unlikely to change the raw data format). BIT NOs INFORMATION 0 - 11 ADC (cell energy)12 - 17 Channel Address (0-63)18 - 28 MCM address29 - 29 030 - 30 031 - 31 Parity

  8. OCDB parameters : simulation vs reconstruction • Are the gains stored in OCDB correctly used both in the simulation and reconstruction? • Yes. Simulated data has been decalibrated and the calibration factors obtained, loaded in OCDB, retrieved and checked. • LHC machine parameters to go to GRP • Not needed for PMD

  9. Reconstruction • Are all the necessary reco params in OCDB (including params for cosmic reco) • Reconstrucion involves clustering and discrimination. For the clustering part so far we don’t have any tunable parameter. For the discrimination part we will have reco paramter. We are in the process of implementing this. • Are reco params fully used in the reco • See above. • Track reconstruction: • shift in the reconstructed Pt: is the problem understood ans is the current situation satisfactory? • doubly found tracks: is the reported increase confirmed and is the origin understood? • is the propagation status correctly taken into account? If the propagation fails, are the track parameters left unchanged? • Is the time information taken into account (needed for pileup) • Time information is not taken into account.

  10. Reconstruction • PID • eta dependency of PID efficiency: is it understood? • We have estimated photon counting efficiency as a function of eta • and found to be reasonable. • PID efficiency at the relativistic rise: is the comparison data vs MC OK? Is the results understood? • Not needed for PMD.

  11. Online Calibration • Status of the procedures (DAs, preprocessor) • So far they have been working fine. Some modification to the DAs and preprocessors are foreseen. Work already started. The Preprocessor • Will be in SVN by 15th May, 2009. • run types defined for your preprocessor (are they correctly implemented in ECS / treated in your preprocessor?) • So far we have had two run types: physics and pedestal. We intend to include calibration run-type. • status of the calibration objects (new objects needed?) • Yes, new objects needed. Need to store the Hot Cell information and the required number of events. The hot cell information from one run will be used to obtain isolated cells for the subsequent run while storing the hot cell information for the next run, and so on.

  12. Offline Calibration • Status of the procedures after the offline October ’08 week: • During Online calibration we store: hot channel information and cell-to-cell gain information. • During 1st Pass Reconstruction, we store cell hit frequency, hot channels, mean, MPV and rms of isolated cell spectra. • Status of the Calibration objects (new objects needed?) • New objects are now added to the code. The modified and the new • codes mainly, • AliPMDHotData.cxx and AliPMDHotData.h for hot channels • AliPMDFirstPassData.cxx and AliPMDFirstPassData.cxx for 1st pass • information will be committed by 15th May, 2009.

  13. GRP • Information you may need to have added in the GRP prepocessor: • Nothing so far. • Run types for which you may need the GRP to run:

  14. Trigger Not needed.

  15. General layout of PMD Simulation chain : SIGNAL BACKGROUND Hits Hits | | | | | | SDigits SDigits | | | | | Merging | ------------------------ | | | Digits -----RAW DATA | |<--------- Cleaning | | | |<----------Calibration RecPoints (Clustering) | | | Discrimination | | ESD | | Analysis

  16. Back Up Slides

More Related