Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 8.1
edited by sendels
on 2019-08-09 12:22
Change comment: added attachments and links
To version 18.1
edited by sndueste
on 2020-03-09 15:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sendels
1 +XWiki.sndueste
Content
... ... @@ -1,26 +2,7 @@
1 -\\
2 2  
3 -* General Concept
4 -* Taking User data: Starting and stopping runs (Users)
5 -** DAQ control panel
6 -** Checklist for proper saving of the data
7 -** More infos on the tools to check the proper saving of the data
8 -** How to get the data out for analysis (short summary)
9 -* Setting up the DAQ - DAQ Run Control GUI (local contacts, FLASH stuff)
10 -** Configuring the DAQ
11 -** Configuring the DAQ monitor
12 -** Start and Stop a run
13 -** Load/Save the configuration
14 -** Assigning the DAQ to the beamline in jddd
15 -** Setting the logbook to print in / putting the Whitelist name in jddd
16 -* In case something goes wrong: Troubleshooting
17 -** No START or STOP buttons are visible in the DAQ control panel
18 -** The DAQ does not start a run
19 -** Data seems not properly saved
20 -** Restarting the DAQ
21 -** what else ???
22 -** Re-read the data base
23 23  
3 +{{toc/}}
4 +
24 24  \\
25 25  
26 26  == General Concept ==
... ... @@ -117,7 +117,6 @@
117 117  
118 118  * The FLASH DAQ system records the data in binary " {{code language="none"}}.raw{{/code}} " files.
119 119  ** [[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).
120 -** 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]]
121 121  ** 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 ...
122 122  
123 123  \\
... ... @@ -135,7 +135,7 @@
135 135  * /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 ...)
136 136  * as example: {{code language="none"}}/asap3/flash/gpfs/bl2/2017/data/11003163/raw/hdf/{{/code}}
137 137  
138 -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]].
139 139  
140 140  \\
141 141  
... ... @@ -233,10 +233,6 @@
233 233  
234 234  \\
235 235  
236 -\\
237 -
238 -\\
239 -
240 240  === Load/Save the configuration ===
241 241  
242 242  
... ... @@ -251,14 +251,24 @@
251 251  
252 252  \\
253 253  
254 -\\
230 +=== Choosing the file size ===
255 255  
256 -\\
232 +The DAQ writes into a file (in .raw format) up to a configurable value. If the limit is reached the file will be closed and a new file will be started. Thus a run can contain tens to hundreds of files.
257 257  
258 -=== Assigning the DAQ to the beamline in jddd ===
234 +The size can be configured to be 100 MB, 350 MB or 1000 MB (default)
259 259  
260 -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.
236 +Few things to consider (in case of doubt talk to the expert (Erland ...)):
261 261  
238 +* 1000 MB: This is the standard setting which is best for archiving (few large files are preferred). However mainly for images that are saved with less than 10 Hz the HDF5 converter has problems with the large files. And for low data rates it may take upto half an hour to fill one 1GB file. Then smaller ones are also preferable.
239 +* 350 MB: Often a good compromise ...
240 +* 100 MB: It is not preferred to have many "small" files for storing the data. For very small data rates this is an option to not wait too long till the next file is created.
241 +
242 +To choose the desired filesize one has to choose a run mode configuration in the RunControlGUI
243 +
244 +[[~[~[image:attach:image2020-1-17_13-39-38.png~|~|height="400"~]~]>>attach:image2020-1-17_13-39-38.png]]
245 +
246 +This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again.
247 +
262 262  \\
263 263  
264 264  \\
... ... @@ -267,6 +267,12 @@
267 267  
268 268  \\
269 269  
256 +=== Assigning the DAQ to the beamline in jddd ===
257 +
258 +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.
259 +
260 +\\
261 +
270 270  === Setting the logbook to print in / putting the Whitelist name in jddd ===
271 271  
272 272  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]]
... ... @@ -333,12 +333,12 @@
333 333  ** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
334 334  
335 335  
336 -\\*Here in more detail:*
328 +\\//**Here in more detail:**//
337 337  
338 338  \\
339 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{{/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"**
342 342  ** The DAQ "expert" panel can be reached from the User DAQ control panel.
343 343  [[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_expert.jpg~|~|alt="DAQ_expert.jpg" width="400" height="350"~]~]>>attach:DAQ_expert.jpg]]
344 344  
... ... @@ -372,9 +372,9 @@
372 372  \\
373 373  
374 374  *
375 -** one has to go to the "Run Modes" tab and select the run mode {{code language="none"}}FLASH1_EXP{{/code}} by clicking on it !
376 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/runmode_set.jpg~|~|alt="runmode_set.jpg" width="400" height="400"~]~]>>attach:runmode_set.jpg]]
377 -** 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 +[[image:url:http://confluence.desy.de/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_US&version=2]]
369 +** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
378 378  ** finally you have to select your White list and start a run ...
379 379  
380 380  \\
... ... @@ -385,19 +385,21 @@
385 385  
386 386  \\
387 387  
388 -=== what else ??? ===
389 -
390 390  \\
391 391  
392 -\\
393 -
394 394  ----
395 395  
396 396  [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]]
397 397  
386 +=== Re-read the data base ===
387 +
388 +If there are new Properties included by Vladimir et al one has to reread the data base.
389 +
390 +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.
391 +
398 398  \\
399 399  
400 -=== Re-read the data base ===
394 +OR one can do the hard way:
401 401  
402 402  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:
403 403