Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 14.1
edited by sndueste
on 2019-11-13 13:45
Change comment: There is no comment for this version
To version 10.1
edited by sndueste
on 2019-09-18 16:47
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -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.Data Acquisition and controls.DAQ and controls overview.WebHome]].
119 +More details and links can be found in the [[doc:FLASHUSER.User overview]].
120 120  
121 121  \\
122 122  
... ... @@ -214,6 +214,10 @@
214 214  
215 215  \\
216 216  
217 +\\
218 +
219 +\\
220 +
217 217  === Load/Save the configuration ===
218 218  
219 219  
... ... @@ -228,26 +228,14 @@
228 228  
229 229  \\
230 230  
231 -=== Choosing the file size ===
235 +\\
232 232  
233 -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.
237 +\\
234 234  
235 -The size can be configured to be 100 MB, 350 MB or 1000 MB (default)
239 +=== Assigning the DAQ to the beamline in jddd ===
236 236  
237 -Few things to consider (in case of doubt talk to the expert (Erland ...)):
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.
238 238  
239 -* 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.
240 -* 350 MB: Often a good compromise ...
241 -* 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.
242 -
243 -To choose the desired filesize one has to choose a run mode configuration in the RunControlGUI
244 -
245 -[[image:attach:image2019-10-24_15-29-36.png||height="400"]]
246 -
247 -This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again:
248 -
249 -[[image:attach:image2019-10-24_15-32-5.png||thumbnail="true" height="250"]]
250 -
251 251  \\
252 252  
253 253  \\
... ... @@ -254,10 +254,6 @@
254 254  
255 255  \\
256 256  
257 -=== Assigning the DAQ to the beamline in jddd ===
258 -
259 -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.
260 -
261 261  \\
262 262  
263 263  === Setting the logbook to print in / putting the Whitelist name in jddd ===
... ... @@ -365,9 +365,9 @@
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 and choose the desired file size (stored settings)
369 -[[image:attach:image2019-10-24_15-29-36.png||height="400"]]
370 -** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
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.
371 371  ** finally you have to select your White list and start a run ...
372 372  
373 373  \\
... ... @@ -384,15 +384,9 @@
384 384  
385 385  [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]]
386 386  
387 -=== Re-read the data base ===
388 -
389 -If there are new Properties included by Vladimir et al one has to reread the data base.
390 -
391 -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.
392 -
393 393  \\
394 394  
395 -OR one can do the hard way:
377 +=== Re-read the data base ===
396 396  
397 397  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:
398 398