NSCL DAQ - Revision history

Rtang: /* Normal installation in Ubuntu 20.04 */

2022-11-04T22:55:21Z

Normal installation in Ubuntu 20.04

← Older revision		Revision as of 18:55, 4 November 2022
Line 9:		Line 9:
	== Normal installation in Ubuntu 20.04 ==		== Normal installation in Ubuntu 20.04 ==

	Please see <b>[https://fsunuc.physics.fsu.edu/elog/~~NSCLDAQ~~/6 this elog entry]</b>.		Please see <b>[https://fsunuc.physics.fsu.edu/elog/Pixie_NSCLDAQ/6 this elog entry]</b>.

	== using Singularity-container in Ubuntu or Debian ==		== using Singularity-container in Ubuntu or Debian ==

Etemanson: /* Install Singularity-container */

2022-09-16T15:10:59Z

Install Singularity-container

← Older revision		Revision as of 11:10, 16 September 2022
Line 19:		Line 19:

	=== Install Singularity-container ===		=== Install Singularity-container ===
			This can be done by source following [https://docs.sylabs.io/guides/3.0/user-guide/installation.html#install-on-linux Sylabs Documentation]. The installation process requires some dependencies from the apt repository as well as installing and configuring Go. An alternative method using a debian repository is shown below.

	* add neuro debain repository (when the following command fail, go to [http://neuro.debian.net/ Neuro Debian website]		* add neuro debain repository (when the following command fail, go to [http://neuro.debian.net/ Neuro Debian website]

Rtang: /* run in background */

2022-09-14T15:03:07Z

run in background

← Older revision		Revision as of 11:03, 14 September 2022
Line 138:		Line 138:

	ps -ef \| grep -E 'Daq\|Ring'		ps -ef \| grep -E 'Daq\|Ring'

	~~<span style="color:red">If run in background, how to run the ReadOutShell? </span>~~

	<span style="color:red">it seems that it opens two instants of VM, one is running DaqPortManager and another is running RingMaster, How can they communicate? </span>		<span style="color:red">it seems that it opens two instants of VM, one is running DaqPortManager and another is running RingMaster, How can they communicate? </span>

Rtang: /* ReadOutShell */

2022-09-14T15:02:48Z

ReadOutShell

← Older revision		Revision as of 11:02, 14 September 2022
Line 145:		Line 145:
	= ReadOutShell =		= ReadOutShell =

	See [[Pixie16_digitizer#ReadOutShell \| the Pixie16 setup]] for the moment.		See [[Pixie16_digitizer#ReadOutShell \| the Pixie16 ReadoutShell setup]] for the moment.

	Also see [https://docs.nscl.msu.edu/daq/newsite/nscldaq-11.4/c3683.html this from NSCL offical webpage]		Also see [https://docs.nscl.msu.edu/daq/newsite/nscldaq-11.4/c3683.html this from NSCL offical webpage]

Rtang: /* NSCLDAQ evt file */

2022-06-06T23:00:18Z

NSCLDAQ evt file

← Older revision		Revision as of 19:00, 6 June 2022
Line 154:		Line 154:

	The NSCL DAQ output the data file as *.evt. It is different from the PIXIE evt file.		The NSCL DAQ output the data file as *.evt. It is different from the PIXIE evt file.

			More information can be found in [https://docs.nscl.msu.edu/daq/newsite/ddas-1.1/Data_01Format.html Data Format].

	The evt file can be view as 4 bytes (32 bits, int) array		The evt file can be view as 4 bytes (32 bits, int) array

Rtang: /* NSCLDAQ evt file */

2022-06-04T20:37:20Z

NSCLDAQ evt file

← Older revision		Revision as of 16:37, 4 June 2022
Line 160:		Line 160:
	! Group\|\| Item \|\| Bytes \|\| word		! Group\|\| Item \|\| Bytes \|\| word
	\|-		\|-
	\| \|\| ~~NSCLDAQ version~~ \|\| 4 \|\| 1		\| rowspan="2" \| Ring Item Header \|\| size \|\| 4 \|\| 1
	\|-		\|-
	\| ~~rowspan="2" \| Ring Item Header \|\| size~~ \|\| 4 \|\| 2		\| type (30 for physics event) \|\| 4 \|\| 2
	\|-		\|-
	\| ~~type (30 for physics event)~~ \|\| 4 \|\| 3		\|rowspan="4" \| Ring Item Body Header \|\| size \|\| 4 \|\| 3
	\|-		\|-
	\|~~rowspan="4"~~ \| ~~Ring Item Body Header~~ \|~~\| size \|\| 4~~ \|\| 4		\| timestamp \|\| 8 \|\| 4,5
	\|-		\|-
	\| ~~timestamp~~ \|\| 8 \|\| 5,6		\| source ID \|\| 4 \|\| 6
	\|-		\|-
	\| ~~source ID~~ \|\| 4 \|\| 7		\| barrier type \|\| 4 \|\| 7
	\|-		\|-
	~~\| barrier type \|\| 4 \|\| 8~~		\| rowspan="10" \| Ring Item Body \|\| size \|\| 4 \|\| 8
	\|-
	\| rowspan="10" \| Ring Item Body \|\| size \|\| 4 \|\| 9
	\|-		\|-
	\| fragment #0 \|\| 56+		\| fragment #0 \|\| 56+
Line 218:		Line 216:

	For the Pixie digitizer, the structure of the '''Raw Data''' can be found [[Pixie16_digitizer#Data_Structure \| Pixie16 digitizer ]]		For the Pixie digitizer, the structure of the '''Raw Data''' can be found [[Pixie16_digitizer#Data_Structure \| Pixie16 digitizer ]]

			From the above table, the '''Ring Item''' are repeated on the top level and also inside the fragment.

			The top level '''Ring Item Header/type''' is used to identify the type of the Ring item

			{\| class ='wikitable'
			! '''Ring Item Header/type''' value \|\| Meaning
			\|-
			\| 1 \|\| Run Begin
			\|-
			\| 2 \|\| Run End
			\|-
			\| 3 \|\| Run Pause
			\|-
			\| 4 \|\| Run Resume
			\|-
			\| 20 \|\| Scaler found
			\|-
			\| 30 \|\| Physics event
			\|-
			\| others \|\| untreated ring item
			\|}

			When the '''Ring Item Header/type''' is not 30, the '''Ring Item Header/size''' - 8 bits data should be skipped.

Rtang: /* NSCLDAQ evt file */

2022-06-04T20:19:24Z

NSCLDAQ evt file

← Older revision		Revision as of 16:19, 4 June 2022
Line 155:		Line 155:
	The NSCL DAQ output the data file as *.evt. It is different from the PIXIE evt file.		The NSCL DAQ output the data file as *.evt. It is different from the PIXIE evt file.

	The evt file can be view as 4 bytes 32 bits array		The evt file can be view as 4 bytes (32 bits, int) array

	{\|class='wikitable'		{\|class='wikitable'

Rtang: /* NSCLDAQ evt file */

2022-06-04T20:11:13Z

NSCLDAQ evt file

← Older revision		Revision as of 16:11, 4 June 2022
Line 176:		Line 176:
	\| rowspan="10" \| Ring Item Body \|\| size \|\| 4 \|\| 9		\| rowspan="10" \| Ring Item Body \|\| size \|\| 4 \|\| 9
	\|-		\|-
	\| fragment #0		\| fragment #0 \|\| 56+
	\|-		\|-
	\| fragment #1		\| fragment #1 \|\| 56+
	\|-		\|-
	\| fragment #2		\| fragment #2 \|\| 56+
	\|-		\|-
	\| ....		\| .... \|\|
	\|-		\|-
	\| fragment #n		\| fragment #n \|\| 56+
	\|}		\|}

Line 214:		Line 214:
	\| Device Info \|\| 4 \|\| 14		\| Device Info \|\| 4 \|\| 14
	\|-		\|-
	\| Raw Data		\| '''Raw Data''' \|\|
	\|}		\|}

			For the Pixie digitizer, the structure of the '''Raw Data''' can be found [[Pixie16_digitizer#Data_Structure \| Pixie16 digitizer ]]

Rtang: /* NSCLDAQ evt file */

2022-06-04T20:02:25Z

NSCLDAQ evt file

@@ Line 215: / Line 215: @@
 |-
 |       Raw Data
 |}

Rtang: /* NSCLDAQ evt file */

2022-06-04T20:02:05Z

NSCLDAQ evt file

← Older revision		Revision as of 16:02, 4 June 2022
Line 206:		Line 206:
	\| Timestamp \|\| 8 \|\| 9, 10		\| Timestamp \|\| 8 \|\| 9, 10
	\|-		\|-
	\|		\| Source ID \|\| 4 \|\| 11
			\|-
			\| Barrier Type \|\| 4 \|\| 12
			\|-
			\| rowspan="4"\| Ring Item Body \|\| size \|\| 4 \|\| 13
			\|-
			\| Device Info \|\| 4 \|\| 14
			\|-
			\| Raw Data
	\|}		\|}