Changes for page How to save data in the User DAQ

Last modified by sndueste on 2025-09-08 15:36

From 21.1 to 22.1 From 27.1 to 28.1

From version 22.1

edited by cpassow
on 2021-02-10 12:43

Change comment: There is no comment for this version

To version 27.1

edited by erlandm
on 2021-06-17 15:46

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.cpassow
++XWiki.erlandm

Content

@@ -20,11 +20,12 @@
  === DAQ control panel ===
--To get to the User DAQ control one has to go to {{code language="none"}}Experiment control{{/code}} -> {{code language="none"}}User DAQ tab{{/code}} -> {{code language="none"}}FLxUSERy DAQ CTRL{{/code}}
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/jddd_DAQ-control-manual-how_to_get.png~|~|alt="jddd_DAQ-control-manual-how_to_get.png" width="500" height="360"~]~]>>attach:jddd_DAQ-control-manual-how_to_get.png]]
++To get to the User DAQ control one has to go to {{code language="none"}}Experiment control{{/code}} -> {{code language="none"}}User DAQ tab{{/code}} -> {{code language="none"}}FLxUSERy DAQ CTRL{{/code}}
++
++[[image:attach:jddd_DAQ-control-manual-how_to_get.png||height="400"]]
  \\The following window opens. Here the User DAQ can be started and stopped as well as the incoming data can be visualized, information about data rates and saved properties is presented as well as the panel is automatically printed in to the logbook:
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/jddd_DAQ-control-manual2.png~|~|alt="jddd_DAQ-control-manual2.png" width="960" height="720"~]~]>>attach:jddd_DAQ-control-manual2.png]]
++[[image:attach:jddd_DAQ-control-manual2.png||height="400"]]
  \\\\
  \\
@@ -66,7 +66,7 @@
  ==== Offline DAQ monitor ====
--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.
++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.
  \\
@@ -74,12 +74,13 @@
  To ultimately check if the correct data is saved one can use the DAQ data GUI to look at the saved raw. files.
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQgui1.jpg~|~|alt="DAQgui1.jpg" width="500" height="350"~]~]>>attach:DAQgui1.jpg]][[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQgui2.jpg~|~|alt="DAQgui2.jpg" width="500" height="350"~]~]>>attach:DAQgui2.jpg]][[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/daqgui3.png~|~|alt="daqgui3.png" width="500" height="350"~]~]>>attach:daqgui3.png]]
++[[image:attach:daqgui3.png||height="250"]][[image:attach:DAQgui2.jpg||height="250"]][[image:attach:DAQgui1.jpg||height="250"]]
++
  \\
--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]]
++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]]
--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.
++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.
  \\To access the desired data one has to:
@@ -97,16 +97,15 @@
  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 ...)
  * The FLASH DAQ system records the data in binary " {{code language="none"}}.raw{{/code}} " files.
--** [[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).
++** (% 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.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]](%%)(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).
  ** 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 ...
  \\
  * To ease the data analysis we IN ADDITION provide //ON REQUEST// the data from the FLASH DAQ as HDF5 format
--** ONLINE HDF5s: To make efficient use of the HDF5 files for analysis during the beamtime and afterwards we provide a [[very useful tool (Beamtime Daq Access)>>doc:FLASHUSER.Near-Online data analysis]]. Using this tool (working for Python and Matlab) one can get the data of parameters per run or for specific bunch ID intervals etc. without having to care from which subset of HDF5 files the data is read ...
--** Summary HDF5 files include complete runs. They will be put after the beamtime on the gpfs storage and are available from computers within DESY (for registered Beamtime participants) and also access
--** Intro to the [[HDF5 structure used at FLASH>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).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 ...
--** [[Short examples>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]] and [[user provided examples>>doc:FLASH.Collection of user codes]] on how to read HDF5 in Matlab
++** ONLINE HDF5s: Intro to the [[HDF5 structure used at FLASH>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).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 ...
++** [[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
++** [[Short examples>>doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).The FLASH HDF5 structure.WebHome]] and [[user provided examples>>doc:FLASH.OUTDATED - Collection of user codes]] on how to read HDF5 in Matlab (no longer recommended).
  The HDF5 files (online and summary) are saved in the [["gpfs" system ~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://confluence.desy.de/display/ASAP3/Architecture||shape="rect"]]. it can be accessed from [[Windows and Linux computers at DESY~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://confluence.desy.de/display/ASAP3/Mounting+the+storage+system+at+the+beamline||shape="rect"]] by the persons ( logins) which are registered for the beamtime in DOOR ( functional accounts
@@ -131,12 +131,12 @@
  === Configuring the DAQ ===
++[[image:attach:RCGUI_2.jpg||height="400"]]
++\\
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RCGUI_2.jpg~|~|alt="RCGUI_2.jpg" width="400" height="500"~]~]>>attach:RCGUI_2.jpg]]
--
--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}}.
++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}}.
  Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via X-Win32 from windows or via ssh from Linux machines.
