Too Large Events - Revision history

Vanwdani at 19:40, 12 January 2018

2018-01-12T19:40:00Z

Vanwdani at 19:32, 12 January 2018

2018-01-12T19:32:58Z

Vanwdani at 19:25, 12 January 2018

2018-01-12T19:25:38Z

Vanwdani at 19:25, 12 January 2018

2018-01-12T19:25:02Z

Vanwdani at 17:47, 12 January 2018

2018-01-12T17:47:00Z

Vanwdani at 17:44, 12 January 2018

2018-01-12T17:44:23Z

Vanwdani at 19:13, 11 January 2018

2018-01-11T19:13:41Z

Vanwdani at 18:49, 11 January 2018

2018-01-11T18:49:01Z

Vanwdani at 18:46, 11 January 2018

2018-01-11T18:46:02Z

Vanwdani at 18:39, 11 January 2018

2018-01-11T18:39:35Z

← Older revision		Revision as of 19:40, 12 January 2018
Line 216:		Line 216:
	Gen part 1 pid = 11 px = 1.42725 py = -0.797663 pz = 2.61651 vx = 0 vy = 0 vz = 0 theta = 32.0008 phi = 29.2		Gen part 1 pid = 11 px = 1.42725 py = -0.797663 pz = 2.61651 vx = 0 vy = 0 vz = 0 theta = 32.0008 phi = 29.2
	</pre>		</pre>
		+
		+
		+	Both simulations are using the same random number sequence for both events, but the FT adds a difference in the hit locations.

@@ Line 178: / Line 178: @@
 <pre>
    EVENT # 81273
 ------------------------------------------------------------------------------------------------------------------------------------------------------
@@ Line 183: / Line 189: @@
    Gen part 1     pid  = 11       px  = 1.42446   py  = -0.80264  pz  = 2.61651   vx  = 0         vy  = 0         vz  = 0         theta  = 32.0008        phi  = 29.4
 ------------------------------------------------------------------------------------------------------------------------------------------------------
 </pre>
@@ Line 188: / Line 199: @@
 Similarly, for Field IN FT ON, event 272 + 1(since event 0)
 <pre>
    EVENT # 273
 ------------------------------------------------------------------------------------------------------------------------------------------------------
@@ Line 194: / Line 211: @@
    DChit 0        dpid  = 11      mpid  = 0       mtid  = 0       otid  = 2       X  = 1097.51    Y  = -567.684   Z  = 2015.87    procID  = 999   sector  = 1     layer  = 1      wire  = 77      Theta   = 31.5063        Phi = -27.3502
 ------------------------------------------------------------------------------------------------------------------------------------------------------
 </pre>

@@ Line 193: / Line 193: @@
    Gen part 1     pid  = 11       px  = 1.42446   py  = -0.80264  pz  = 2.61651   vx  = 0         vy  = 0         vz  = 0         theta  = 32.0008        phi  = 29.4
    DChit 0        dpid  = 11      mpid  = 0       mtid  = 0       otid  = 2       X  = 1097.51    Y  = -567.684   Z  = 2015.87    procID  = 999   sector  = 1     layer  = 1      wire  = 77      Theta   = 31.5063        Phi = -27.3502
 ------------------------------------------------------------------------------------------------------------------------------------------------------
 </pre>

