Closed carolinecollard closed 1 year ago
carolinecollard
commented
1 year ago Comment : I haven't updated the dEdX SF yet, as some work on the fitting macro is needed to get more robust numbers. IN addition, the Fpix cut was applied for the SF_HHit* plots in V45 :( I will work on these numbers with the next production.
tvami
commented
1 year ago who is using Ih Up (dedxMUpObj) and Down ?
That was supposed to be in input to the mass method. If you guys dont use it, then nobody does
tvami
commented
1 year ago is it OK to choose that file
Yes, tho, for the MC the file Analyzer/test/Tamas/HSCParticleProducerAnalyzer_2018_mc_cfg.py and Analyzer/test/Tamas/HSCParticleProducerAnalyzer_2018_SignalMC_cfg.py is used
switching to Ih_striponly for globalIh --> add plots with Ih_noL1. Open related question : who is using Ih Up (dedxMUpObj) and Down ? Because at the moment these quantities have nothing to do with the globalIh definition...
new set of K and C parameters derived without Fpix cut applied in the selection. new values put in one file of Tamas (is it OK to choose that file Analyzer/test/Tamas/HSCParticleProducerAnalyzer_master_cfg.py for that ?). The values are derived from V45p6, except for 2017 MC for which V45p3 is used. note that the MC values are derived with the actual dEdX SF used in the Framework. the macro code to derive the parameter values is uploaded in the framework.
cleaning of the pixel for calibration : for dEdX SF : no more cut on Fpix at track level, no more cut on probQ at cluster level, but add a cut on the cluster size for K and C : no more cut at Fpix at track level. for Ih_noL1 definition : the probQ cut is still applied, a new cut on the cluster size is applied in addition.
new plots : to answer Slava's questions (like Cluster dE/dX in Strip vs time) + add 2 CR : CR2 = 55 < pT < 70 and CR3 = 70< pT < 200.