--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:
++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:
  \\
@@ -177,13 +177,11 @@
  Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.
--\\
++[[image:attach:RCGUI_properties.jpg||height="400"]]
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RCGUI_properties.jpg~|~|alt="RCGUI_properties.jpg" width="503" height="311"~]~]>>attach:RCGUI_properties.jpg]]
--
  \\
--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]].
++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]].
  \\
@@ -193,12 +193,7 @@
  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.
  [[image:attach:daq_monitor_config.png||height="400"]]
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/daq_monitor_config.png~|~|alt="daq_monitor_config.png" width="700" height="390"~]~]>>attach:daq_monitor_config.png]]
--\\
--
--\\
--
  === Start and Stop a run ===
  In order to "activate" and test your configuration you have to start a run with the new configuration. **NOTE: Whenever the configuration was changed with the RCGUI the new run HAS to be started with the RCGUI **(starting with the jddd DAQ panel would only start the last configuration that has been running before !!!
@@ -217,9 +217,8 @@
  === Load/Save the configuration ===
++[[image:attach:whitelist.jpg||height="400"]]
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/whitelist.jpg~|~|alt="whitelist.jpg" width="532" height="370"~]~]>>attach:whitelist.jpg]]
--
  Once a list of subsystems is defined and tested this parameter combination should then be saved in a so-called //white list//. By loading this white list one can then easily configure the DAQ after changes / restarts ... to the initially defined settings to save the correct data.
  The whitelist can be saved/loaded with the Run Control GUI by: {{code language="none"}}File -> Group White List -> Save/Load{{/code}}. Note, while the top left rectangle's background of time and date is yellow, don't try any further controls of the GUI, you might confuse the program. It is busy reading the configuration from the run control database. The background changes back to grey when it has finished.
  \\The filename convention for the White Lists are arranged in the way:
@@ -241,7 +241,7 @@
  * 350 MB: Often a good compromise ...
  * 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.
--To choose the desired filesize one has to choose a run mode configuration in the RunControlGUI
++To choose the desired file size one has to choose a run mode configuration in the RunControlGUI
  [[~[~[image:attach:image2020-1-17_13-39-38.png~|~|height="400"~]~]>>attach:image2020-1-17_13-39-38.png]]
@@ -266,16 +266,13 @@
  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]]
  Define logbook / and whitelist for display in the jddd DAQ control (jddd otherwise does not "know" which White list was used ... this has to be put in by hand ...up to now)
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/setting_parameters.jpg~|~|alt="setting_parameters.jpg" width="500" height="300"~]~]>>attach:setting_parameters.jpg]]
--\\
++[[image:attach:setting_parameters.jpg||height="400"]]
  \\
  \\
--\\
--
  == In case something goes wrong: Troubleshooting ==
  \\
@@ -282,7 +282,7 @@
  === No //START// or //STOP// buttons are visible in the DAQ control panel ===
--~* 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 ...
++~* 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 ...
  \\
@@ -298,9 +298,11 @@
  === Data seems not properly saved ===
