110 likes | 215 Views
Status of JCORRAN analysis train. R.Diaz D.Kim. Analysis Module “Ali JCORRAN Task”. Name : AliJCORRANTask Inherited from AliAnalysisTaskSE Inputs : ESD/AOD Outputs : Tree of AliJPhoton , AliJTrack , AliJHeader ( nano AOD) Offline Trigger in place to improve Rejection
E N D
Status of JCORRAN analysis train R.DiazD.Kim
Analysis Module “AliJCORRANTask” • Name : AliJCORRANTask • Inherited from AliAnalysisTaskSE • Inputs : ESD/AOD • Outputs : Tree of AliJPhoton, AliJTrack , AliJHeader (nano AOD) • Offline Trigger in place to improve Rejection • ( photon energy/pizeropT) • We keep • calorimeters clusters • charged tracks reconstructed in the central tracking system. • SVN proposal • Main module : • AliROOT/PWG4/AliJCORRANTask.cxx • Base Class in a directory : • AliROOT/PWG4/JCORRAN
AliJCORRANTask can read directly from ESD ESD jcorran.root AliJTrack AliJPhoton AliJHeader jcorranQA.root nano AOD AliJCORRANTask TASK 1 JCORRAN Analysis Code Plots(xE, correlation functions…)
Input : AOD after ESD filter JCORRAN task can run with ESD filer module and Cutter can be saved in the outputs Acceptance and Efficiency Correction Services Monte Carlo Truth ESD jcorran.root AliJTrack AliJPhoton AliJHeader jcorranQA.root nano AOD TASK 1 (ESD filter) TASK 2 TASK … AliJCORRANTask AOD JCORRAN Analysis Code Plots(xE, correlation functions…)
AliJCORRANTask test • Local ESD and AOD files : tested • AliEn • First pass completed and tested - jet-jet and gamma-jet [LHC08v, LHC08r, LHC08q] • PROOF • Tested with one file in lxplus • couldn’t connect on PROOF from outside of CERN ? • Issues : • Code debug in a main Task : • Bug in AliAnalysisTaskESDfilter • filling the AOD caloCluster position (line 845 -860) reported to Andreas Morsch • [setting up all the cluster positions with the last track position] • ( fixed locally now and being used for 2nd pass ) • Alien job : many Zombie files , being investigated .
Final Data analysis codes Sepeli : /mnt/nas1/wrk/djkim/work/076.DirG/JCORRAN After your approval, this should go to svn in jyuwiki or phenixcvs
JDataManger/JEventPool 1. // more getters are needed to have PHENIX/ALICE specific control in main code at this moment since PHENIX has more now PhJHeader* GetEventPhJHeader(){ return fHeaderList->GetPhJHeader(0);} AliJHeader* GetEventAliJHeader(){ return fHeaderList->GetAliJHeader(0);} 2. void JDataManager::FillList(TClonesArray* listToFill, TClonesArray* listFromToFill, intcBin, particleTypewhatToFill, corrTypewhatCorrType){ if(fExperiment==kPHENIX){ cuts etc..…} if(fExperiment==kALICE { cuts etc …} 3. void JEventPool::FillNewList(TClonesArray *inList, float cent, float Z, intiev){..} FillListvsFillNewList ; confusing naming JDataManager::RegisterList(…) vsJEventPool::AcceptList(..) 4. Hadron PID is Ready in JDataManagerfor ALICE/PHENIX
JCard • Because we need to Read “ascii” Input • We need the current JCard functionalities and keep the (void*) to define class members as it was, which is unavoidable • TVector is supposed to be afterward • I propose to leave the code as it was • Number of new variables ~ 5 in addition to all existing things. • won’t change things much//
ALICE productions • MC • PDC 08/LHC08r jet-jet pp, PYTHIA, Pt hard > 50 GeV/c 270001 – 270028 2,900,000 • PDC 08/LHC08v jet-jet pp, PYTHIA, 15 GeV/c < Pt hard < 50 GeV/c 280001 – 280043 4,316,900 • PDC 08/LHC08u gamma-jet pp (2), PYTHIA, no quenching 260007 – 260036 3,036,000 • Jyvaskyla production jet-jet and g-jet djkim/PWG4 • Cosmic • First pp
ejobs • Two binaries and job submission scripts • Jtkt_phenix / jtkt_alice • ejobs-phenix , ejobs-alice • Manage the data location and etc
Vertex • The vertex diamond at the LHC can be parametrized by Gaussian shapes along the z -axis (with σz = 5.3 cm) and in the x , y directions. • The width parameter in the transverse plane, σx,y, reported as 15µm. • Depend on the choice of the beam parameter β∗ • affects the beam luminosity and lifetime • σx,y= √εβ∗ ~ 75 µm • With ε = 0.57nm rad ( beam emittance ) , β∗ ~ 10m