140 likes | 275 Vues
Ssd simulation status : preparation for embedding. Jonathan Bouchet Svt Meeting : 09/19. Ssd simulation chain. SsdSimulationMaker SLS (slow simulator) Simulate charge over the strips SPA Signal+pedestal+noise Addition Pedestal supression Zero supression. SsdClusterMaker SCF
E N D
Ssd simulation status : preparation for embedding Jonathan Bouchet Svt Meeting : 09/19
Ssd simulation chain SsdSimulationMaker SLS (slow simulator) Simulate charge over the strips SPA Signal+pedestal+noise Addition Pedestal supression Zero supression SsdClusterMaker SCF Scan the strips Form the clusters SCM Associate the clusters
Ssd Reconstruction Chain SsdDaqmaker Scan the strips and store the pedestals, id and noise into assdStripCalib table SsdPointMaker Do the reconstruction of the clusters Match the clusters to form a hit
Ssd soft : real data vs simu • Many differences between the 2 codes • Real Data : • pick the ssdStripCalib (pedestal and noise) accorging to the time stamp • in /Calibration/ssd. • Reco : (s/n)>5 && noise > 0. • Geometry : ssdWafersPosition.C (the geometry with alignment corrections) • Simu : • The actual calibration : pedestal =100 ADC , noise = 3 ADC • in /starDb/svt/ssd/ • Reco : (s/n)> 5 only • Geometry : geom.C (old) • To have a consistent simu with respect to the data, we must have makers and parameters (noise, pedestal, geometry) equivalent
New way for embedding StSsdDaqMaker DAQ File StSsdPointMaker Spa_strip StSsdSimulationMaker Fzd File St_scf_Maker St_scm_Maker • old chain : StSsdSimulationMaker + St_scf_Maker + St_scm_Maker • New chain : StSsdSimulationMaker + StSsdPointMaker
Noise of the clusters P-side N-side Simulation Real data
Noise : with the new calibration P-side N-side
Charge of the clusters Pedestal = 100 ADC Noise = 3 ADC With real pedestal and noise values • Remove the large tail for the fake clusters (noise)
Comparison between the 2 chains: signal to noise Old chain New chain
Size of the clusters [strips] New chain Old chain • The 2 chains give the same results
Comparison with the efficiencies • Within the bars errors, efficiencies look the same for the 2 chains Old chain New chain
Efficiency • The efficiency looked better (agree with the real data) • But it was before a correction (use simu flag in StSsdDbMaker) • After this correction , efficiency get back to 70 % • Bands in residuals • The difference between efficiencies in simu vs real data still here until now
Summary,outlook • Old Db vs ssdStripCalib • Effect on the clusters properties (noise,size) • Consistant with the real data • Old reco chain vs new reco chain • The 2 chains give similars results (number of ssdHit reco,efficiency) • Not entirely ready for embedding (see previous problem) • Check efficiency (if agree with real data) • Then eliminate old makers (status of StSsdEvalMaker)-->rename Ssd simu chain • Create StSsdMixer for embedding