Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 23.1
edited by cpassow
on 2021-02-10 12:43
Change comment: There is no comment for this version
To version 12.1
edited by sndueste
on 2019-10-24 16:04
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.cpassow
1 +XWiki.sndueste
Content
... ... @@ -98,6 +98,7 @@
98 98  
99 99  * The FLASH DAQ system records the data in binary " {{code language="none"}}.raw{{/code}} " files.
100 100  ** [[reading the data 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]] works 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).
101 +** Examples how to read from {{code language="none"}}.raw{{/code}} files can also be found in [[the user code collection>>doc:FLASH.Collection of user codes]]
101 101  ** 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 ...
102 102  
103 103  \\
... ... @@ -115,7 +115,7 @@
115 115  * /asap3/flash/gpfs/ //beamline used// / //year// /data/ //Beamtime application number// /raw/hdf/ (the //Beamtime application number// can be fund in the pdf schedule sent around by Rolf ...)
116 116  * as example: {{code language="none"}}/asap3/flash/gpfs/bl2/2017/data/11003163/raw/hdf/{{/code}}
117 117  
118 -More details and links can be found in the [[doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome]].
119 +More details and links can be found in the [[doc:FLASHUSER.User overview]].
119 119  
120 120  \\
121 121  
... ... @@ -189,11 +189,14 @@
189 189  
190 190  === Configuring the DAQ monitor ===
191 191  
192 -The DAQ monitor ( and the Offline monitor) can be configured using DAQdataGUI.
193 -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.
193 +The DAQ monitor ( and the Offline monitor) can be confgured using DAQdataGUI.
194 +Load a test run containing all relavant propoerties. 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.
195 +[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/daq_monitor_config.png~|~|alt="daq_monitor_config.png" width="700" height="390"~]~]>>attach:daq_monitor_config.png]]
194 194  
195 -[[image:attach:daq_monitor_config.png||height="400"]]
197 +\\
196 196  
199 +\\
200 +
197 197  === Start and Stop a run ===
198 198  
199 199  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 !!!
... ... @@ -238,11 +238,11 @@
238 238  
239 239  To choose the desired filesize one has to choose a run mode configuration in the RunControlGUI
240 240  
241 -[[~[~[image:attach:image2020-1-17_13-39-38.png~|~|height="400"~]~]>>attach:image2020-1-17_13-39-38.png]]
245 +[[image:attach:image2019-10-24_15-29-36.png||height="400"]]
242 242  
243 -This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again.
247 +This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again:
244 244  
245 -\\
249 +[[image:attach:image2019-10-24_15-32-5.png||thumbnail="true" height="250"]]
246 246  
247 247  \\
248 248  
... ... @@ -322,12 +322,12 @@
322 322  ** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
323 323  
324 324  
325 -\\//**Here in more detail:**//
329 +\\*Here in more detail:*
326 326  
327 327  \\
328 328  
329 329  * 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.
330 -** **to be able to restart the DAQ one has to run jddd on the {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}} (up to now ( 2020) the restat on our consoles (cons0...12) is NOT possible yet [[image:url:http://hasfweb.desy.de/pub/TWiki/SmiliesPlugin/frown.gif||alt="frown"]]) : 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"**
334 +** to be able to restart the DAQ one has to run jddd on the {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}} (up to now (Aug 2018) the restat on our consoles (cons0...12) is NOT possible yet [[image:url:http://hasfweb.desy.de/pub/TWiki/SmiliesPlugin/frown.gif||alt="frown"]]) : log in at one of these machines with your beamline account (e.g. bl1user or fl24user). Start jddd with the {{code language="none"}}jFLASH{{/code}} command. Click on "Photons" -> Experimental Hall "Photons main panel"
331 331  ** The DAQ "expert" panel can be reached from the User DAQ control panel.
332 332  [[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_expert.jpg~|~|alt="DAQ_expert.jpg" width="400" height="350"~]~]>>attach:DAQ_expert.jpg]]
333 333  
... ... @@ -361,8 +361,9 @@
361 361  \\
362 362  
363 363  *
364 -** 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)
365 -** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
368 +** one has to go to the "Run Modes" tab and select the run mode {{code language="none"}}FLASH1_EXP{{/code}} by clicking on it !
369 +[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/runmode_set.jpg~|~|alt="runmode_set.jpg" width="400" height="400"~]~]>>attach:runmode_set.jpg]]
370 +** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . now all subsystems are included.
366 366  ** finally you have to select your White list and start a run ...
367 367  
368 368  \\
... ... @@ -377,17 +377,11 @@
377 377  
378 378  ----
379 379  
380 -== [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]] ==
385 +[[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]]
381 381  
382 -=== Re-read the data base ===
383 -
384 -If there are new Properties included by Vladimir et al one has to reread the data base.
385 -
386 -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.
387 -
388 388  \\
389 389  
390 -OR one can do the hard way:
389 +=== Re-read the data base ===
391 391  
392 392  On flashlxuser1 or 2 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:
393 393  
... ... @@ -400,25 +400,3 @@
400 400  {{code language="none"}}"expert" -> "Run Control Commands" -> "Re-init SHM"{{/code}}
401 401  
402 402  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.
403 -
404 -\\
405 -
406 -Tracking DAQ restarts
407 -
408 -A system was implemented (March 2020) where each restart of a user DAQ is recorded in a log file
409 -
410 -One can see all log files in :
411 -
412 -/home/doocsadm/bm/rcdb/restartslog/
413 -
414 -=== data base errors ===
415 -
416 -The red flags next to the  different stream indicators tell something about data base errors
417 -
418 -[[image:url:https://mail.desy.de/service/home/~~/?auth=co&loc=de&id=154203&part=2.2||width="788" height="140"]]
419 -
420 -upper flag:  There was a problem to read run catalogue
421 -
422 -lower flag: There was a problem to read dccp catalogue.
423 -
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.