Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 12.1
edited by sndueste
on 2019-10-24 16:04
Change comment: There is no comment for this version
To version 20.1
edited by sndueste
on 2020-03-19 09:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -98,7 +98,6 @@
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]]
102 102  ** 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 ...
103 103  
104 104  \\
... ... @@ -116,7 +116,7 @@
116 116  * /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 ...)
117 117  * as example: {{code language="none"}}/asap3/flash/gpfs/bl2/2017/data/11003163/raw/hdf/{{/code}}
118 118  
119 -More details and links can be found in the [[doc:FLASHUSER.User overview]].
118 +More details and links can be found in the [[doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome]].
120 120  
121 121  \\
122 122  
... ... @@ -190,8 +190,8 @@
190 190  
191 191  === Configuring the DAQ monitor ===
192 192  
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.
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.
195 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]]
196 196  
197 197  \\
... ... @@ -242,11 +242,11 @@
242 242  
243 243  To choose the desired filesize one has to choose a run mode configuration in the RunControlGUI
244 244  
245 -[[image:attach:image2019-10-24_15-29-36.png||height="400"]]
244 +[[~[~[image:attach:image2020-1-17_13-39-38.png~|~|height="400"~]~]>>attach:image2020-1-17_13-39-38.png]]
246 246  
247 -This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again:
246 +This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again.
248 248  
249 -[[image:attach:image2019-10-24_15-32-5.png||thumbnail="true" height="250"]]
248 +\\
250 250  
251 251  \\
252 252  
... ... @@ -326,12 +326,12 @@
326 326  ** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
327 327  
328 328  
329 -\\*Here in more detail:*
328 +\\//**Here in more detail:**//
330 330  
331 331  \\
332 332  
333 333  * 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.
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"
333 +** **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"**
335 335  ** The DAQ "expert" panel can be reached from the User DAQ control panel.
336 336  [[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_expert.jpg~|~|alt="DAQ_expert.jpg" width="400" height="350"~]~]>>attach:DAQ_expert.jpg]]
337 337  
... ... @@ -365,9 +365,8 @@
365 365  \\
366 366  
367 367  *
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.
367 +** 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)
368 +** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
371 371  ** finally you have to select your White list and start a run ...
372 372  
373 373  \\
... ... @@ -382,11 +382,17 @@
382 382  
383 383  ----
384 384  
385 -[[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]]
383 +== [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]] ==
386 386  
385 +=== Re-read the data base ===
386 +
387 +If there are new Properties included by Vladimir et al one has to reread the data base.
388 +
389 +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.
390 +
387 387  \\
388 388  
389 -=== Re-read the data base ===
393 +OR one can do the hard way:
390 390  
391 391  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:
392 392  
... ... @@ -399,3 +399,17 @@
399 399  {{code language="none"}}"expert" -> "Run Control Commands" -> "Re-init SHM"{{/code}}
400 400  
401 401  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.
406 +
407 +\\
408 +
409 +=== data base errors ===
410 +
411 +The red flags next to the  different stream indicators tell something about data base errors
412 +
413 +[[image:url:https://mail.desy.de/service/home/~~/?auth=co&loc=de&id=154203&part=2.2||width="788" height="140"]]
414 +
415 +upper flag:  There was a problem to read run catalogue
416 +
417 +lower flag: There was a problem to read dccp catalogue.
418 +
419 +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.