Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 9.1
edited by sndueste
on 2019-09-18 16:46
Change comment: There is no comment for this version
To version 16.1
edited by sndueste
on 2020-01-17 13:41
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  
... ... @@ -214,10 +214,6 @@
214 214  
215 215  \\
216 216  
217 -\\
218 -
219 -\\
220 -
221 221  === Load/Save the configuration ===
222 222  
223 223  
... ... @@ -232,14 +232,24 @@
232 232  
233 233  \\
234 234  
235 -\\
230 +=== Choosing the file size ===
236 236  
237 -\\
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.
238 238  
239 -=== Assigning the DAQ to the beamline in jddd ===
234 +The size can be configured to be 100 MB, 350 MB or 1000 MB (default)
240 240  
241 -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 ...)):
242 242  
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 +
243 243  \\
244 244  
245 245  \\
... ... @@ -248,6 +248,12 @@
248 248  
249 249  \\
250 250  
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 +
251 251  === Setting the logbook to print in / putting the Whitelist name in jddd ===
252 252  
253 253  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]]
... ... @@ -353,9 +353,9 @@
353 353  \\
354 354  
355 355  *
356 -** one has to go to the "Run Modes" tab and select the run mode {{code language="none"}}FLASH1_EXP{{/code}} by clicking on it !
357 -[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/runmode_set.jpg~|~|alt="runmode_set.jpg" width="400" height="400"~]~]>>attach:runmode_set.jpg]]
358 -** 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.
359 359  ** finally you have to select your White list and start a run ...
360 360  
361 361  \\
... ... @@ -366,19 +366,21 @@
366 366  
367 367  \\
368 368  
369 -=== what else ??? ===
370 -
371 371  \\
372 372  
373 -\\
374 -
375 375  ----
376 376  
377 377  [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]]
378 378  
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 +
379 379  \\
380 380  
381 -=== Re-read the data base ===
394 +OR one can do the hard way:
382 382  
383 383  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:
384 384