1 / 22

Status MUON software

Status MUON software. Ginés MARTINEZ SUBATECH, Nantes, France ALICE-Offline week 8-12 mars 2004. News from MUON. Physics & Offline MUON meeting in Clermont in january 2004. Next Physics & Offline MUON meeting at CERN April 22 th 2004. MUON Workshop in South Africa June 2004.

schmit
Télécharger la présentation

Status MUON software

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. Status MUON software Ginés MARTINEZ SUBATECH, Nantes, France ALICE-Offline week 8-12 mars 2004

  2. News from MUON • Physics & Offline MUON meeting in Clermont in january 2004. Next Physics & Offline MUON meeting at CERN April 22th 2004. MUON Workshop in South Africa June 2004. • New IO, data container, new definition of the geometry, new response function of chambers, new ALICE coordinates system **, aligment framework, mapping; ... • New developments have started: RawData, Event Sumary Data (ESD), Realistic Physics Cocktail, Sdigits step, trigger reconstruction, matching tracking-trigger, ... • PPR in good shape

  3. What we are NOT doing ! • Calibration • Online control of the spectrometer. • Documentation. • Utilisation of DataGRID (AliEn). • Interface with Beam tests. • Data Base for physics • Reconstruction framework • Participation to the commun framework More people needed!

  4. Geometry Thèse E.Dumonteil Unique definition of the MUON geometry Envelop method from Ivana Hrivnacova Global Interface for MUON Geometry 3D positionning of chambersPositionnement Aligment with physics Dead line : Jan 2004 Done !

  5. New Classes for geometry • AliMUONChamber modified and AliMUONv1 simplified • AliMUONChamberGeometry • AliMUONGeometryConstituent • AliMUONGeometryEnvelope • AliMUONVGeometryBuilder • AliMUONSt1GeometryBuilder (V2) • AliMUONSt2GeometryBuilder • AliMUONSt345GeometryBuilder • AliMUONTriggerGeometryBuilder

  6. Angle effect on spatial resolution The angle effect is taken into account by adding fluctuation of charge position along wires to the one calculated by AliRoot This fluctuation has been obtained from the simulation with gaussian form. PhD Thesis K. Boudjemline HV=1750V PS data Simulation Spatial Resolution (mm) Angle (degrees)

  7. Angle effect and the Upsilon mass • Dipole, Absorber, MUON, Hall, Pipe • Origin 0,0,0 • Sigma 0,0,0 • AliGenPara(1,AliGenMUONlib::kUpsilon); Mass resolution 83.8+-1.3 MeV/c2==> 89.8+-1.4 MeV/c2 BeforeAfter

  8. Dependence in pT

  9. Dependence in y

  10. Realistic simulation of the non-gaussian tails of the spatial reponse function of the tracking chambers: To be done ! Efficiency simulation

  11. Muon Cocktail for Data Challenge 2004 Muon cocktail based on muon source parametrisations of AliGenMUONLib. AliGenMUONCocktail inherence from AliGenCocktail: Cocktail defined in the init Generation based on interaction probability Scaling with Ncoll and Npart included (so pp and PbPb) Proto-trigger at the generation level (multiplicity and pT cut) Generation bias information included Bottonium and charmonium physics scaled with Ncol with shadowing Open charm and beauty physics at the level of the mesons. Parametrisation of hadronic muon from vertex scaled with Ncoll and Npart

  12. Invariant Mass spectra

  13. Sdigit generation • AliMUONDigitizerv1 (AliRunDigitizer framework) was doing Hits => Digits • Merging at Hit level (not aliroot standard) • AliMUONSDigitizerv1 and AliMUONDigitizerv2 have splitted the Digits generation in two steps : Hit=>SDigits and Sdigits => Digits and merging is done at the Sdigits level. • We are ready for AliSimulation framework. • How to manage the merging with underlying events? New ouput in AliRunDigitizer? using folders ?

  14. Data container for MUON • Removing containers from AliMUON • AliMUONData class to manage container lists in the trees, SetTreeAddress, MakeBranch, AddtXXX and ResetXXX • Each reconstruction step need its own datacontainer. • Generalisation could be possible via AliLoader • Generation needs a data container in AliMUON • In the generation step AliMUONData::fHits directly added to AliRun::GetMCApp for PurifyKine() in the SetTreeAddres of AliMUON.

  15. Uncoupling reconstruction from simulation framework • Not a trivial task. • Removing reconstruction from AliMUON • New clusterer class (from TPC) AliMUONClusterer • The reconstruction needs a Loader pointer and its own data container (?) • We are ready to be in the AliReconstruction framework

  16. Uncoupling reconstruction and data containers • Removing data container from AliModule (done) • Creating a new class to contain data AliMUONData (done) • Each reconstruction step needs a pointer to the fLoader and its ow data container (done but not optimal) • Why calling AliModule::SetTreeAddress() each time a AliLoader::LoadXXX is called? • Generalisation of a data container, but keeping the flexibility for each sub detector • Container in AliLoader ?

  17. AliESDMUON • Filling TclonesArray of AliESDMUONTracks : tracking, vertex, hits, chi2, matching with trigger flag, chi2 matching, ... • AliMUON::FillESD ready • Output to be defined by core team • Interface with analysis macro to be developped. (When will it be ready?)

  18. More on reconstruction • Adapting tracking output to the NewIO • Creating trigger tracking • Matching of trigger and tracking • How do we do to manage merging with underlying events? New output (directory) in AliRunDigitizer, Same NewIO files but different folders ?

  19. Data link objects • Tracks, hits, sdigits, digits, rawclusters (recpoints), localtrigger, globaltrigger, tracks • Now links are defined as data members of the data objects. Not everything is possible and dHLT needs something operational asap. Proposal (to be ready for the summer 04): • Special Data link objects. For instance AliMUONSdigitLink (link to hits and tracks in Kine). Refering with TRef ? • Data link objects will be added to the data container and respecting the same output structure as for Data objects • Generation of Data link object will be optional.

  20. More thing in the To Do List • Using new geometry in the digitalisation, clusterisation, tracking etc ... (end 2004) • New clusterisation and Kalman filter tracking (end 2004) • RawData interface with Digits • Interface between geometry with GMS monitoring and physics alignment • Integration of dHLT code in aliroot • Realistic geometry of Station 2

  21. Planning 2004 - 2006(draft jan 04)

  22. Our priorities • More muoners are needed in 2005 to be ready in 2007. • We lost 3 PhD students in 2003-04. New PhD must be involved in offline developments. A full time Post-doc lost in 2003. • PPR to be finished in 2004. More muoners shoud be involved. • Improve our communication with far away labs in India and South-Africa: Video-confe, VRVS, Web must be our standard to avoid the information to be confined in Europe.

More Related