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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sndueste
1 +XWiki.sendels
Content
... ... @@ -1,7 +1,26 @@
1 +\\
1 1  
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
2 2  
3 -{{toc/}}
4 -
5 5  \\
6 6  
7 7  == General Concept ==
... ... @@ -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).
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]]
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]].
138 +More details and links can be found in the [[doc:FLASHUSER.User overview]].
119 119  
120 120  \\
121 121  
... ... @@ -213,6 +213,10 @@
213 213  
214 214  \\
215 215  
236 +\\
237 +
238 +\\
239 +
216 216  === Load/Save the configuration ===
217 217  
218 218  
... ... @@ -227,24 +227,14 @@
227 227  
228 228  \\
229 229  
230 -=== Choosing the file size ===
254 +\\
231 231  
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.
256 +\\
233 233  
234 -The size can be configured to be 100 MB, 350 MB or 1000 MB (default)
258 +=== Assigning the DAQ to the beamline in jddd ===
235 235  
236 -Few things to consider (in case of doubt talk to the expert (Erland ...)):
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.
237 237  
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 -
248 248  \\
249 249  
250 250  \\
... ... @@ -253,12 +253,6 @@
253 253  
254 254  \\
255 255  
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 -
262 262  === Setting the logbook to print in / putting the Whitelist name in jddd ===
263 263  
264 264  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]]
... ... @@ -364,9 +364,9 @@
364 364  \\
365 365  
366 366  *
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.
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.
370 370  ** finally you have to select your White list and start a run ...
371 371  
372 372  \\
... ... @@ -377,21 +377,19 @@
377 377  
378 378  \\
379 379  
388 +=== what else ??? ===
389 +
380 380  \\
381 381  
392 +\\
393 +
382 382  ----
383 383  
384 384  [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]]
385 385  
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 -
392 392  \\
393 393  
394 -OR one can do the hard way:
400 +=== Re-read the data base ===
395 395  
396 396  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:
397 397