Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 24.1
edited by sendels
on 2021-02-10 14:45
Change comment: There is no comment for this version
To version 26.1
edited by sndueste
on 2021-06-07 08:45
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
... ... @@ -67,7 +67,7 @@
67 67  
68 68  ==== Offline DAQ monitor ====
69 69  
70 -This tool looks if a predefined selection of parameters is saved in the raw file. When a raw.-file reached its maximum size ( ~~ 1 GB) it is closed and a new file is opened. Once closed, the Offline DAQ monitor reads the file and checks if there are entris for the selected parameters. It shows the fraction of events containing data. For “fast” data (data written with 10 Hz and bunch ID synchronous like images, ADC traces) this should be close to 100%. For “slow” data (saved about every second e.g. pressures , temperatures...) this is about 10-20%. **However it is to note** that this program just check if there is **anything** saved. It does not check if it is the proper data.
70 +This tool looks if a predefined selection of parameters is saved in the raw file. When a raw.-file reached its maximum size ( ~~ 1 GB) it is closed and a new file is opened. Once closed, the Offline DAQ monitor reads the file and checks if there are entries for the selected parameters. It shows the fraction of events containing data. For “fast” data (data written with 10 Hz and bunch ID synchronous like images, ADC traces) this should be close to 100%. For “slow” data (saved about every second e.g. pressures , temperatures...) this is about 10-20%. **However it is to note** that this program just check if there is **anything** saved. It does not check if it is the proper data.
71 71  
72 72  \\
73 73  
... ... @@ -79,9 +79,9 @@
79 79  
80 80  \\
81 81  
82 -The DAQ Data GUI is a general tool to select and visualise data that was saved in the DAQ . It has in addition simple analysis options like histogram, mean, min or max values as function of time etc. Also correlations between different parameters can be analyzed in the tool. More details can be found [[How to Use the FLASH DAQ Data GUI?~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FLASHDAQdataGUI||shape="rect"]] and [[ here (DAQdataGUI link collection) >>doc:FLASH.How to get the data out of the DAQ]]
82 +The DAQ Data GUI is a general tool to select and visualize data that was saved in the DAQ . It has in addition simple analysis options like histogram, mean, min or max values as function of time etc. Also correlations between different parameters can be analyzed in the tool. More details can be found [[How to Use the FLASH DAQ Data GUI?~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://ttfinfo.desy.de/FLASHWiki/Wiki.jsp?page=FLASHDAQdataGUI||shape="rect"]] and [[ here (DAQdataGUI link collection) >>doc:FLASH.How to get the data out of the DAQ]]
83 83  
84 -The tool (separate Java program) can be started [[DAQdataGUI~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://ttfinfo2.desy.de/common/applications/DAQdataGUI-experimental.jnlp||shape="rect"]] or in the DAQ control panel ( lower right) on your local (Desy) PC. In some cases the access via Windows does not work. An option which should always work is to log onto {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}} and start {{code language="none"}}DAQdataGUI{{/code}} from the command line.
84 +The tool (separate Java program) can be started [[DAQdataGUI~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://ttfinfo2.desy.de/common/applications/DAQdataGUI-experimental.jnlp||shape="rect"]] or in the DAQ control panel ( lower right) on your local (Desy) PC. In some cases the access via Windows does not work. An option which should always work is to log onto {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} and start {{code language="none"}}DAQdataGUI{{/code}} from the command line.
85 85  
86 86  
87 87  \\To access the desired data one has to:
... ... @@ -136,9 +136,9 @@
136 136  [[image:attach:RCGUI_2.jpg||height="400"]]
137 137  \\
138 138  
139 -Using the jddd DAQ control panel one can start and stop runs but in order to configure the DAQ which data to save one has to use a a separate *DAQ run control * java application. Since it needs write access to DOOCS internal file systems, which can not be made available elsewhere one has to start the system on our DOOCS control computers [[flashlxuser1.desy.de>>url:http://flashlxuser1.desy.de||shape="rect"]]{{code language="none"}}{{/code}} or [[flashlxuser2.desy.de>>url:http://flashlxuser2.desy.de||shape="rect"]]{{code language="none"}}{{/code}}.
139 +Using the jddd DAQ control panel one can start and stop runs but in order to configure the DAQ which data to save one has to use a a separate *DAQ run control * java application. Since it needs write access to DOOCS internal file systems, which can not be made available elsewhere one has to start the system on our DOOCS control computers {{code language="none"}}flashlxuser1.desy.de, flashlxuser2.desy.de {{/code}} or {{code language="none"}}flashlxuser3.desy.de{{/code}}.
140 140  Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via X-Win32 from windows or via ssh from Linux machines.
141 -Once logged in to {{code language="none"}}flashlxuser1{{/code}} or {{code language="none"}}flashlxuser2{{/code}} the DAQ run control can be started. Depending on the DAQ you want to use the commands are:
141 +Once logged in to {{code language="none"}}flashlxuser1,2,3{{/code}} the DAQ run control can be started. Depending on the DAQ you want to use the commands are:
142 142  
143 143  \\
144 144  
... ... @@ -183,7 +183,7 @@
183 183  
184 184  \\
185 185  
186 -Using the {{code language="none"}}Add{{/code}} and {{code language="none"}}Rem(ove){{/code}} buttons one can move the desired "subsystems" in the included side - meaning that they are saved. The "subsystems" contain typically several DOOCS parameters. E.g. {{code language="none"}}EXPERIMENT_MHZ_ADC_BL1{{/code}} contains all relevant DOOCS properties of the 4 MHZ ADC channels available at BL1. To get a detailled information about the saved parameters one can have a look to the "Show Properties in Subsystems" button . In addition, a list of all possible subsystems and their description can be found [[here>>doc:FLASHUSER.Configuring the user DAQs]].
186 +Using the {{code language="none"}}Add{{/code}} and {{code language="none"}}Rem(ove){{/code}} buttons one can move the desired "subsystems" in the included side - meaning that they are saved. The "subsystems" contain typically several DOOCS parameters. E.g. {{code language="none"}}EXPERIMENT_MHZ_ADC_BL1{{/code}} contains all relevant DOOCS properties of the 4 MHZ ADC channels available at BL1. To get a detailed information about the saved parameters one can have a look to the "Show Properties in Subsystems" button . In addition, a list of all possible subsystems and their description can be found [[here>>doc:FLASHUSER.Configuring the user DAQs]].
187 187  
188 188  \\
189 189  
... ... @@ -235,7 +235,7 @@
235 235  * 350 MB: Often a good compromise ...
236 236  * 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.
237 237  
238 -To choose the desired filesize one has to choose a run mode configuration in the RunControlGUI
238 +To choose the desired file size one has to choose a run mode configuration in the RunControlGUI
239 239  
240 240  [[~[~[image:attach:image2020-1-17_13-39-38.png~|~|height="400"~]~]>>attach:image2020-1-17_13-39-38.png]]
241 241  
... ... @@ -273,7 +273,7 @@
273 273  
274 274  === No //START// or //STOP// buttons are visible in the DAQ control panel ===
275 275  
276 -~* The jddd GUI only shows the Start and stop bunnon if the DAQ is in the "Idle" state. sometimes the DAQ "just" gets stuck in the stopping phase. Then stopping again or starting form the not "Idle" state can help. For this goto the "Advanced" tab of the jddd DAQ control . there the START and STOP buttons are always available ... independent of the state of the DAQ. If this does not help you may have to restart the DAQ ...
276 +~* The jddd GUI only shows the Start and stop button if the DAQ is in the "Idle" state. sometimes the DAQ "just" gets stuck in the stopping phase. Then stopping again or starting form the not "Idle" state can help. For this goto the "Advanced" tab of the jddd DAQ control . there the START and STOP buttons are always available ... independent of the state of the DAQ. If this does not help you may have to restart the DAQ ...
277 277  
278 278  \\
279 279  
... ... @@ -315,7 +315,7 @@
315 315  \\
316 316  
317 317  * Generally there 3 ways to "restart" the DAQ
318 -** 1. The least interferring way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
318 +** 1. The least interfering way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
319 319  ** 2. The "re-start DAQ" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
320 320  ** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
321 321  
... ... @@ -325,7 +325,7 @@
325 325  \\
326 326  
327 327  * 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.
328 -** **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"**
328 +** **to be able to restart the DAQ one has to run jddd on the {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} (up to now ( 2021) the restat on our consoles (cons0...12) is NOT reliably possible ) : 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"**
329 329  ** The DAQ "expert" panel can be reached from the User DAQ control panel.
330 330  
331 331   [[image:attach:DAQ_expert.jpg||height="400"]]
... ... @@ -388,7 +388,7 @@
388 388  
389 389  OR one can do the hard way:
390 390  
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:
391 +On flashlxuser1,2 or 3 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  
393 393  {{code language="none"}}Options -> "Show Expert Menu"{{/code}}
394 394  
... ... @@ -416,7 +416,7 @@
416 416  
417 417  \\
418 418  
419 -[[image:url:https://mail.desy.de/service/home/~~/?auth=co&loc=de&id=154203&part=2.2||width="788" height="140"]]
419 +[[image:attach:2021-02-10 15_23_20-How to save data in the User DAQ - FS-FLASH USER - DESY Confluence.png||width="600"]]
420 420  
421 421  upper flag:  There was a problem to read run catalogue
422 422