← Older revision		Revision as of 19:25, 12 January 2018
Line 169:		Line 169:

	This method works in allowing a root file to be created. However, since each hit is weighted information about that specific angle theta-momentum differential cross section is lost.		This method works in allowing a root file to be created. However, since each hit is weighted information about that specific angle theta-momentum differential cross section is lost.
		+
		+	Comparing Shield IN FT On/Off 1st hits to see if they can be swapped use evioAnalysis_Compare.C
		+
		+
		+	For Field IN OFF, event 272 in the file LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081.evio when coverted to a root that contains all the 316050 lines of the total LUND file, or 105350 Moller events
		+
		+	81files*1000events per file=81,000events+272event=81,272 event number+1 event (since event 0)
		+
		+	<pre>
		+	EVENT # 81273
		+	------------------------------------------------------------------------------------------------------------------------------------------------------
		+	Gen part 0 pid = 11 px = -1.42446 py = 0.80264 pz = 10997.4 vx = 0 vy = 0 vz = 0 theta = 0.0085184 phi = 150.6
		+	Gen part 1 pid = 11 px = 1.42446 py = -0.80264 pz = 2.61651 vx = 0 vy = 0 vz = 0 theta = 32.0008 phi = 29.4
		+	------------------------------------------------------------------------------------------------------------------------------------------------------
		+	</pre>
		+
		+
		+	Similarly, for Field IN FT ON, event 272 + 1(since event 0)
		+	<pre>
		+	EVENT # 273
		+	------------------------------------------------------------------------------------------------------------------------------------------------------
		+	Gen part 0 pid = 11 px = -1.42446 py = 0.80264 pz = 10997.4 vx = 0 vy = 0 vz = 0 theta = 0.0085184 phi = 150.6
		+	Gen part 1 pid = 11 px = 1.42446 py = -0.80264 pz = 2.61651 vx = 0 vy = 0 vz = 0 theta = 32.0008 phi = 29.4
		+	DChit 0 dpid = 11 mpid = 0 mtid = 0 otid = 2 X = 1097.51 Y = -567.684 Z = 2015.87 procID = 999 sector = 1 layer = 1 wire = 77 Theta = 31.5063 Phi = -27.3502
		+	------------------------------------------------------------------------------------------------------------------------------------------------------
		+	EVENT # 274
		+	------------------------------------------------------------------------------------------------------------------------------------------------------
		+	</pre>

← Older revision		Revision as of 17:47, 12 January 2018
Line 167:		Line 167:
	+------------------------------------------------+------------+------------+		+------------------------------------------------+------------+------------+
	</pre>		</pre>
		+
		+	This method works in allowing a root file to be created. However, since each hit is weighted information about that specific angle theta-momentum differential cross section is lost.

@@ Line 93: / Line 93: @@
 which causes the error.  Since the random number sequence is set in the gcard, we can edit the LUND file and insert new values for the Moller electron (all 0).
 <pre>
-event #*3lines per event-2 lines off from 1=817 line number
+event #*3lines per event-2 lines off from 1=814 line number
 </pre>
-The random number sequence hopefully continues without more too large DC hit numbers.  Making a test directory with a LUND file of 5 copies of a zero momentum moller electron with the same conditions as LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081/LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081.evio event #273
+The random number sequence hopefully continues without more too large DC hit numbers.  Making a test directory with a LUND file of 5 copies of a zero momentum moller electron with the same conditions as LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081/LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081.evio event #272(start at line 814)
 <pre>
-       1       1       1       1       16.291110947826 -3515.474338375954176   -20624.345660442169901  0.000834480408767       -10994.256220661920452
+       1       1       1       1       1       16.291110947826 -3515.474338375954176   -20624.345660442169901  0.000834480408767       -10994.256220661920452
        -1      1       11      0       0       -0.001421646561293      0.000807607649314       10.997383476373649      10.997383609788516      0.000511        0       0       0
        -1      1       11      0       0       0.00    0.000   0.00    0.00    0.000511        0       0       0
 </pre>
 The momentum of the Moller particle is set at zero.  No DC hits should occur.  Testing the output of the evio with evio-dump

@@ Line 88: / Line 88: @@
 and the event number+1
 <pre>
-eventnum=eventnum entry=272
+eventnum=eventnum entry=272 (count starts at 0)
 </pre>
 which causes the error.  Since the random number sequence is set in the gcard, we can edit the LUND file and insert new values for the Moller electron (all 0).
 <pre>
