Running pRUParser - Revision history

Vei046 at 09:23, 1 September 2020

2020-09-01T09:23:12Z

← Older revision		Revision as of 09:23, 1 September 2020
Line 120:		Line 120:

	* Random empty frames with/without compression leads to missing region headers.		* Random empty frames with/without compression leads to missing region headers.

	* Data long are sometimes not analyzed correctly leading to a different hit pattern from what was expected.

	* No specific check for fatal or data overrun in ALPIDE trailer, which should be a critical warning, and the frame should be saved.		* No specific check for fatal or data overrun in ALPIDE trailer, which should be a critical warning, and the frame should be saved.

Mri083: /* Known Issues */ More details added

2020-06-30T09:44:35Z

Known Issues: More details added

← Older revision		Revision as of 09:44, 30 June 2020
Line 105:		Line 105:

	* Unable to analyze datastream if idle (FF) is thrown into the datastream, needs masking to handle this. (Testcase 5)		* Unable to analyze datastream if idle (FF) is thrown into the datastream, needs masking to handle this. (Testcase 5)
			** idle is masked by the RU firmware in normal operation
			** need to be handled as optional debug feature
			** extended error checking if error occurred

	* Mistakenly throws missing region header error when we have a frame consisting of only header+trailer with alpide trailer set to b8, which should be a busy violation.		* Mistakenly throws missing region header error when we have a frame consisting of only alpide header+trailer with alpide trailer set to b8, which should be a busy violation.

	* Parser reports more pru frame errors than there are frames when busies are thrown in randomly. Reports missing trailer errors when all trailers are present.		* Parser reports more pru frame errors than there are frames when busies are thrown in randomly. Reports missing trailer errors when all trailers are present.

	* All frames with errors are ~~thrown~~, should be saved somewhere.		* All frames with errors are discarded, should be saved somewhere.
			** currently all frames with errors are stored in a temporary internal buffer, needs to be saved to file
			** consider an error descriptor struct to describe frames in the raw buffer

	* Need more detail on ALPIDE trailer flags, the different errors should be stored along with the frame id somewhere. (Additional fields in .root format)		* Need more detail on ALPIDE trailer flags, the different errors should be stored along with the frame id somewhere. (Additional fields in .root format)

	* Random empty frames with/without compression leads to missing region headers.		* Random empty frames with/without compression leads to missing region headers.

	* Data long are sometimes not analyzed correctly leading to a different hit pattern from what was expected.		* Data long are sometimes not analyzed correctly leading to a different hit pattern from what was expected.
Line 121:		Line 126:

	* Conversion of data to .root format is only started after all the data is read out. This should be parallelized so that the conversion may start once the first pru-trailer is received.		* Conversion of data to .root format is only started after all the data is read out. This should be parallelized so that the conversion may start once the first pru-trailer is received.
			** implement after stable error handling is implemented

Vei046 at 12:28, 23 June 2020

2020-06-23T12:28:30Z

← Older revision		Revision as of 12:28, 23 June 2020
Line 119:		Line 119:

	* No specific check for fatal or data overrun in ALPIDE trailer, which should be a critical warning, and the frame should be saved.		* No specific check for fatal or data overrun in ALPIDE trailer, which should be a critical warning, and the frame should be saved.

			* Conversion of data to .root format is only started after all the data is read out. This should be parallelized so that the conversion may start once the first pru-trailer is received.

Vei046 at 12:25, 23 June 2020

2020-06-23T12:25:11Z

← Older revision		Revision as of 12:25, 23 June 2020
Line 117:		Line 117:

	* Data long are sometimes not analyzed correctly leading to a different hit pattern from what was expected.		* Data long are sometimes not analyzed correctly leading to a different hit pattern from what was expected.

			* No specific check for fatal or data overrun in ALPIDE trailer, which should be a critical warning, and the frame should be saved.

Vei046 at 12:22, 23 June 2020

2020-06-23T12:22:18Z

