Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 36.2
edited by sndueste
on 2025-09-08 15:23
Change comment: There is no comment for this version
To version 35.4
edited by sndueste
on 2025-04-23 14:40
Change comment: Renamed back-links.

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,1 @@
1 -FLASHUSER.Offline data analysis (DAQ).WebHome
1 +FS-FLASH USER tmp.Offline data analysis (DAQ).WebHome
Content
... ... @@ -88,11 +88,11 @@
88 88  The (% class="twikiNewLink" %)DAQdataGui(%%) is a powerful tool to visualize the saved data and to do very preliminary analysis. however for more detailed analysis the data has to be read into analysis programs ( matlab, python, Origin ...) here are different options one can use (what option is the best and how to set it up has to be discussed before hand with the FLASH DAQ experts ...)
89 89  
90 90  * The FLASH DAQ system records the data in binary " {{code language="none"}}.raw{{/code}} " files.
91 -** (% class="confluence-link" %)reading the .raw files [[directly via Python>>url:https://ttfinfo.desy.de/DOOCSWiki/Wiki.jsp?page=PythonDAQClientInterface||shape="rect"]], or [[via Matlab >>doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.Offline data analysis (DAQ).For experts\: many ways to get Data from the DAQ.How to Access the DAQ Using Matlab.WebHome]](%%)(no longer recommended) works, yet 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).
91 +** (% class="confluence-link" %)reading the .raw files [[directly via Python>>url:https://ttfinfo.desy.de/DOOCSWiki/Wiki.jsp?page=PythonDAQClientInterface||shape="rect"]], or [[via Matlab >>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).For experts\: many ways to get Data from the DAQ.How to Access the DAQ Using Matlab.WebHome]](%%)(no longer recommended) works, yet 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).
92 92  ** 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 ...
93 93  
94 94  * To ease the data analysis we IN ADDITION provide //ON REQUEST// the data from the FLASH DAQ as HDF5 format
95 -** ONLINE HDF5s: Intro to the [[HDF5 structure used at FLASH>>doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]]. This contains also a list of the most used Parameters saved at FLASH for analysis - including the HDF5 names, DOOCS and DAQ names ...
95 +** ONLINE HDF5s: Intro to the [[HDF5 structure used at FLASH>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]]. This contains also a list of the most used Parameters saved at FLASH for analysis - including the HDF5 names, DOOCS and DAQ names ...
96 96  ** [[Examples>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]] and an [[API>>url:https://gitlab.desy.de/christopher.passow/fdh-builder||shape="rect"]] to make use of the online HDF5s
97 97  **
98 98  
... ... @@ -103,7 +103,7 @@
103 103  * /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 ...)
104 104  * as example: {{code language="none"}}/asap3/flash/gpfs/bl2/2017/data/11003163/raw/hdf/{{/code}}
105 105  
106 -More details and links can be found in the [[doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.WebHome]].
106 +More details and links can be found in the [[doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome]].
107 107  
108 108  
109 109  
... ... @@ -177,12 +177,8 @@
177 177  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 four  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:FLASH.Configuring the user DAQs]].
178 178  
179 179  
180 -=== The DAQmonitor ===
180 +=== Configuring the DAQ monitor ===
181 181  
182 -A general manual for the DAQ monitor can be found here: [[DOOCS DAQ Monitor Server - XWiki>>url:https://xwiki.desy.de/xwiki/bin/view/MCS/MCS%20Applications/FLASH%20%20European%20XFEL%20%20SINBAD-ARES%20%20PITZ%20%20KALDERA/Accelerator%20DAQ%20%28FLASHEuropean%20XFELSINBAD-ARES%29/DOOCS%20DAQ%20Monitor%20Server/]]
183 -
184 -**How to configure the DAQMonitor:**
185 -
186 186  The DAQ monitor ( and the Offline monitor) can be configured using DAQdataGUI.
187 187  Load a test run containing all relevant properties. Select all properties you want to monitor. Use {{code language="none"}}Tools -> Channels to DAQMonitor{{/code}} and choose your DAQ. This sends a list with the selected properties to the DAQ monitor of your system.
188 188  
... ... @@ -295,8 +295,7 @@
295 295  
296 296  
297 297  * 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.
298 -** **Its recommended to run jddd on Linux in the DESY network, meaning wither on our User consoles in the Experimental halls (cons0...12)  or on  {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}}. Log in at one of these machines with your beamline account (e.g. fl12 user or fl24user). **(On the flashlxuser machines there are no desktop icons to start jddd. Here you can use  the  shell command: {{code language="none"}}flash ->{{/code}} Click on "Photons" -> "Photons main panel" )
299 -** Since 2025 the restart also works from Window
294 +** **to be able to restart the DAQ one has to run jddd on Linux in the DESY network, meaning wither on our User consoles in the Experimental halls (cons0...12)  or on  {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}}. Log in at one of these machines with your beamline account (e.g. bl1user or fl24user). **(On the flashlxuser machines there are no desktop icons to start jddd. Here you can use  the  shell command: {{code language="none"}}flash ->{{/code}} Click on "Photons" -> "Photons main panel" )
300 300  ** To Restart the DAQs you need the **"expert" Tab** of the  User DAQ control panel.
301 301  
302 302   [[image:attach:image2022-9-9_10-57-31.png||height="400"]]
... ... @@ -307,7 +307,7 @@
307 307  ==== **all to INITIALIZE** ====
308 308  
309 309  
310 -*
305 +* \\
311 311  ** First, one may try the "**all to INITIALIZE"** button. It starts a script window showing the progress of the initialization. The script sets all subcomponents to initialize. It is helpful if one subcomponent got stuck.
312 312  ** If there is no window coming up or closing right away there may be a problem with the rights. In this case you:
313 313  *** may try to login at the flashlxuser machines and try there again