DF Definitions of Tracking Elements - Revision history

Friadavi: /* Tracks */

2019-03-07T01:03:33Z

Tracks

2018-07-12T19:06:13Z

Crosses

2018-07-12T17:15:32Z

Crosses

2018-07-12T17:15:13Z

Tracks

2018-07-12T17:06:27Z

Segments

2018-07-12T17:04:07Z

2018-07-11T17:16:15Z

Hits

2018-07-11T17:13:46Z

Trajectories

2018-07-11T17:12:22Z

Tracks

2018-07-11T17:10:23Z

@@ Line 174: / Line 174: @@
 =Tracks=
-a;skdjf
+Tracks represent the culmination of the entire reconstruction chain. Importantly, they include the reconstructed interaction vertex, momentum at that vertex, and the charge of the particle. They also contain some basic information about the crosses from which the interaction vertex was reconstructed and some statistical data about the fit.
 [[File:DF_DC_Tracks.png|600px]]

@@ Line 115: / Line 115: @@
 =Crosses=
-as;dkj
+Crosses represent a point in space between two superlayers and an associated direction vector. The point is found by taking the average of two points on the midplane between the two superlayers. Those two points are defined by the intersection of the midplane with the lines defined by the Segments. The direction vector is more complicated and can be understood by studying the code below.
 [[File:DF_DC_Crosses.png|600px]]

@@ Line 115: / Line 115: @@
 =Crosses=
 Below is an example of how Crosses are stored in a Hipo file.
@@ Line 144: / Line 146: @@
 ------------------------+---------------------------+
 </pre>
 =Tracks=
 a;skdjf

@@ Line 145: / Line 145: @@
 </pre>
 =Tracks=
 Below is an example of how Tracks are stored in a Hipo file.

@@ Line 72: / Line 72: @@
 =Segments=
-Segments are collections of hits in a single superlayer which have had "bad" hits culled from them. Additionally, a segments also represents a line segment (surprise!) which is a linear approximation of the path of the particle through the superlayer. In the image below, the two segments are represented by the two collections of yellow hexagons. On the left segment you can see the circles which represent the distance of closest approach (doca) of the particle to the wire. The right segment lacks these as there wasn't enough information to solve the left-right ambiguity problem. Also notice that on the left the line segment is approximately tangential to all of the doca circles.
+Segments are collections of hits in a single superlayer which have had "bad" hits culled from them. Additionally, a segment also represents a line segment (surprise!) which is a linear approximation of the path of the particle through the superlayer. In the image below, the two segments are represented by the two collections of yellow hexagons. On the left segment you can see the circles which represent the distance of closest approach (doca) of the particle to the wire. The right segment lacks these as there wasn't enough information to answer the left-right ambiguity. Also notice that on the left the line segment is approximately tangential to all of the doca circles.
 [[File:DF_DC_Segments.png|600px]]

@@ Line 34: / Line 34: @@
 =Clusters=
 Below is an example of how Clusters are stored in a Hipo file.
@@ Line 69: / Line 72: @@
 =Segments=
 Below is an example of how Segments are stored in a Hipo file.
@@ Line 110: / Line 115: @@
 =Crosses=
 Below is an example of how Crosses are stored in a Hipo file.

@@ Line 1: / Line 1: @@
 =Hits=
-Hits are representations of the locations where a particle flying through the drift chamber layers induces a voltage pulse in a nearby wire. In the image below they are represented by the red hexagons.
+Hits are representations of the locations where a particle flying through the drift chamber layers induces a voltage pulse in a nearby wire. In the image below they are represented by the red hexagons. Note that the fact that the track doesn't intersect the hexagons is due to projecting the 3D data onto a 2D plane.
 [[File:DF_DC_Hits.png|600px]]

@@ Line 191: / Line 191: @@
 <pre style="overflow-x: scroll; overflow-y: scroll; white-space: pre;">
 =Main Page=
 [[User:Friadavi]]

← Older revision		Revision as of 17:12, 11 July 2018
Line 144:		Line 144:

	<pre style="overflow-x: scroll; overflow-y: scroll; white-space: pre;">		<pre style="overflow-x: scroll; overflow-y: scroll; white-space: pre;">
		+	SHOWING BANK
		+	------------------------+---------------------------+
		+	>>>> GROUP (group= 20626) (name=HitBasedTrkg::HBTracks):
		+	------------------------+---------------------------+
		+	id ( SHORT) : 1
		+	status ( SHORT) : 100
		+	sector ( BYTE) : 3
		+	c1_x ( FLOAT) : -128.5109
		+	c1_y ( FLOAT) : 115.4666
		+	c1_z ( FLOAT) : 506.9086
		+	c1_ux ( FLOAT) : 0.0032
		+	c1_uy ( FLOAT) : -0.0799
		+	c1_uz ( FLOAT) : -0.9968
		+	c3_x ( FLOAT) : -128.7847
		+	c3_y ( FLOAT) : 120.8905
		+	c3_z ( FLOAT) : 574.3513
		+	c3_ux ( FLOAT) : -0.0045
		+	c3_uy ( FLOAT) : 0.0802
		+	c3_uz ( FLOAT) : 0.9968
		+	t1_x ( FLOAT) : -57.5850
		+	t1_y ( FLOAT) : 45.6473
		+	t1_z ( FLOAT) : 166.7499
		+	t1_px ( FLOAT) : -0.3076
		+	t1_py ( FLOAT) : 0.2565
		+	t1_pz ( FLOAT) : 0.7588
		+	Vtx0_x ( FLOAT) : -2.2362
		+	Vtx0_y ( FLOAT) : -1.3091
		+	Vtx0_z ( FLOAT) : 28.8956
		+	p0_x ( FLOAT) : -0.1872
		+	p0_y ( FLOAT) : 0.3537
		+	p0_z ( FLOAT) : 0.7590
		+	Cross1_ID ( SHORT) : 1
		+	Cross2_ID ( SHORT) : 2
		+	Cross3_ID ( SHORT) : 3
		+	q ( BYTE) : -1
		+	pathlength ( FLOAT) : 583.9297
		+	chi2 ( FLOAT) : 9557.5850
		+	ndf ( SHORT) : 27
		+	------------------------+---------------------------+
		+	</pre>

−	~~</pre>~~
	=Trajectories=		=Trajectories=