Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 29.1
edited by sndueste
on 2022-09-08 17:33
Change comment: There is no comment for this version
To version 34.2
edited by sndueste
on 2025-02-05 11:21
Change comment: Update document after refactoring.

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).WebHome
Tags
... ... @@ -1,0 +1,1 @@
1 +favourite
Content
... ... @@ -1,22 +3,19 @@
1 -
2 -
3 3  {{toc/}}
4 4  
5 -\\
6 6  
7 7  == General Concept ==
8 8  
9 -A large number of parameters which are essential for ALL Experiments is continuously saved (pulse energy, arrival time, Beamline settings ...) in the [[ PHOTONDIAGNOSTIC FLASH DAQ>>doc:FLASHUSER.FLASH1 PhotDiag stream]] system.
10 -Other [[experiment related information>>doc:FLASHUSER.Configuring the user DAQs]] is ONLY saved by the users **ON DEMAND **in the FLASH DAQ system. To record this type of data we have 3 User DAQs at FLASH1 (FLASH1_USER1,FLASH1_USER2 and FLASH1_USER3) and two at FLASH 2 (FLASH2_USER1, FLASH2_USER2)
6 +
7 +All Data which is important for the experiment is saved by the users **ON DEMAND **in the FLASH DAQ system. To record this type of data we have 3 User DAQs at FLASH1 (FLASH1_USER1,FLASH1_USER2 and FLASH1_USER3) and two at FLASH 2 (FLASH2_USER1, FLASH2_USER2)
11 11  How to save this experiment related "User-Data" will be explained briefly in this page:
12 12  
13 -\\
10 +In addition, a large number of parameters is continuously saved (pulse energy, arrival time, Beamline settings ...) in the PHOTONDIAGNOSTIC FLASH DAQ system as backup.
14 14  
12 +
15 15  == Taking User data: Starting and stopping runs (Users) ==
16 16  
17 17  In order to save the experiment related data from ADCs, Images, delayline detectors etc. the User DAQ has to be started to record the experiment data. The options which data can be saved, have to be discussed way before the beamtime. For regular beamtime operation the DAQ also was setup by experts before the beamtime. If things do not look like described here look in the troubleshooting section below.
18 18  
19 -\\
20 20  
21 21  === DAQ control panel ===
22 22  
... ... @@ -26,9 +26,8 @@
26 26  \\The following window opens. Here the User DAQ can be started and stopped as well as the incoming data can be visualized, information about data rates and saved properties is presented as well as the panel is automatically printed in to the logbook:
27 27  
28 28  [[image:attach:jddd_DAQ-control-manual2.png||width="800"]]
29 -\\\\
26 +\\
30 30  
31 -\\
32 32  
33 33  * By pressing the start and stop button, besides sending the commands to the DAQ the button prints the panel to the respective beamline / experiments logbook. Here you can later on keep track of the runs. Links to the Beamline logbooks can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.E-Logbooks.WebHome]].
34 34  * here a sample entry in the **logbook**. The run number, "run comment" and several other parameters are printed as (searchable) text in addition with the screenshot of the DAQ control to get all relevant data for this run in the logbook: [[image:attach:image2022-9-8_10-57-56.png||thumbnail="true" height="250"]]
... ... @@ -35,8 +35,6 @@
35 35  * NOTE: After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
36 36  * 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 ...
37 37  
38 -\\
39 -
40 40  === Checklist for proper saving of the data ===
41 41  
42 42  * 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 !!!)
... ... @@ -54,23 +54,19 @@
54 54  
55 55  If not all points of the list are o.k. there may be some problem with the writing of the data. Look to the troubleshooting section and / or talk to beamline stuff.
56 56  
57 -\\
58 58  
59 59  === More infos on the tools to check the proper saving of the data ===
60 60  
61 -\\
62 62  
63 63  ==== DAQ monitor ====
64 64  
65 65  The DAQ monitor shows a predefined selection of parameters as they are received in the DAQ //before// writing to a file. Here one can check if the desired data //arrives// in the DAQ and if the ranges are set correctly (e.g. sufficient acquisition time). The parameters to look at are defined before the beamtime with the local contact / DAQ group (details see below)
66 66  
67 -\\
68 68  
69 69  ==== Offline DAQ monitor ====
70 70  
71 71  This tool looks if a predefined selection of parameters is saved in the raw file. When a raw.-file reached its maximum size ( ~~ 1 GB) it is closed and a new file is opened. Once closed, the Offline DAQ monitor reads the file and checks if there are entries for the selected parameters. It shows the fraction of events containing data. For “fast” data (data written with 10 Hz and bunch ID synchronous like images, ADC traces) this should be close to 100%. For “slow” data (saved about every second e.g. pressures , temperatures...) this is about 10-20%. **However it is to note** that this program just check if there is **anything** saved. It does not check if it is the proper data.
72 72  
73 -\\
74 74  
75 75  ==== DAQ Data GUI ====
76 76  
... ... @@ -78,15 +78,15 @@
78 78  
79 79  [[image:attach:daqgui3.png||height="250"]][[image:attach:DAQgui2.jpg||height="250"]][[image:attach:DAQgui1.jpg||height="250"]]
80 80  
81 -\\
82 82  
83 -The DAQ Data GUI is a general tool to select and visualize data that was saved in the DAQ . It has in addition simple analysis options like histogram, mean, min or max values as function of time etc. Also correlations between different parameters can be analyzed in the tool. More details can be found [[How to Use the FLASH DAQ Data GUI?~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FLASHDAQdataGUI||shape="rect"]] and [[ here (DAQdataGUI link collection) >>doc:FLASH.How to get the data out of the DAQ]]
72 +The DAQ Data GUI is a general tool to select and visualize data that was saved in the DAQ . It has in addition simple analysis options like histogram, mean, min or max values as function of time etc. Also correlations between different parameters can be analyzed in the tool. More details can be found [[How to Use the FLASH DAQ Data GUI?~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FLASHDAQdataGUI||shape="rect"]] and [[ here (DAQdataGUI link collection) >>doc:FLASH.How to get the data out of the DAQ]]
84 84  
85 -The tool (separate Java program) can be started [[DAQdataGUI~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://ttfinfo2.desy.de/common/applications/DAQdataGUI-experimental.jnlp||shape="rect"]] or in the DAQ control panel ( lower right) on your local user console (Linux or Windows) or log  onto the COntrol machines: {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} (there you also may start via  {{code language="none"}}DAQdataGUI{{/code}} from the command line).
74 +The tool (separate Java program) can be started [[DAQdataGUI~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>url:http://ttfinfo2.desy.de/common/applications/DAQdataGUI-experimental.jnlp||shape="rect"]] or in the DAQ control panel ( lower right) on your local user console (Linux or Windows) or log  onto the COntrol machines: {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} (there you also may start via  {{code language="none"}}DAQdataGUI{{/code}} from the command line).
86 86  
87 87  
88 -\\To access the desired data one has to:
89 89  
78 +To access the desired data one has to:
79 +
90 90  * enter the {{code language="none"}}run number{{/code}} of the run you want to look at at //Run//
91 91  * select your DAQ in the //Experiment// drop down menu: {{code language="none"}}FLASHy_USERx{{/code}}
92 92  * press {{code language="none"}}get Channels/Files{{/code}}
... ... @@ -93,24 +93,20 @@
93 93  * 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) )
94 94  * 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.
95 95  
96 -\\
97 -
98 98  === How to get the data out for analysis (short summary) ===
99 99  
100 100  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 ...)
101 101  
102 102  * The FLASH DAQ system records the data in binary " {{code language="none"}}.raw{{/code}} " files.
103 -** (% 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).
104 104  ** 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 ...
105 105  
106 -\\
107 -
108 108  * To ease the data analysis we IN ADDITION provide //ON REQUEST// the data from the FLASH DAQ as HDF5 format
109 109  ** 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 ...
110 110  ** [[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
111 111  ** [[Short examples>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]] and [[user provided examples>>doc:FLASH.OUTDATED - Collection of user codes]] on how to read HDF5 in Matlab (no longer recommended).
112 112  
113 -The HDF5 files (online and summary) are saved in the [["gpfs" system ~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://confluence.desy.de/display/ASAP3/Architecture||shape="rect"]]. it can be accessed from [[Windows and Linux computers at DESY~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://confluence.desy.de/display/ASAP3/Mounting+the+storage+system+at+the+beamline||shape="rect"]] by the persons ( logins) which are registered for the beamtime in DOOR ( functional accounts
99 +The HDF5 files (online and summary) are saved in the [["gpfs" system ~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>url:https://confluence.desy.de/display/ASAP3/Architecture||shape="rect"]]. it can be accessed from [[Windows and Linux computers at DESY~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>url:https://confluence.desy.de/display/ASAP3/Mounting+the+storage+system+at+the+beamline||shape="rect"]] by the persons ( logins) which are registered for the beamtime in DOOR ( functional accounts
114 114  
115 115  The path to your data is structured the following way:
116 116  
... ... @@ -119,30 +119,25 @@
119 119  
120 120  More details and links can be found in the [[doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome]].
121 121  
122 -\\
123 123  
124 -\\
125 125  
126 -\\
127 127  
128 128  == Setting up the DAQ - DAQ Run Control GUI (local contacts, FLASH stuff) ==
129 129  
130 130  This section is intended for the local contacts / FLASH staff to set up the DAQ according to the needs of users before the beamtime. For troubleshooting this may also be helpful for users ...
131 131  
132 -\\
133 133  
134 134  === Configuring the DAQ ===
135 135  
136 136  [[image:attach:RCGUI_2.jpg||height="400"]]
137 -\\
119 +
138 138  
139 -\\
140 140  
141 -Using the jddd DAQ control panel one can start and stop runs but in order to configure the DAQ which data to save one has to use a a separate *DAQ run control * java application. Since it needs write access to DOOCS internal file systems, which can not be made available elsewhere one has to start the system on our linux user consoles at the beamline or on the  DOOCS control computers {{code language="none"}}flashlxuser1.desy.de, flashlxuser2.desy.de {{/code}} or {{code language="none"}}flashlxuser3.desy.de{{/code}}.
142 -Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via fastX3 or {{code language="none"}}Remote desktop{{/code}} from windows or via ssh from Linux machines.
122 +Using the jddd DAQ control panel one can start and stop runs but in order to configure the DAQ which data to save one has to use a a separate *DAQ run control * java application. Since it needs write access to DOOCS internal file systems, which can not be made available elsewhere one has to start the system on our linux user consoles at the beamline or on the  DOOCS control computers {{code language="none"}}flashlxuser1.desy.de, flashlxuser2.desy.de {{/code}} or {{code language="none"}}flashlxuser3.desy.de{{/code}}.
123 +Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via fastX3 or {{code language="none"}}Remote desktop{{/code}} from windows or via ssh from Linux machines.
143 143  Once logged in to {{code language="none"}}flashlxuser1,2,3{{/code}} the DAQ run control can be started in the "advanced"  Tab of the DAQ control :
144 144  
145 -[[image:attach:image2022-9-8_11-14-7.png||border="true" width="343" height="250"]]
126 +[[image:attach:image2022-9-8_11-14-7.png||border="true" height="250" width="343"]]
146 146  
147 147  Or in the command line:
148 148  
... ... @@ -188,21 +188,17 @@
188 188  FLASH2_USER2 DAQ
189 189  )))
190 190  
191 -\\
192 -
193 193  Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.
194 194  
195 195  [[image:attach:RCGUI_properties.jpg||height="400"]]
196 196  
197 -\\
198 198  
199 -Using the {{code language="none"}}Add{{/code}} and {{code language="none"}}Rem(ove){{/code}} buttons one can move the desired "subsystems" in the included side - meaning that they are saved. The "subsystems" contain typically several DOOCS parameters. E.g. {{code language="none"}}EXPERIMENT_MHZ_ADC_BL1{{/code}} contains all relevant DOOCS properties of the four  MHZ ADC channels available at BL1. To get a detailed information about the saved parameters one can have a look to the "Show Properties in Subsystems" button . In addition, a list of all possible subsystems and their description can be found [[here>>doc:FLASHUSER.Configuring the user DAQs]].
177 +Using the {{code language="none"}}Add{{/code}} and {{code language="none"}}Rem(ove){{/code}} buttons one can move the desired "subsystems" in the included side - meaning that they are saved. The "subsystems" contain typically several DOOCS parameters. E.g. {{code language="none"}}EXPERIMENT_MHZ_ADC_BL1{{/code}} contains all relevant DOOCS properties of the four  MHZ ADC channels available at BL1. To get a detailed information about the saved parameters one can have a look to the "Show Properties in Subsystems" button . In addition, a list of all possible subsystems and their description can be found [[here>>doc:FLASH.Configuring the user DAQs]].
200 200  
201 -\\
202 202  
203 203  === Configuring the DAQ monitor ===
204 204  
205 -The DAQ monitor ( and the Offline monitor) can be configured using DAQdataGUI.
182 +The DAQ monitor ( and the Offline monitor) can be configured using DAQdataGUI.
206 206  Load a test run containing all relevant properties. Select all properties you want to monitor. Use {{code language="none"}}Tools -> Channels to DAQMonitor{{/code}} and choose your DAQ. This sends a list with the selected properties to the DAQ monitor of your system.
207 207  
208 208  [[image:attach:daq_monitor_config.png||height="400"]]
... ... @@ -211,30 +211,27 @@
211 211  
212 212  In order to "activate" and test your configuration you have to start a run with the new configuration. **NOTE: Whenever the configuration was changed with the RCGUI the new run HAS to be started with the RCGUI **(starting with the jddd DAQ panel would only start the last configuration that has been running before !!!
213 213  
214 -\\
215 215  
216 -To START a run - meaning starting to save the experiment related data - one has to press the "start" button in the Run Control GUI. This opens a confirmation window asking if you really want to start the run ("in default mode"). Press yes. Now it takes about 20 seconds for the system to start up and start recording data. Indication is the "Run Control: RUN" and "DAQ: RUN" greenish indicators on the upper left side of the run control.
192 +**To START** a run - meaning starting to save the experiment related data - one has to press the "start" button in the Run Control GUI. This opens a confirmation window asking if you really want to start the run ("in default mode"). Press yes. Now it takes about 20 seconds for the system to start up and start recording data. Indication is the "Run Control: RUN" and "DAQ: RUN" greenish indicators on the upper left side of the run control.
217 217  
218 -To STOP a run one has to press the "stop" button. This opens a window for comments. This contains already the actual Experiment name by default. Please leave this information in. Add a comment for your run. This comment will be printed into the logbook and can later on be used to identify individual runs ... note you are required to type in something otherwise the run will not stop.
194 +**To STOP** a run one has to press the "stop" button. This opens a window for comments. This contains already the actual Experiment name by default. Please leave this information in. Add a comment for your run. This comment will be printed into the logbook and can later on be used to identify individual runs ... note you are required to type in something otherwise the run will not stop.
219 219  
220 220  The stopping also needs about 20 seconds.*_IT IS IMPORTANT_ not to start and stop the DAQ while it is still ramping up or down. So please wait before restarting the DAQ.*
221 221  
222 222  After the run use the DAQ data GUI to check if the data intended is saved properly.
223 223  
224 -\\
225 225  
226 226  === Load/Save the configuration ===
227 227  
228 228  [[image:attach:whitelist.jpg||height="250"]]
229 229  
230 -Once a list of subsystems is defined and tested this parameter combination should then be saved in a so-called //white list//. By loading this white list one can then easily configure the DAQ after changes / restarts ... to the initially defined settings to save the correct data.
231 -The whitelist can be saved/loaded with the Run Control GUI by: {{code language="none"}}File -> Group White List -> Save/Load{{/code}}. Note, while the top left rectangle's background of time and date is yellow, don't try any further controls of the GUI, you might confuse the program. It is busy reading the configuration from the run control database. The background changes back to grey when it has finished.
232 -\\The filename convention for the White Lists are arranged in the way:
205 +Once a list of subsystems is defined and tested this parameter combination should then be saved in a so-called //white list//. By loading this white list one can then easily configure the DAQ after changes / restarts ... to the initially defined settings to save the correct data.
206 +The whitelist can be saved/loaded with the Run Control GUI by: {{code language="none"}}File -> Group White List -> Save/Load{{/code}}. Note, while the top left rectangle's background of time and date is yellow, don't try any further controls of the GUI, you might confuse the program. It is busy reading the configuration from the run control database. The background changes back to grey when it has finished.
207 +\\The filename convention for the White Lists are arranged in the way:
233 233  //DAQ name// - //Date of creation// - //name of the PI / Experiment// - //optional comment on the type of data//
234 234  
235 235  The whitelists are stored in separate folders for each beamline.
236 236  
237 -\\
238 238  
239 239  === Choosing the file size ===
240 240  
... ... @@ -254,51 +254,41 @@
254 254  
255 255  This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again.
256 256  
257 -\\
258 258  
259 -\\
260 260  
261 -\\
262 262  
263 -\\
264 264  
265 265  === Assigning the DAQ to the beamline in jddd ===
266 266  
267 267  To assign which DAQ is used at what beamline one has to use the dropdown menu in the {{code language="none"}}parameter monitor{{/code}}. In each Beamline overview tab (BL1,2,3) there is a button (upper right) that starts the {{code language="none"}}parameter monitor{{/code}} panel. In the upper middle is a DAQ field in which the appropriate DAQ can be assigned to the Beamline.
268 268  
269 -\\
239 +[[image:attach:image2022-9-9_9-51-8.png||height="150"]]
270 270  
241 +
271 271  === Setting the logbook to print in / putting the Whitelist name in jddd ===
272 272  
273 -The jddd DAQ Control should be set up that it prints by default the relevant run information in the logbook associated to your beamline [[Logbooks>>doc:FLASH.Electronic Logbooks]]
244 +The jddd DAQ Control should be set up that it prints by default the relevant run information in the logbook associated to your beamline [[Logbooks>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.E-Logbooks.WebHome]]
274 274  
275 275  Define logbook / and whitelist for display in the jddd DAQ control (jddd otherwise does not "know" which White list was used ... this has to be put in by hand ...up to now)
276 276  
277 277  [[image:attach:setting_parameters.jpg||height="400"]]
278 278  
279 -\\
280 280  
281 -\\
282 282  
283 283  == In case something goes wrong: Troubleshooting ==
284 284  
285 -\\
286 -
287 287  === No //START// or //STOP// buttons are visible in the DAQ control panel ===
288 288  
289 289  The jddd GUI only shows the Start and stop button if the DAQ is in the "Idle" state. Sometimes the DAQ "just" gets stuck in the stopping phase. Then stopping again or starting form the not "Idle" state can help. For this goto the "Advanced" tab of the jddd DAQ control . there the START and STOP buttons are always available ... independent of the state of the DAQ. If this does not help you may have to restart the DAQ ...
290 290  
291 -\\
292 292  
293 293  === The DAQ does not start a run ===
294 294  
295 -\\
296 296  
297 -* Mainly the DAQ works fine but one of the properties that should be saved is not available or somehow corrupted. There the {{code language="none"}}RC logfile{{/code}} helps (see below) to determine where to localize the problem. The pragmatic way is to exclude the subsystems which may contain the properties with problems. Thus exclude the "critical" subsystems. Start a run. If this works, include one by one the excluded subsystems and start runs. That way one should find out which subsystem causes the problem. Now one can investigate this one in more detail. Is the property available in DOOCS? Does it update? maybe restart the server providing the property ...
262 +* Mainly the DAQ works fine but one of the properties that should be saved is not available or somehow corrupted. There the {{code language="none"}}RC logfile{{/code}} helps (see below) to determine where to localize the problem. The pragmatic way is to exclude the subsystems which may contain the properties with problems. Thus exclude the "critical" subsystems. Start a run (starting with the RCGUI not with jddd DAQ control ). If this works, include one by one the excluded subsystems and start runs. That way one should find out which subsystem causes the problem. Now one can investigate this one in more detail. Is the property available in DOOCS? Does it update? maybe restart the server providing the property ...
298 298  
299 -\\
264 + as example: [[image:url:https://ttfinfo.desy.de/FELPGMelog/data/2017/15/11.04/2017-04-11T02:56:05-00.PNG||height="250"]]
300 300  
301 -\\
302 302  
303 303  === Data seems not properly saved ===
304 304  
... ... @@ -313,80 +313,67 @@
313 313  * Sometimes also a restart of the DAQ (see below) helps ... This however is more the case if the DAQ does not start at all or saves no data at all ...
314 314  * in several cases the reason is a configuration problem of the server. Then 2 servers are sending on the same "address". Then one property usually is saved without loss while the second one is only saved once in a while ( 1-5%). Here the server has to be fixed. As fast cure one can only exclude the less important subsystem and save the more important properly ...
315 315  
316 -\\
317 317  
318 -\\
319 319  
320 -\\
321 -
322 322  === Restarting the DAQ ===
323 323  
324 -\\
325 325  
326 326  * 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 ...
327 327  
328 -\\
287 +* Generally there** 3 ways to "restart" the DAQ**
288 +** 1. The least interfering way is the "**all to INITIALIZE**" that tries to reset the DAQ processes ... helps for simple "hickups"
289 +** 2. The "**re-start DAQ**" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
290 +** 3. In very hard and severe cases there is the **ultimate restart button: "re-start DAQ (no RCSHM)"**
329 329  
330 -* Generally there 3 ways to "restart" the DAQ
331 -** 1. The least interfering way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
332 -** 2. The "re-start DAQ" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
333 -** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
292 +//**Here in more detail:**//
334 334  
335 335  
336 -\\//**Here in more detail:**//
337 -
338 -\\
339 -
340 340  * if the DAQ gets stuck in the starting or stopping procedure one can try to initialize the DAQ or in the worst case restart it.
341 -** **to be able to restart the DAQ one has to run jddd on the {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} (up to now ( 2021) the restat on our consoles (cons0...12) is NOT reliably possible ) : log in at one of these machines with your beamline account (e.g. bl1user or fl24user). Start jddd with the {{code language="none"}}flash{{/code}} command. Click on "Photons" -> Experimental Hall "Photons main panel"**
342 -** The DAQ "expert" panel can be reached from the User DAQ control panel.
296 +** **to be able to restart the DAQ one has to run jddd on Linux in the DESY network, meaning wither on our User consoles in the Experimental halls (cons0...12)  or on  {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}}. Log in at one of these machines with your beamline account (e.g. bl1user or fl24user). **(On the flashlxuser machines there are no desktop icons to start jddd. Here you can use  the  shell command: {{code language="none"}}flash ->{{/code}} Click on "Photons" -> "Photons main panel" )
297 +** To Restart the DAQs you need the **"expert" Tab** of the  User DAQ control panel.
343 343  
344 - [[image:attach:DAQ_expert.jpg||height="400"]]
345 -\\
299 + [[image:attach:image2022-9-9_10-57-31.png||height="400"]]
300 +
346 346  
347 -*
348 -** Then you see the following "DAQ expert panel":
349 -** first one may try the "all to INITIALIZE" button. it starts a script window and asks for the passwd (the beamline accounts (blxuser) should have the according rights. vuvfuser has it for sure. The script sets all subcomponents to initialize. It is helpful if one subcomponent got stuck.
302 +There is some description of the different ways to restart the DAQ in the panel:
350 350  
351 - [[image:attach:UserDAQ_status.jpg||height="400"]]
352 -\\
304 +==== **all to INITIALIZE** ====
353 353  
354 -\\
355 355  
356 -* If this does not help you have to "re-start DAQ". This completely restarts all processes and takes a while. A script window appears and shows what steps are actually done. At the end is sais: "Cleanup finished".
307 +*
308 +** First, one may try the "**all to INITIALIZE"** button. It starts a script window showing the progress of the initialization. The script sets all subcomponents to initialize. It is helpful if one subcomponent got stuck.
309 +** If there is no window coming up or closing right away there may be a problem with the rights. In this case you:
310 +*** may try to login at the flashlxuser machines and try there again
311 +*** or use the red "DAQ restart" Button one below. This button reacts technically different and can circumvent rights problems ... 
357 357  
358 - [[image:attach:DAQ_restart_msg.jpg||height="400"]]
313 +
314 + Initialize script: [[image:attach:image2022-9-9_11-6-38.png||height="250"]] parts of the DAQ are in different "states":[[image:url:https://ttfinfo.desy.de/Flash_THzStreakingelog/data/2020/49/2020-12-02T13:53:01.jpg||height="250"]]
359 359  
360 -\\
361 361  
362 -* For the "re-start DAQ" the DAQ should come up in the same state as before. Meaning that the subsystems (ADCs, cameras ..) are still loaded and displayed. If this is not the case you can try to load your white list and start a new run. If the data is saved correctly you are done.
317 +==== Restart the DAQ ====
363 363  
364 -\\
365 365  
366 -* **IF the DAQ still does not work properly** the final option is the: "re-start DAQ (no RCSHM)". This button does the same as the "re-start DAQ" but the Run Controller shared memory is **not** re-stored. It means that after the DAQ is back no run configuration is selected.
367 -** in the jddd control the list of subsystems sais "empty"
368 -** in the RCGUI in the lower part it sais "RUN mode is not set"
320 +* If the "initialize"  does not help,  you have to "re-start DAQ". This completely restarts all processes and takes a while. A script window appears and shows what steps are actually done. At the end is sais: "Cleanup finished".
321 +* There are **actually 2 buttons** to "restart" the DAQ. They start the same restarting script - however in different ways. Thus, if one for what ever reason does not work with your configuration you may use the second one ... 
369 369  
370 - [[image:attach:restart_RCM_no_runmode.jpg||height="400"]]
371 -\\
323 + Script window:  [[image:attach:DAQ_restart_msg.jpg||height="400"]] Restart: [[image:attach:image2022-9-9_11-30-33.png||height="400"]]
372 372  
373 -\\
374 374  
375 -*
376 -** one has to go to the "Run Modes" tab and select the run mode {{code language="none"}}FLASH1_EXP{{/code}} by clicking on it and choose the desired file size (stored settings)
377 -** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
378 -** finally you have to select your White list and start a run ...
326 +* For the "re-start DAQ" the DAQ should come up in the same state as before. Meaning that the subsystems (ADCs, cameras ..) are still loaded and displayed. If this is not the case you can try to load your white list and start a new run. If the data is saved correctly you are done.
379 379  
380 -\\
328 +==== "Ultimate" restart ====
381 381  
382 -\\
330 +* **IF the DAQ still does not work properly** the final option is the: " "Ultimate" re-start DAQ (no RCSHM)". This button does the same as the "re-start DAQ" but the Run Controller shared memory is **not** re-stored. It means that after the DAQ is back no run configuration is selected.
331 +** in the jddd control the list of subsystems sais "empty" [[image:attach:image2022-9-9_11-36-1.png||thumbnail="true" height="250"]]
332 +** and you have to reload the parameters to be saved from the  Whitelist.
333 +** you can use the "Runcontrol"  button right below the  "Ultimate" re-start DAQ (no RCSHM)" to start the RunControl window
334 +** choose the files ize ( best default: 1GB)[[image:attach:image2022-9-9_11-39-3.png||thumbnail="true" height="250"]]
335 +** goto "Subsystems" tab and load your Whitelist
336 +** and start a run ...
383 383  
384 384  * If there are still components not working after the "re-start DAQ (no RCSHM)" you have to call the photon coordinator (4455) and pray ...
385 385  
386 -\\
387 387  
388 -\\
389 -
390 390  ----
391 391  
392 392  == [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]] ==
... ... @@ -397,23 +397,25 @@
397 397  
398 398  This can be done easiest by going to the run modes and choose a different "stored setting" (changing e.g. from filesize 100 MB to 350 MB) and going back to subsystems. At this point the new database entries are read in. then one can do the same backwards to switch back to the initial file size. Doing this the configured list of subsystems is lost and one has to reload the whitelist and start a run to get the loaded whitelist in the configuration.
399 399  
400 -\\
401 401  
402 402  OR one can do the hard way:
403 403  
404 404  On flashlxuser1,2 or 3 start RCGUIFL1USER1 or appropriate to the DAQ you want to reconfigure. Select the tab "Run Modes". To then reload or re-init the run control database you need the expert menu entry:
405 405  
406 -{{code language="none"}}Options -> "Show Expert Menu"{{/code}}
356 +{{code language="none"}}
357 +Options -> "Show Expert Menu"
358 +{{/code}}
407 407  
408 408  Then you go to {{code language="none"}}"Expert" -> "Run Control Commands" -> "Remove SHM"{{/code}} (occasionally twice).
409 409  
410 410  After you see a message in the RCGUI messages window that the SHM was removed you do:
411 411  
412 -{{code language="none"}}"expert" -> "Run Control Commands" -> "Re-init SHM"{{/code}}
364 +{{code language="none"}}
365 +"expert" -> "Run Control Commands" -> "Re-init SHM"
366 +{{/code}}
413 413  
414 414  Now close the RCGUI and start it again. Switch to the tab "subsystems", wait for the subsystems to be reloaded and load the whitelist you want to use.
415 415  
416 -\\
417 417  
418 418  Tracking DAQ restarts
419 419  
... ... @@ -427,7 +427,6 @@
427 427  
428 428  The red flags next to the  different stream indicators tell something about data base errors
429 429  
430 -\\
431 431  
432 432  [[image:attach:2021-02-10 15_23_20-How to save data in the User DAQ - FS-FLASH USER - DESY Confluence.png||width="600"]]
433 433  
... ... @@ -436,3 +436,23 @@
436 436  lower flag: There was a problem to read dccp catalogue.
437 437  
438 438  In both cases there are counters of failures to read a catalogue. If this counter is not incrementing with every attempt to read a catalogue, then it's no problem. It can be monitored and reset in the panel that one gets by pressing on "green" area.
391 +
392 +
393 +=== raw writers ===
394 +
395 +(all user DAQs are using stream 2) [[image:attach:image-2023-12-14_13-50-19.png||width="318"]]
396 +
397 +what raw writers are used ? ... They are defined in {{code language="none"}}FLASH.DAQ/FLxUSERy.EVENTBUILDER/EVB.STREAM.2/EVB.ROOT.SRVRS {{/code}} as XML string
398 +
399 +what is the current raw writer? ... {{code language="none"}}FLASH.DAQ/FLxUSERy.EVENTBUILDER/EVB.STREAM.2/CUR.RAW.WRITER{{/code}}
400 +
401 +OR
402 +
403 +one can have a look at the Offline monitor :[[image:attach:image-2023-12-14_13-51-33.png||width="406"]]
404 +
405 +FLASH.DAQ/FL1USER1.DAQ.OFFL.MONITOR/MONITOR/LAST.FILE
406 +
407 +FLASH.DAQ/FL1USER1.DAQ.OFFL.MONITOR/MONITOR/CUR.WRITER
408 +
409 +
410 +
2021-02-10 15_23_20-How to save data in the User DAQ - FS-FLASH USER - DESY Confluence.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +43.7 KB
Content
DAQ_expert.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +0 bytes
Content
DAQ_restart_msg.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +114.4 KB
Content
DAQgui1.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +243.3 KB
Content
DAQgui2.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +192.6 KB
Content
RCGUI_2.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +139.3 KB
Content
RCGUI_properties.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +178.5 KB
Content
RC_logfile.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +154.7 KB
Content
UserDAQ_status.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +92.8 KB
Content
daq_monitor_config.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +82.3 KB
Content
daqgui3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +86.7 KB
Content
image-2023-12-14_13-50-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +6.5 KB
Content
image-2023-12-14_13-51-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +24.0 KB
Content
image2019-10-24_15-29-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +282.7 KB
Content
image2019-10-24_15-32-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +370.6 KB
Content
image2020-1-17_13-39-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +343.1 KB
Content
image2022-9-8_10-50-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +242.2 KB
Content
image2022-9-8_10-57-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +278.7 KB
Content
image2022-9-8_11-14-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
image2022-9-9_10-57-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +447.8 KB
Content
image2022-9-9_11-23-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +81.5 KB
Content
image2022-9-9_11-24-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +1.1 MB
Content
image2022-9-9_11-30-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +376.2 KB
Content
image2022-9-9_11-36-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +38.2 KB
Content
image2022-9-9_11-39-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +52.8 KB
Content
image2022-9-9_11-6-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +190.5 KB
Content
image2022-9-9_9-51-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +155.3 KB
Content
jddd_DAQ-control-manual-how_to_get.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +240.6 KB
Content
jddd_DAQ-control-manual2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +208.4 KB
Content
restart_RCM_no_runmode.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
runmode_set.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
setting_parameters.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +42.1 KB
Content
whitelist.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +26.4 KB
Content