Changes for page How to save data in the User DAQ

Summary

• Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Parent

...	...	@@ -1,0 +1,1 @@
	1	+FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).WebHome

Content

...	...	@@ -31,7 +31,6 @@
31	31	* NOTE: After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
32	32	* NOTE: Each run has a unique run number. This number is needed to retrieve the data later on. So it is important to keep track which number is associated to what experimental parameters. Note that the run numbers are used by all FLASH DAQs (currently about 10). It might thus well be, that two consecutive runs from you do have run numbers which are spaced by more than one if another DAQ has been started in-between ...
33	33
34		-
35	35	=== Checklist for proper saving of the data ===
36	36
37	37	* Check that some 20 seconds after starting a run the DAQ control shows that the internal checks did not show errors -> the **DAQ traffic light is green** (... still there may be undetected problems !!!)
...	...	@@ -84,16 +84,14 @@
84	84	* browse through the data tree and select your important parameters and drag them with the mouse in the {{code language="none"}}selected{{/code}} window. The list of important parameters should have been defined before the experiment with the FLASH stuff together. This list can also be found in the offline monitor (lower part of DAQ control) )
85	85	* press {{code language="none"}}Start Display{{/code}} to open a new window with your data. In case it was a long run and / or a large amount of data per shot one can limit the number of shown events to a fraction: {{code language="none"}}Events -> Reading Options -> Event Interval{{/code}} provides the option to show only every //n// th dataset.
86	86
87		-
88	88	=== How to get the data out for analysis (short summary) ===
89	89
90	90	The (% class="twikiNewLink" %)DAQdataGui(%%) is a powerful tool to visualize the saved data and to do very preliminary analysis. however for more detailed analysis the data has to be read into analysis programs ( matlab, python, Origin ...) here are different options one can use (what option is the best and how to set it up has to be discussed before hand with the FLASH DAQ experts ...)
91	91
92	92	* The FLASH DAQ system records the data in binary " {{code language="none"}}.raw{{/code}} " files.
93		-** (% class="confluence-link" %)reading the .raw files [[directly via Python>>url:https://ttfinfo.desy.de/DOOCSWiki/Wiki.jsp?page=PythonDAQClientInterface||shape="rect"]], or [[via Matlab >>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).For experts\: many ways to get Data from the DAQ.How to Access the DAQ Using Matlab.WebHome]](%%)(no longer recommended) works, yet not for all data types equally well, and needs precise knowledge of the desired Parameters (useful to have a quick look / preliminary analysis on few parameters).
	91	+** (% class="confluence-link" %)reading the .raw files [[directly via Python>>url:https://ttfinfo.desy.de/DOOCSWiki/Wiki.jsp?page=PythonDAQClientInterface||shape="rect"]], or [[via Matlab >>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).For experts\: many ways to get Data from the DAQ.How to Access the DAQ Using Matlab.WebHome]](%%)(no longer recommended) works, yet not for all data types equally well, and needs precise knowledge of the desired Parameters (useful to have a quick look / preliminary analysis on few parameters).
94	94	** Note that the raw data is only accessible from certain computers within the DESY network and thus not very handy for offline analysis later on ...
95	95
96		-
97	97	* To ease the data analysis we IN ADDITION provide //ON REQUEST// the data from the FLASH DAQ as HDF5 format
98	98	** ONLINE HDF5s: Intro to the [[HDF5 structure used at FLASH>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]]. This contains also a list of the most used Parameters saved at FLASH for analysis - including the HDF5 names, DOOCS and DAQ names ...
99	99	** [[Examples>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]] and an [[API>>url:https://gitlab.desy.de/christopher.passow/fdh-builder||shape="rect"]] to make use of the online HDF5s
...	...	@@ -172,7 +172,6 @@
172	172	FLASH2_USER2 DAQ
173	173	)))
174	174
175		-
176	176	Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.
177	177
178	178	[[image:attach:RCGUI_properties.jpg||height="400"]]
...	...	@@ -283,19 +283,16 @@
283	283
284	284
285	285
286		-
287	287	=== Restarting the DAQ ===
288	288
289	289
290	290	* If the RCGUI does not respond (and also the clock display does not count up) one has to restart the GUI. Usually the DAQ is not affected by the RCGUI hang up ...
291	291
292		-
293	293	* Generally there** 3 ways to "restart" the DAQ**
294	294	** 1. The least interfering way is the "**all to INITIALIZE**" that tries to reset the DAQ processes ... helps for simple "hickups"
295	295	** 2. The "**re-start DAQ**" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
296	296	** 3. In very hard and severe cases there is the **ultimate restart button: "re-start DAQ (no RCSHM)"**
297	297
298		-
299	299	//**Here in more detail:**//
300	300
301	301
...	...	@@ -342,11 +342,9 @@
342	342	** goto "Subsystems" tab and load your Whitelist
343	343	** and start a run ...
344	344
345		-
346	346	* If there are still components not working after the "re-start DAQ (no RCSHM)" you have to call the photon coordinator (4455) and pray ...
347	347
348	348
349		-
350	350	----
351	351
352	352	== [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]] ==