- genevb's home page
- Posts
- 2024
- 2023
- 2022
- September (1)
- 2021
- 2020
- 2019
- December (1)
- October (4)
- September (2)
- August (6)
- July (1)
- June (2)
- May (4)
- April (2)
- March (3)
- February (3)
- 2018
- 2017
- December (1)
- October (3)
- September (1)
- August (1)
- July (2)
- June (2)
- April (2)
- March (2)
- February (1)
- 2016
- November (2)
- September (1)
- August (2)
- July (1)
- June (2)
- May (2)
- April (1)
- March (5)
- February (2)
- January (1)
- 2015
- December (1)
- October (1)
- September (2)
- June (1)
- May (2)
- April (2)
- March (3)
- February (1)
- January (3)
- 2014
- December (2)
- October (2)
- September (2)
- August (3)
- July (2)
- June (2)
- May (2)
- April (9)
- March (2)
- February (2)
- January (1)
- 2013
- December (5)
- October (3)
- September (3)
- August (1)
- July (1)
- May (4)
- April (4)
- March (7)
- February (1)
- January (2)
- 2012
- December (2)
- November (6)
- October (2)
- September (3)
- August (7)
- July (2)
- June (1)
- May (3)
- April (1)
- March (2)
- February (1)
- 2011
- November (1)
- October (1)
- September (4)
- August (2)
- July (4)
- June (3)
- May (4)
- April (9)
- March (5)
- February (6)
- January (3)
- 2010
- December (3)
- November (6)
- October (3)
- September (1)
- August (5)
- July (1)
- June (4)
- May (1)
- April (2)
- March (2)
- February (4)
- January (2)
- 2009
- November (1)
- October (2)
- September (6)
- August (4)
- July (4)
- June (3)
- May (5)
- April (5)
- March (3)
- February (1)
- 2008
- 2005
- October (1)
- My blog
- Post new blog entry
- All blogs
Effects of offset in distortion maps
At today's TPC meeting, Yuri asked what would be the effect on the distortion maps (particularly SpaceCharge & GridLeak as the largest distortions) if the z-axis of the TPC was offset (e.g. the beam produces SpaceCharge from an axis offset from the TPC's z-axis). It is not a direct answer to the question, but it can give some idea...
I made distortion maps (of all distortions handled by StMagUtilities) for the highest luminosity run from Run 12 (13099025). The maps are distortions vs. radius [60,190] and z [-205,205] in [cm]. I then shifted the maps by 1 cm in the y direction and took the difference of the new map from the original map. I do not believe this is accurate to within a factor of 2 (after all, we calibrate the distortions to match what we see in the data, so re-calibrating with a shifted axis would give a slightly different full distortion map), but is correct for order of magnitude.
In that context, for the largest distortions (highest luminosities), it appears we could have systematic errors on the ~1mm scale.
-Gene
I made distortion maps (of all distortions handled by StMagUtilities) for the highest luminosity run from Run 12 (13099025). The maps are distortions vs. radius [60,190] and z [-205,205] in [cm]. I then shifted the maps by 1 cm in the y direction and took the difference of the new map from the original map. I do not believe this is accurate to within a factor of 2 (after all, we calibrate the distortions to match what we see in the data, so re-calibrating with a shifted axis would give a slightly different full distortion map), but is correct for order of magnitude.
In that context, for the largest distortions (highest luminosities), it appears we could have systematic errors on the ~1mm scale.
map of... | full distortion | absolute difference with offset |
---|---|---|
δ(rφ) @ φ=0 | ||
δ(rφ) @ φ=π/2 | ||
δ(r) @ φ=0 | ||
δ(r) @ φ=π/2 |
-Gene
Groups:
- genevb's blog
- Login or register to post comments