DAQmonitor - XWiki

For synchronous data access you can use a DAQ middle layer server called the DAQmonitor. The DAQMonitor usually is used to check that the data revived by the[[ DAQ >>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).How to save data in the User DAQ.WebHome]]is correct.

2

3

But it is also possible to pass the trainID (historically called macropulse) in pydoocs {{code language="none"}}read{{/code}} methode and ensure related data. For this purpose the DAQmonitor (to be updated !) provides a ring buffer. [[An example>>url:https://stash.desy.de/projects/FSFL/repos/jupyter-notebook/browse/examples/pydoocs_read_bytrainId/MHzADC_via_DAQmonitor.ipynb||rel="nofollow" shape="rect" class="external-link"]] how to read the data from the ring buffer can be found in the [[repository>>url:https://stash.desy.de/projects/FSFL/repos/jupyter-notebook/browse||rel="nofollow" shape="rect" class="external-link"]].

4

5

In addition the data from the DAQ monitor can be seen in the DAQ control to crosscheck that the data that should be saved reaches the DAQ correctly (long enough ADC traces ...)

6

7

[[image:attach:2020-09-10T16 41 50.png||thumbnail="true" height="250"]]

\\

== Configuring the DAQ monitor: ==

12

13

After taken a DAQ run with the actual DAQ configuration which will be used during the beamtime, you could configure the DAQmonitor by using the taken DAQ run via the [[DAQdataGUI>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).For experts\: many ways to get Data from the DAQ.WebHome]].

14

15

[[image:attach:2020-09-18 13_18_57-Window.png||height="250"]]

16

17

Currently it is the recommendation to configure the DAQmonitor as {{code language="none"}}vuvfuser{{/code}} from {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}}.

\\

== Extra stuff ==

For experts: if a run is active (like in PBD) and the DAQmonitor is not reacting and can not be configured one can set the monitor ( in the status panel) to INITIALIZED and send the configuration and set to RUN again ...

\\

== MCS4 documentation ==

28

29

[[Link to the DAQmonitor Docu from MCS4>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=DAQ%20monitor%20server%20with%20Python%20support||shape="rect"]]

\\

\\

\\

Wiki source code of DAQmonitor

Applications

Navigation

version	line-number	content
15.2	1	For synchronous data access you can use a DAQ middle layer server called the DAQmonitor. The DAQMonitor usually is used to check that the data revived by the[[ DAQ >>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).How to save data in the User DAQ.WebHome]]is correct.
	2
	3	But it is also possible to pass the trainID (historically called macropulse) in pydoocs {{code language="none"}}read{{/code}} methode and ensure related data. For this purpose the DAQmonitor (to be updated !) provides a ring buffer. [[An example>>url:https://stash.desy.de/projects/FSFL/repos/jupyter-notebook/browse/examples/pydoocs_read_bytrainId/MHzADC_via_DAQmonitor.ipynb\|\|rel="nofollow" shape="rect" class="external-link"]] how to read the data from the ring buffer can be found in the [[repository>>url:https://stash.desy.de/projects/FSFL/repos/jupyter-notebook/browse\|\|rel="nofollow" shape="rect" class="external-link"]].
	4
	5	In addition the data from the DAQ monitor can be seen in the DAQ control to crosscheck that the data that should be saved reaches the DAQ correctly (long enough ADC traces ...)
	6
	7	[[image:attach:2020-09-10T16 41 50.png\|\|thumbnail="true" height="250"]]
	8
	9	\\
	10
	11	== Configuring the DAQ monitor: ==
	12
	13	After taken a DAQ run with the actual DAQ configuration which will be used during the beamtime, you could configure the DAQmonitor by using the taken DAQ run via the [[DAQdataGUI>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).For experts\: many ways to get Data from the DAQ.WebHome]].
	14
	15	[[image:attach:2020-09-18 13_18_57-Window.png\|\|height="250"]]
	16
	17	Currently it is the recommendation to configure the DAQmonitor as {{code language="none"}}vuvfuser{{/code}} from {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}}.
	18
	19	\\
	20
	21	== Extra stuff ==
	22
	23	For experts: if a run is active (like in PBD) and the DAQmonitor is not reacting and can not be configured one can set the monitor ( in the status panel) to INITIALIZED and send the configuration and set to RUN again ...
	24
	25	\\
	26
	27	== MCS4 documentation ==
	28
	29	[[Link to the DAQmonitor Docu from MCS4>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=DAQ%20monitor%20server%20with%20Python%20support\|\|shape="rect"]]
	30
	31	\\
	32
	33	\\
	34
	35	\\