++[[image:attach:RC_logfile.jpg||height="250"]]
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RC_logfile.jpg~|~|alt="RC_logfile.jpg" width="518" height="300"~]~]>>attach:RC_logfile.jpg]]When checking the saved run with the (% class="twikiNewLink" %)DAQdataGUI(%%) it may happen that the property shows up in the data tree but no events are saved. Then (most likely) something is wrong with the sending of the data.
++ When checking the saved run with the (% class="twikiNewLink" %)DAQdataGUI(%%) it may happen that the property shows up in the data tree but no events are saved. Then (most likely) something is wrong with the sending of the data.
++
  * A very helpful tool is the {{code language="none"}}RC logfile{{/code}}. in the RCGUI on the lower right side there is a button to start an editor with the log file. besides lots of standard entries there is usually also a hint on where to find the problem ...
  * check if the device is working properly. Is it connected? Can you see data in jddd / DOOCS ? . If not you have to fix the DOOCS part ... DAQ can only save what is properly implemented in DOOCS.
  * If camera images are not properly saved ( e.g. only "0"s in the image matrix or the DAQ sender can not be switched to "on") a **restart of the camera server** usually helps.
@@ -322,7 +322,7 @@
  \\
  * Generally there 3 ways to "restart" the DAQ
--** 1. The least interferring way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
++** 1. The least interfering way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
  ** 2. The "re-start DAQ" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
  ** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
@@ -332,26 +332,25 @@
  \\
  * 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.
--** **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"**
++** **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"**
  ** The DAQ "expert" panel can be reached from the User DAQ control panel.
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_expert.jpg~|~|alt="DAQ_expert.jpg" width="400" height="350"~]~]>>attach:DAQ_expert.jpg]]
++               [[image:attach:DAQ_expert.jpg||height="400"]]
  \\
--\\
--
  *
  ** Then you see the following "DAQ expert panel":
  ** first one may try the "all to INITIALIZE" button. it starts a script window and asks for the passwd (the beamline accounts (blxuser) should have the according rights. vuvfuser has it for sure. The script sets all subcomponents to initialize. It is helpful if one subcomponent got stuck.
++               [[image:attach:UserDAQ_status.jpg||height="400"]]
++\\
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/UserDAQ_status.jpg~|~|alt="UserDAQ_status.jpg" width="500" height="400"~]~]>>attach:UserDAQ_status.jpg]]
--
  \\
  * If this does not help you have to "re-start DAQ". This completely restarts all processes and takes a while. A script window appears and shows what steps are actually done. At the end is sais: "Cleanup finished".
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_restart_msg.jpg~|~|alt="DAQ_restart_msg.jpg" width="400" height="350"~]~]>>attach:DAQ_restart_msg.jpg]]
++     [[image:attach:DAQ_restart_msg.jpg||height="400"]]
++
  \\
  * For the "re-start DAQ" the DAQ should come up in the same state as before. Meaning that the subsystems (ADCs, cameras ..) are still loaded and displayed. If this is not the case you can try to load your white list and start a new run. If the data is saved correctly you are done.
@@ -361,10 +361,12 @@
  * **IF the DAQ still does not work properly** the final option is the: "re-start DAQ (no RCSHM)". This button does the same as the "re-start DAQ" but the Run Controller shared memory is **not** re-stored. It means that after the DAQ is back no run configuration is selected.
  ** in the jddd control the list of subsystems sais "empty"
  ** in the RCGUI in the lower part it sais "RUN mode is not set"
--[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/restart_RCM_no_runmode.jpg~|~|alt="restart_RCM_no_runmode.jpg" width="400" height="400"~]~]>>attach:restart_RCM_no_runmode.jpg]]
++               [[image:attach:restart_RCM_no_runmode.jpg||height="400"]]
  \\
++\\
++
  *
  ** 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)
  ** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . initially all subsystems are included.
@@ -394,7 +394,7 @@
  OR one can do the hard way:
--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:
++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:
  {{code language="none"}}Options -> "Show Expert Menu"{{/code}}
@@ -420,8 +420,10 @@
  The red flags next to the  different stream indicators tell something about data base errors
--[[image:url:https://mail.desy.de/service/home/~~/?auth=co&loc=de&id=154203&part=2.2||width="788" height="140"]]
++\\
++[[image:attach:2021-02-10 15_23_20-How to save data in the User DAQ - FS-FLASH USER - DESY Confluence.png||width="600"]]
++
  upper flag:  There was a problem to read run catalogue
  lower flag: There was a problem to read dccp catalogue.

Changes for page How to save data in the User DAQ

Summary

Details

Applications

Navigation