← Older revision		Revision as of 12:22, 23 June 2020
Line 100:		Line 100:
	xxd -r -p testcase_pruformat.txt outputfilename.bin		xxd -r -p testcase_pruformat.txt outputfilename.bin
	</syntaxhighlight>		</syntaxhighlight>


			=== Known Issues ===

			* Unable to analyze datastream if idle (FF) is thrown into the datastream, needs masking to handle this. (Testcase 5)

			* Mistakenly throws missing region header error when we have a frame consisting of only header+trailer with alpide trailer set to b8, which should be a busy violation.

			* Parser reports more pru frame errors than there are frames when busies are thrown in randomly. Reports missing trailer errors when all trailers are present.

			* All frames with errors are thrown, should be saved somewhere.

			* Need more detail on ALPIDE trailer flags, the different errors should be stored along with the frame id somewhere. (Additional fields in .root format)

			* Random empty frames with/without compression leads to missing region headers.

			* Data long are sometimes not analyzed correctly leading to a different hit pattern from what was expected.

Vei046 at 10:58, 23 June 2020

2020-06-23T10:58:39Z

← Older revision		Revision as of 10:58, 23 June 2020
Line 86:		Line 86:

	=== Generation of test data ===		=== Generation of test data ===

			Clone into the WP3 repository

			<syntaxhighlight lang="bash">
			cd wp3/software/simulation
			pip3 install -r requirements.txt
			python3 test_cases.py
			</syntaxhighlight>

			cd to the desired test case folder. The different test cases are described in test_cases.py

			<syntaxhighlight lang="bash">
			xxd -r -p testcase_pruformat.txt outputfilename.bin
			</syntaxhighlight>

Mri083 at 11:13, 19 June 2020

2020-06-19T11:13:07Z

@@ Line 9: / Line 9: @@
 == Protocol Dependencies ==
 The pRUParser uses the pRU Data Format Specification v0.2
 == Usage ==
@@ Line 71: / Line 73: @@
 ALPIDE Strobe Extended: n
 </syntaxhighlight>

Osk090 at 08:13, 4 February 2020

2020-02-04T08:13:48Z

← Older revision		Revision as of 08:13, 4 February 2020
Line 1:		Line 1:
	[[Main Page]] -> [[Control & Readout Software Documentation and Howto's]] -> [[Running pRUParser]]		[[Main Page]] -> [[Control & Readout Software Documentation and Howto's]] -> [[Running pRUParser]]


	== Software Function ==		== Software Function ==

Osk090 at 08:13, 4 February 2020

2020-02-04T08:13:36Z

← Older revision		Revision as of 08:13, 4 February 2020
Line 1:		Line 1:
			[[Main Page]] -> [[Control & Readout Software Documentation and Howto's]] -> [[Running pRUParser]]

	== Software Function ==		== Software Function ==
	The pRUParser takes a raw, binary, offload stream of pRU data from a file created by the pDTP Client.		The pRUParser takes a raw, binary, offload stream of pRU data from a file created by the pDTP Client.

Osk090 at 08:12, 4 February 2020

2020-02-04T08:12:15Z

← Older revision		Revision as of 08:12, 4 February 2020
Line 20:		Line 20:

	== Output ==		== Output ==
	During the parse, status summaries will be printed:		During the parse, if verbosity is greater than 0, a status summaries will be printed:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	Starting pipeline ...		Starting pipeline ...
	Input policy [File reader]: file readout/testDataX288.bin size kxcd		Input policy [File reader]: file readout/testDataX288.bin size kxcd
	Filter policy [Forward]: buffer of kxcd byte(s)		Filter policy [Forward]: buffer of kxcd byte(s)
	This parse had a speed of: ~~672~~.~~798~~ Mb/s		This parse had a speed of: kx.cd Mb/s
	Ouput policy [File writer]: write to file readout/pData.bin size kxcd		Ouput policy [File writer]: write to file readout/pData.bin size kxcd
	... done		... done
			</syntaxhighlight>

			Otherwise, only a the parse benchmark will be printed
			<syntaxhighlight lang="bash">
			This parse had a speed of: kx.cd Mb/s
	</syntaxhighlight>		</syntaxhighlight>