Closer look at resids in Run 11 cosmics

NOTE: Open any image in a new browser window or tab to make it larger. Unless otherwise stated, black data is for zero B field (ZF), blue is full field (FF), and red is reversed full field (RFF).

 

 Continuing looking at cosmic data in Run 11, after my initial look, I processed more data and tried to get a better look at dependencies on B fields. I again used large inner TPC hit errors, selected "quality" tracks staying completely within sectors, and looked at residuals and other values stored in the StiPulls TTree. Here are the statistics on hits (not tracks!) used in these plots vs. sector number, making it clear that statistics are worse for horizontal sectors, and in sectors 4 and 20, which had large dead regions.

Trigger statistics:

  • RFF: 3830426
  • FF: 1574532
  • ZF: 4691124

Here now are the residuals vs. local x (~radius) for each of the 24 sectors (first row is sectors 1..6, second is 7..12, etc., vertical axis is [-0.09, 0.09 cm]), using FitSlices to get gaussian means, as opposed to histogram profiles:

 

Some interesting features:

  1. There appears to be a general ordering of blue above black above red (FF above ZF above RFF).
  2. ZF is not far from flat.
  3. A "chicken feet" feature observable most prominently in the vertical sectors 6,12,18,24 where divergence between the three field results appear largest, which appears to go away as one moves to the horizontal sectors 3,9,15,21.
  4. The horizontal sectors seem to have enough statistics that the error bars are smaller than the points, and the point-to-point variation is small.
  5. It does look like there are some real alignment features visible, such as a shift between inner and outer sectors notable in sectors 22,23,24.

This may be an indicator that a field distortion is in play?

In this next pair of plots, I take RFF mean residuals minus FF and plot 2D converting sectors into azimuth:

Here again one can see the RFF vs. FF difference is largest in the vertical sectors, but the plot isn't as convincing of a vertical distortion as I had hoped it might be.

Also, a field distortion may have some z dependence, so here is the z dependence of the mean residuals from the first three bins in local X using all sectors.

Again, not quite as strong an indicator of a field distortion as one might hope in that the z dependencies aren't clear, nor are they going to zero at the endcaps (though perhaps they do in the ZF data?).

__________

Moving on to Z residuals vs. sector (vertical axis range [-0.09, 0.09 cm]:

Evident here is a lot of timing offsets among the padrows, which appear to be common for all three fields. This looks like there is a lot to sort out. Again using only the first 3 bins in local x, here's the z dependence of the z residuals:

This almost looks like a drift velocity error, but it may have something to do with time-of-flight and probably needs a little deeper investigating.

_________

Other variables vs. sector....

Mean curvature:

The horizontal sectors show a notable deviation, which may reflect that these are mostly tracks which come from above, not below, so the track has a preference to curve in from that direction (a positive curvature for the south sectors of 3 and 21 [sector 21's FF point is unfortunately way off the vertical scale, probably because statistics were bad for it due to dead regions], and a negative curvature for the north sectors of 9 and 15).

 

abs(Mean z):

abs(Mean dip angle):

Mean crossing angle: