BeamLine for pp500 from TPC Twist

The TPC Twist calibration involves using vertices reconstructed by the TPC, and the current practice is to compare the vertices reconstructed by the east and west halves separately. However, in the process, the vertices reconstructed using the whole TPC are stored. Taking these vertices (from runs 12061094-12062005), and weighting by sqrt(multiplicity)/<sqrt(multiplicity)> over the range of vertices between -50 cm < Vz < 50 cm when taking the profile of (Vx vs. Vz) and (Vy vs. Vz), then fitting a 1st order polynomial gives me a good preliminary BeamLine calibration. Here are the (Vx vs. Vz) and (Vy vs. Vz) profiles and fits respectively:

 

There are some visible artifacts in these distributions which should be cleared up in any final calibration, but are acceptable at the level of our interest in determining this to within a few hundred microns as a preliminary calibration (though systematic variations over the course of time during Run 11 are not studied here).

When comparing to the BeamLine calibration that was previously found using HLT data (which assumed zero slope), this result is significantly different:

Intercept [cm] in... x y
HLT 0.526±0.001 0.585±0.001
Twist 0.3259±0.0005 -0.0962±0.0005
difference -0.2001 -0.6812

A different study found signed DCAs that were maximally incorrect at phi = ~0 and ~pi (horizontal) when using the HLT-determined BeamLine, which would imply that the BeamLine was maximally off in the vertical direction...perhaps even by more than half a centimeter. This is in accord with the difference between the HLT-determined and Twist-determined BeamLines, which is about 0.7 cm and is predominantly vertical. So there is reason to be optimistic that the Twist-determined calibration is better.

I still suspect there is some coordinate system difference between HLT and offline reconstruction, but this is my only evidence at this time. In fact, the TPC global coordinate system does use a shift of -0.1780 cm in x and and -0.6752 cm in y (see the database entries for Geometry_tpc / tpcGlobalPosition), which comes very close to matching shifts seen between these two determinations of BeamLine position (see "difference" in the above table)! 

I have uploaded these numbers to the database for Run 11 pp500.

-Gene