-event #*3lines per event=819 line number
+event #*3lines per event-2 lines off from 1=817 line number
 </pre>
-The random number sequence hopefully continues without more too large DC hit numbers.
+The random number sequence hopefully continues without more too large DC hit numbers.  Making a test directory with a LUND file of 5 copies of a zero momentum moller electron with the same conditions as LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081/LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081.evio event #273

← Older revision		Revision as of 18:46, 11 January 2018
Line 78:		Line 78:
	===========================================================		===========================================================
	</pre>		</pre>
		+
		+
		+	We know the file
		+	<pre>
		+	OPENED FILE : LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081/LH2_0Sol_-1Tor_11GeV_IsotropicPhi_ShieldIn_081.evio
		+	</pre>
		+
		+
		+	and the event number+1
		+	<pre>
		+	eventnum=eventnum entry=272)
		+	</pre>
		+
		+	which causes the error. Since the random number sequence is set in the gcard, we can edit the LUND file and insert new values for the Moller electron (all 0). The random number sequence hopefully continues without more too large DC hit numbers.

← Older revision		Revision as of 18:39, 11 January 2018
Line 56:		Line 56:

	2092788898692672-4294967295=2092784603725377 which is over the size of the 32bit variable. We could edit the entire evio read program structure for a 64bit variable or ignore just that specific Theta-Momentum pair. The output of the Shield in may have more DC interactions, but the effect of the shield still blocks electrons regardless if it is on or off. The plots shown earlier and the paper show there isn't much difference. Simulations will be done with the FT OFF.		2092788898692672-4294967295=2092784603725377 which is over the size of the 32bit variable. We could edit the entire evio read program structure for a 64bit variable or ignore just that specific Theta-Momentum pair. The output of the Shield in may have more DC interactions, but the effect of the shield still blocks electrons regardless if it is on or off. The plots shown earlier and the paper show there isn't much difference. Simulations will be done with the FT OFF.
		+
		+	For Shield IN/OFF -1xTorus Field we still get a too large event.
		+	<pre>
		+	The lines below might hint at the cause of the crash.
		+	If they do not help you then please submit a bug report at
		+	http://root.cern.ch/bugs. Please post the ENTIRE stack trace
		+	from above as an attachment in addition to anything else
		+	that might help us fixing this issue.
		+	===========================================================
		+	#5 std::_Rb_tree<unsigned int, std::pair<unsigned int const, bankIndex_t>, std::_Select1st<std::pair<unsigned int const, bankIndex_t> >, std::less<unsigned int>, std::allocator<std::pair<unsigned int const, bankIndex_t> > >::_M_erase (this=this
		+	entry=0x7fc8a4ecae40, __x=0x40b0c0168b89c126) at /usr/include/c++/4.8/bits/stl_tree.h:1125
		+	#6 0x0000000000442725 in clear (this=0x7fc8a4ecae40) at /usr/include/c++/4.8/bits/stl_tree.h:860
		+	#7 clear (this=0x7fc8a4ecae40) at /usr/include/c++/4.8/bits/stl_map.h:789
		+	#8 EvioBankIndex::initBankIndex (this=0x7fc8a4ecae40, buffer=0x7fc8a3f88a40) at src/reader/EvioBankIndex.cc:24
		+	#9 0x000000000043ce03 in EvioDataEvent::init (this=this
		+	entry=0x7fc8a3f88a40, ptr=<optimized out>, len=<optimized out>) at src/reader/EvioDataEvent.cc:136
		+	#10 0x000000000043c5ea in EvioFileReader::readEvent (this=this
		+	entry=0x7fc8a3e02010, eventnum=eventnum
		+	entry=272) at src/reader/EvioFileReader.cc:114
		+	#11 0x0000000000409797 in main (argc=<optimized out>, argv=<optimized out>) at src/convertor/evio2root.cc:851
		+	===========================================================
		+	</pre>