Evolution of FGT helix tracker continues. Changes since 'take2'

• increase minmal # of clusters from nP+nR>=4    to   nP>=3 & nR>=3
• increase assumed errors on clusters from 0.03mm  to 4mm
• reduce reco vertex Z cut form |Z|<80cm to |Z|<50 cm

Input data sets, real events:

• pp200,  minB trig, runs 13066101-104, 51k events  --> reco 219 tracks, Fig 1+2
• pp510, minB trig, run 13079078, 317k events  --> reco 3275, Fig 3+4
• pp510, minB trig, 1/7 of run 13105023, 97k  events  --> reco 595, Fig 5+6

Residua in both planes have RMS of 1.5-2.5mm

More detailed plots, including residua are in attachements

 

---

Fig 0. Example of reco track in octant 3. This track uses 5 P and 5 R clusters, took ~18K events to find it.
Event=recoEve18241_cl69_nP5_nR5 

Naming convention: event#, cl=total # of clusters, nP=# of used P-clusters, nR=# of used R-clusters .

More animated events like this are in the attachment.

---

Fig 1. pp200, fitting summary, runs 13066101-104

Fig 2. pp200, X-Y of reco tracks, runs 13066101-104

---

Fig 3. pp510, fitting summary, run 13079078, TPC was not read out so there is no Zvertex correlation

Fig 4. pp510, X-Y of reco tracks, run 13079078

---

Fig 5. pp510, fitting summary,run 13105023, TPC was not read

Fig 6. pp510, X-Y of reco tracks, run 13105023

---

Verification of FGT timing. COmparison of Z-vertex correlation w/ TPC