STAR Protected
Update 04.30.2018 -- Run 9 pp: Resolution Widths (No QA Cuts)
Even after removing the cut on 'pTreco', the widths of the track resolution distribution still don't look right: the minimum is in the wrong place (~2 GeV/c vs.
Update 04.29.2018 -- Run 14 AuAu: Recoil Jet Check
To check our AuAu signal, I calculated the recoil jet pTcorr spectrum in AuAu using my jet reconstruction code.
Update 04.29.2018 -- Run 9 pp: Resolution Widths (No PtReco cut)
Following up from the previous post:
Update 04.26.2018 -- Run 9 pp: Resolution Width (Different Calculation)
The odd results I obtained previously have cast doubts on how I was calculating the resolution width:
eTOF Data Format
Data Format Used in the 2020 run (commissioning & production)
1) CbmTofStarSubevent2019
Article 20 SN0014
Docs from LBL assembly
QM talk slides draft
Yang Wu's QM 2018 talk slides (draft_03 is same as draft_04). Thanks for any comments and/or advices!
Update 04.23.2018 -- Pythia: pT Resolution Width (and Resolution / Efficiency Algorithm)
I wanted to check what the pT resolution [sigma = (pTmc - pTreco) / pTmc] looks like as implemented in our standalone Pythia8 simulation, so as to compare it to the resolution I calculated from the Ru