Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 27.1
edited by erlandm
on 2021-06-17 15:46
Change comment: There is no comment for this version
To version 32.1
edited by sndueste
on 2023-12-14 13:55
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.erlandm
1 +XWiki.sndueste
Tags
... ... @@ -1,0 +1,1 @@
1 +favourite
Content
... ... @@ -6,8 +6,8 @@
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 one at FLASH 2 (FLASH2_USER1)
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:FLASH.FLASH1 PhotDiag stream]] system.
10 +Other [[experiment related information>>doc:FLASH.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)
11 11  How to save this experiment related "User-Data" will be explained briefly in this page:
12 12  
13 13  \\
... ... @@ -20,19 +20,20 @@
20 20  
21 21  === DAQ control panel ===
22 22  
23 -To get to the User DAQ control one has to go to {{code language="none"}}Experiment control{{/code}} -> {{code language="none"}}User DAQ tab{{/code}} -> {{code language="none"}}FLxUSERy DAQ CTRL{{/code}}
23 +To get to the User DAQ control one has to go to {{code language="none"}}Experiment control{{/code}} -> {{code language="none"}}User DAQ tab{{/code}} -> {{code language="none"}}FLxUSERy DAQ CTRL {{/code}}
24 24  
25 -[[image:attach:jddd_DAQ-control-manual-how_to_get.png||height="400"]]
25 +[[image:attach:jddd_DAQ-control-manual-how_to_get.png||width="500"]][[image:attach:image2022-9-8_10-50-53.png||width="450"]]
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 -[[image:attach:jddd_DAQ-control-manual2.png||height="400"]]
28 +[[image:attach:jddd_DAQ-control-manual2.png||width="800"]]
29 29  \\\\
30 30  
31 31  \\
32 32  
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:FLASH.Electronic Logbooks]] (DESY internal link)
34 -* After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
35 -* 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 +* 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 +* 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 +* NOTE: After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
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 ...
36 36  
37 37  \\
38 38  
... ... @@ -81,7 +81,7 @@
81 81  
82 82  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]]
83 83  
84 -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 (Desy) PC. In some cases the access via Windows does not work. An option which should always work is to log onto {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} and start {{code language="none"}}DAQdataGUI{{/code}} from the command line.
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).
85 85  
86 86  
87 87  \\To access the desired data one has to:
... ... @@ -135,12 +135,16 @@
135 135  [[image:attach:RCGUI_2.jpg||height="400"]]
136 136  \\
137 137  
138 -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 DOOCS control computers {{code language="none"}}flashlxuser1.desy.de, flashlxuser2.desy.de {{/code}} or {{code language="none"}}flashlxuser3.desy.de{{/code}}.
139 -Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via X-Win32 from windows or via ssh from Linux machines.
140 -Once logged in to {{code language="none"}}flashlxuser1,2,3{{/code}} the DAQ run control can be started. Depending on the DAQ you want to use the commands are:
141 -
142 142  \\
143 143  
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.
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 +
145 +[[image:attach:image2022-9-8_11-14-7.png||border="true" width="343" height="250"]]
146 +
147 +Or in the command line:
148 +
144 144  (% class="wrapped" %)
145 145  |(((
146 146  Unix command
... ... @@ -175,7 +175,16 @@
175 175  )))|(((
176 176  FLASH2_USER1 DAQ
177 177  )))
183 +|(% colspan="1" %)(((
184 +{{code language="none"}}
185 +RCGUIFL2USER2
186 +{{/code}}
187 +)))|(% colspan="1" %)(((
188 +FLASH2_USER2 DAQ
189 +)))
178 178  
191 +\\
192 +
179 179  Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.
180 180  
181 181  [[image:attach:RCGUI_properties.jpg||height="400"]]
... ... @@ -182,7 +182,7 @@
182 182  
183 183  \\
184 184  
185 -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 4 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]].
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:FLASH.Configuring the user DAQs]].
186 186  
187 187  \\
188 188  
... ... @@ -199,9 +199,9 @@
199 199  
200 200  \\
201 201  
202 -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.
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.
203 203  
204 -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.
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.
205 205  
206 206  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.*
207 207  
... ... @@ -211,7 +211,7 @@
211 211  
212 212  === Load/Save the configuration ===
213 213  
214 -[[image:attach:whitelist.jpg||height="400"]]
228 +[[image:attach:whitelist.jpg||height="250"]]
215 215  
216 216  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.
217 217  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.
... ... @@ -252,11 +252,13 @@
252 252  
253 253  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.
254 254  
269 +[[image:attach:image2022-9-9_9-51-8.png||height="150"]]
270 +
255 255  \\
256 256  
257 257  === Setting the logbook to print in / putting the Whitelist name in jddd ===
258 258  
259 -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]]
275 +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]]
260 260  
261 261  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)
262 262  
... ... @@ -268,11 +268,9 @@
268 268  
269 269  == In case something goes wrong: Troubleshooting ==
270 270  
271 -\\
272 -
273 273  === No //START// or //STOP// buttons are visible in the DAQ control panel ===
274 274  
275 -~* 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 ...
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 ...
276 276  
277 277  \\
278 278  
... ... @@ -280,9 +280,9 @@
280 280  
281 281  \\
282 282  
283 -* 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 ...
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 (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 ...
284 284  
285 -\\
299 + as example: [[image:url:https://ttfinfo.desy.de/FELPGMelog/data/2017/15/11.04/2017-04-11T02:56:05-00.PNG||height="250"]]
286 286  
287 287  \\
288 288  
... ... @@ -313,10 +313,10 @@
313 313  
314 314  \\
315 315  
316 -* Generally there 3 ways to "restart" the DAQ
317 -** 1. The least interfering way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
318 -** 2. The "re-start DAQ" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
319 -** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
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)"**
320 320  
321 321  
322 322  \\//**Here in more detail:**//
... ... @@ -324,47 +324,52 @@
324 324  \\
325 325  
326 326  * 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.
327 -** **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"**
328 -** The DAQ "expert" panel can be reached from the User DAQ control panel.
341 +** **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" )
342 +** To Restart the DAQs you need the **"expert" Tab** of the  User DAQ control panel.
329 329  
330 - [[image:attach:DAQ_expert.jpg||height="400"]]
344 + [[image:attach:image2022-9-9_10-57-31.png||height="400"]]
331 331  \\
332 332  
333 -*
334 -** Then you see the following "DAQ expert panel":
335 -** 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.
347 +There is some description of the different ways to restart the DAQ in the panel:
336 336  
337 - [[image:attach:UserDAQ_status.jpg||height="400"]]
338 -\\
349 +==== **all to INITIALIZE** ====
339 339  
340 340  \\
341 341  
342 -* 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".
353 +*
354 +** 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.
355 +** If there is no window coming up or closing right away there may be a problem with the rights. In this case you:
356 +*** may try to login at the flashlxuser machines and try there again
357 +*** or use the red "DAQ restart" Button one below. This button reacts technically different and can circumvent rights problems ... 
343 343  
344 - [[image:attach:DAQ_restart_msg.jpg||height="400"]]
359 +
360 + 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"]]
345 345  
346 346  \\
347 347  
348 -* 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.
364 +==== Restart the DAQ ====
349 349  
350 350  \\
351 351  
352 -* **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.
353 -** in the jddd control the list of subsystems sais "empty"
354 -** in the RCGUI in the lower part it sais "RUN mode is not set"
368 +* 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".
369 +* 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 ... 
355 355  
356 - [[image:attach:restart_RCM_no_runmode.jpg||height="400"]]
357 -\\
371 + Script window:  [[image:attach:DAQ_restart_msg.jpg||height="400"]] Restart: [[image:attach:image2022-9-9_11-30-33.png||height="400"]]
358 358  
359 359  \\
360 360  
361 -*
362 -** 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)
363 -** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
364 -** finally you have to select your White list and start a run ...
375 +* 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.
365 365  
366 -\\
377 +==== "Ultimate" restart ====
367 367  
379 +* **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.
380 +** in the jddd control the list of subsystems sais "empty" [[image:attach:image2022-9-9_11-36-1.png||thumbnail="true" height="250"]]
381 +** and you have to reload the parameters to be saved from the  Whitelist.
382 +** you can use the "Runcontrol"  button right below the  "Ultimate" re-start DAQ (no RCSHM)" to start the RunControl window
383 +** choose the files ize ( best default: 1GB)[[image:attach:image2022-9-9_11-39-3.png||thumbnail="true" height="250"]]
384 +** goto "Subsystems" tab and load your Whitelist
385 +** and start a run ...
386 +
368 368  \\
369 369  
370 370  * If there are still components not working after the "re-start DAQ (no RCSHM)" you have to call the photon coordinator (4455) and pray ...
... ... @@ -422,3 +422,25 @@
422 422  lower flag: There was a problem to read dccp catalogue.
423 423  
424 424  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.
444 +
445 +\\
446 +
447 +=== raw writers ===
448 +
449 +(all user DAQs are using stream 2) [[image:attach:image-2023-12-14_13-50-19.png||width="318"]]
450 +
451 +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
452 +
453 +what is the current raw writer? ... {{code language="none"}}FLASH.DAQ/FLxUSERy.EVENTBUILDER/EVB.STREAM.2/CUR.RAW.WRITER{{/code}}
454 +
455 +OR
456 +
457 +one can have a look at the Offline monitor :[[image:attach:image-2023-12-14_13-51-33.png||width="406"]]
458 +
459 +FLASH.DAQ/FL1USER1.DAQ.OFFL.MONITOR/MONITOR/LAST.FILE
460 +
461 +FLASH.DAQ/FL1USER1.DAQ.OFFL.MONITOR/MONITOR/CUR.WRITER
462 +
463 +\\
464 +
465 +\\
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 +91.2 KB
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