- xuanli's home page
- Posts
- 2015
- 2014
- 2013
- December (4)
- November (2)
- October (6)
- September (4)
- August (6)
- July (4)
- June (4)
- May (4)
- April (3)
- March (15)
- February (6)
- January (5)
- 2012
- December (3)
- November (10)
- October (9)
- September (4)
- August (5)
- July (11)
- June (3)
- May (1)
- April (1)
- March (1)
- January (2)
- 2011
- December (3)
- October (4)
- September (3)
- August (3)
- July (2)
- June (6)
- May (13)
- April (7)
- March (10)
- February (2)
- January (1)
- 2010
- 2009
- My blog
- Post new blog entry
- All blogs
ESMD raw ADC cross check
With 5 runs in run08 pp data, the following are the run numbers,
run index run number
1 9060056
2 9061067
3 9061096
4 9064011
5 9064019
My codes marked sector from 0 to 11 and strip from 0 to 287 while Justin's codes marked strip from 1 to 288 and sector from 1 to 12. So in my codes for example for u pannel, the histogram named with hSMD[0][2][1] meaning the raw ADC for ESMD hSMD[panel is U][sector index = 2][strip index = 1]. This is related to Justins histogram a03U002 which is sector 3 U panel strip 2.
So in the following, I use the the marking in my codes. I look at the same strip using the same files input and compare the raw ADC histogram mean and RMS for the same run both using Justin's codes and my codes.
The data points in the following plots are the mean of the raw adc distribution and the error bars are the RMS of the raw adc distribution.
Fig1, U panel sector 2 strip 1.
Fig2, U panel sector 2 strip 11.
This means using Justins codes, there's no pedestal shifting and using my codes there's pedestal shifting. Next step is need to check my codes to understand the differences. If there's no pedestal shifting, it's a good news for the followin data analysis.
- xuanli's blog
- Login or register to post comments