Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 7.1
edited by sendels
on 2019-05-15 13:07
Change comment: There is no comment for this version
To version 33.1
edited by sndueste
on 2024-03-14 15:13
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.sendels
1 +XWiki.sndueste
Tags
... ... @@ -1,0 +1,1 @@
1 +favourite
Content
... ... @@ -1,58 +1,36 @@
1 -\\
1 +{{toc/}}
2 2  
3 -* General Concept
4 -* Taking User data: Starting and stopping runs (Users)
5 -** DAQ control panel
6 -** Checklist for proper saving of the data
7 -** More infos on the tools to check the proper saving of the data
8 -** How to get the data out for analysis (short summary)
9 -* Setting up the DAQ - DAQ Run Control GUI (local contacts, FLASH stuff)
10 -** Configuring the DAQ
11 -** Configuring the DAQ monitor
12 -** Start and Stop a run
13 -** Load/Save the configuration
14 -** Assigning the DAQ to the beamline in jddd
15 -** Setting the logbook to print in / putting the Whitelist name in jddd
16 -* In case something goes wrong: Troubleshooting
17 -** No START or STOP buttons are visible in the DAQ control panel
18 -** The DAQ does not start a run
19 -** Data seems not properly saved
20 -** Restarting the DAQ
21 -** what else ???
22 -** Re-read the data base
23 23  
24 -\\
25 -
26 26  == General Concept ==
27 27  
28 -A large number of parameters which are essential for ALL Experiments is continuously saved (pulse energy, arrival time, Beamline settings ...) in the [[ PHOTONDIAGNOSTIC FLASH DAQ>>doc:FLASHUSER.FLASH1 PhotDiag stream]] system.
29 -Other [[experiment related information>>doc:FLASHUSER.Configuring the user DAQs]] is ONLY saved by the users ON DEMAND in the FLASH DAQ system. To record this type of data we have 3 User DAQs at FLASH1 (FLASH1_USER1,FLASH1_USER2 and FLASH1_USER3) and one at FLASH 2 (FLASH2_USER1)
6 +
7 +All Data which is important for the experiment is saved by the users **ON DEMAND **in the FLASH DAQ system. To record this type of data we have 3 User DAQs at FLASH1 (FLASH1_USER1,FLASH1_USER2 and FLASH1_USER3) and two at FLASH 2 (FLASH2_USER1, FLASH2_USER2)
30 30  How to save this experiment related "User-Data" will be explained briefly in this page:
31 31  
32 -\\
10 +In addition, a large number of parameters is continuously saved (pulse energy, arrival time, Beamline settings ...) in the PHOTONDIAGNOSTIC FLASH DAQ system as backup.
33 33  
12 +
34 34  == Taking User data: Starting and stopping runs (Users) ==
35 35  
36 36  In order to save the experiment related data from ADCs, Images, delayline detectors etc. the User DAQ has to be started to record the experiment data. The options which data can be saved, have to be discussed way before the beamtime. For regular beamtime operation the DAQ also was setup by experts before the beamtime. If things do not look like described here look in the troubleshooting section below.
37 37  
38 -\\
39 39  
40 40  === DAQ control panel ===
41 41  
42 -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}}
43 -[[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"]]
20 +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}}
21 +
22 +[[image:attach:jddd_DAQ-control-manual-how_to_get.png||width="500"]][[image:attach:image2022-9-8_10-50-53.png||width="450"]]
44 44  \\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:
45 45  
46 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/jddd_DAQ-control-manual2.png||alt="jddd_DAQ-control-manual2.png" width="960" height="720"]]
47 -\\\\
25 +[[image:attach:jddd_DAQ-control-manual2.png||width="800"]]
26 +\\
48 48  
49 -\\
50 50  
51 -* By pressing the start and stop button, besides sending the commands to the DAQ the button prints the panel to the respective beamline / experiments logbook. Here you can later on keep track of the runs. Links to the Beamline logbooks can be found [[here>>doc:FLASHUSER.Electronic Logbooks]] (DESY internal link)
52 -* After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
53 -* Each run has a unique run number. This number is needed to retrieve the data later on. So it is important to keep track which number is associated to what experimental parameters. Note that the run numbers are used by all FLASH DAQs (currently about 10). It might thus well be, that two consecutive runs from you do have run numbers which are spaced by more than one if another DAQ has been started in-between ...
29 +* By pressing the start and stop button, besides sending the commands to the DAQ the button prints the panel to the respective beamline / experiments logbook. Here you can later on keep track of the runs. Links to the Beamline logbooks can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.E-Logbooks.WebHome]].
30 +* here a sample entry in the **logbook**. The run number, "run comment" and several other parameters are printed as (searchable) text in addition with the screenshot of the DAQ control to get all relevant data for this run in the logbook: [[image:attach:image2022-9-8_10-57-56.png||thumbnail="true" height="250"]]
31 +* NOTE: After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
32 +* NOTE: Each run has a unique run number. This number is needed to retrieve the data later on. So it is important to keep track which number is associated to what experimental parameters. Note that the run numbers are used by all FLASH DAQs (currently about 10). It might thus well be, that two consecutive runs from you do have run numbers which are spaced by more than one if another DAQ has been started in-between ...
54 54  
55 -\\
56 56  
57 57  === Checklist for proper saving of the data ===
58 58  
... ... @@ -71,38 +71,35 @@
71 71  
72 72  If not all points of the list are o.k. there may be some problem with the writing of the data. Look to the troubleshooting section and / or talk to beamline stuff.
73 73  
74 -\\
75 75  
76 76  === More infos on the tools to check the proper saving of the data ===
77 77  
78 -\\
79 79  
80 80  ==== DAQ monitor ====
81 81  
82 82  The DAQ monitor shows a predefined selection of parameters as they are received in the DAQ //before// writing to a file. Here one can check if the desired data //arrives// in the DAQ and if the ranges are set correctly (e.g. sufficient acquisition time). The parameters to look at are defined before the beamtime with the local contact / DAQ group (details see below)
83 83  
84 -\\
85 85  
86 86  ==== Offline DAQ monitor ====
87 87  
88 -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.
63 +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.
89 89  
90 -\\
91 91  
92 92  ==== DAQ Data GUI ====
93 93  
94 94  To ultimately check if the correct data is saved one can use the DAQ data GUI to look at the saved raw. files.
95 95  
96 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQgui1.jpg||alt="DAQgui1.jpg" width="500" height="350"]][[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQgui2.jpg||alt="DAQgui2.jpg" width="500" height="350"]][[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/daqgui3.png||alt="daqgui3.png" width="500" height="350"]]
97 -\\
70 +[[image:attach:daqgui3.png||height="250"]][[image:attach:DAQgui2.jpg||height="250"]][[image:attach:DAQgui1.jpg||height="250"]]
98 98  
99 -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:FLASHUSER.How to get the data out of the DAQ]]
100 100  
101 -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.
73 +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~|~|height="12" width="13"~]~]>>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]]
102 102  
75 +The tool (separate Java program) can be started [[DAQdataGUI~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>url:http://ttfinfo2.desy.de/common/applications/DAQdataGUI-experimental.jnlp||shape="rect"]] or in the DAQ control panel ( lower right) on your local user console (Linux or Windows) or log  onto the COntrol machines: {{code language="none"}}flashlxuser1,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} (there you also may start via  {{code language="none"}}DAQdataGUI{{/code}} from the command line).
103 103  
104 -\\To access the desired data one has to:
105 105  
78 +
79 +To access the desired data one has to:
80 +
106 106  * enter the {{code language="none"}}run number{{/code}} of the run you want to look at at //Run//
107 107  * select your DAQ in the //Experiment// drop down menu: {{code language="none"}}FLASHy_USERx{{/code}}
108 108  * press {{code language="none"}}get Channels/Files{{/code}}
... ... @@ -109,7 +109,6 @@
109 109  * browse through the data tree and select your important parameters and drag them with the mouse in the {{code language="none"}}selected{{/code}} window. The list of important parameters should have been defined before the experiment with the FLASH stuff together. This list can also be found in the offline monitor (lower part of DAQ control) )
110 110  * press {{code language="none"}}Start Display{{/code}} to open a new window with your data. In case it was a long run and / or a large amount of data per shot one can limit the number of shown events to a fraction: {{code language="none"}}Events -> Reading Options -> Event Interval{{/code}} provides the option to show only every //n// th dataset.
111 111  
112 -\\
113 113  
114 114  === How to get the data out for analysis (short summary) ===
115 115  
... ... @@ -116,19 +116,16 @@
116 116  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 ...)
117 117  
118 118  * The FLASH DAQ system records the data in binary " {{code language="none"}}.raw{{/code}} " files.
119 -** [[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).
120 -** Examples how to read from {{code language="none"}}.raw{{/code}} files can also be found in [[the user code collection>>doc:FLASHUSER.Collection of user codes]]
93 +** (% 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).
121 121  ** 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 ...
122 122  
123 -\\
124 124  
125 125  * To ease the data analysis we IN ADDITION provide //ON REQUEST// the data from the FLASH DAQ as HDF5 format
126 -** 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 ...
127 -** 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
128 -** Intro to the [[HDF5 structure used at FLASH>>url:http://hasfweb.desy.de/bin/view/Setup/HDF5main||shape="rect" class="twikiLink"]]. This contains also a list of the most used Parameters saved at FLASH for analysis - including the HDF5 names, DOOCS and DAQ names ...
129 -** [[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:FLASHUSER.Collection of user codes]] on how to read HDF5 in Matlab
98 +** 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 ...
99 +** [[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
100 +** [[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).
130 130  
131 -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
102 +The HDF5 files (online and summary) are saved in the [["gpfs" system ~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>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~|~|height="12" width="13"~]~]>>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
132 132  
133 133  The path to your data is structured the following way:
134 134  
... ... @@ -135,31 +135,30 @@
135 135  * /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 ...)
136 136  * as example: {{code language="none"}}/asap3/flash/gpfs/bl2/2017/data/11003163/raw/hdf/{{/code}}
137 137  
138 -More details and links can be found in the [[doc:FLASHUSER.User overview]].
109 +More details and links can be found in the [[doc:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.WebHome]].
139 139  
140 -\\
141 141  
142 -\\
143 143  
144 -\\
145 145  
146 146  == Setting up the DAQ - DAQ Run Control GUI (local contacts, FLASH stuff) ==
147 147  
148 148  This section is intended for the local contacts / FLASH staff to set up the DAQ according to the needs of users before the beamtime. For troubleshooting this may also be helpful for users ...
149 149  
150 -\\
151 151  
152 152  === Configuring the DAQ ===
153 153  
121 +[[image:attach:RCGUI_2.jpg||height="400"]]
122 +
154 154  
155 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RCGUI_2.jpg||alt="RCGUI_2.jpg" width="400" height="500"]]
156 156  
157 -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}}.
158 -Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via X-Win32 from windows or via ssh from Linux machines.
159 -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:
125 +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 linux user consoles at the beamline or on the  DOOCS control computers {{code language="none"}}flashlxuser1.desy.de, flashlxuser2.desy.de {{/code}} or {{code language="none"}}flashlxuser3.desy.de{{/code}}.
126 +Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via fastX3 or {{code language="none"}}Remote desktop{{/code}} from windows or via ssh from Linux machines.
127 +Once logged in to {{code language="none"}}flashlxuser1,2,3{{/code}} the DAQ run control can be started in the "advanced"  Tab of the DAQ control :
160 160  
161 -\\
129 +[[image:attach:image2022-9-8_11-14-7.png||border="true" height="250" width="343"]]
162 162  
131 +Or in the command line:
132 +
163 163  (% class="wrapped" %)
164 164  |(((
165 165  Unix command
... ... @@ -194,119 +194,117 @@
194 194  )))|(((
195 195  FLASH2_USER1 DAQ
196 196  )))
167 +|(% colspan="1" %)(((
168 +{{code language="none"}}
169 +RCGUIFL2USER2
170 +{{/code}}
171 +)))|(% colspan="1" %)(((
172 +FLASH2_USER2 DAQ
173 +)))
197 197  
175 +
198 198  Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.
199 199  
200 -\\
178 +[[image:attach:RCGUI_properties.jpg||height="400"]]
201 201  
202 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RCGUI_properties.jpg||alt="RCGUI_properties.jpg" width="503" height="311"]]
203 203  
204 -\\
181 +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]].
205 205  
206 -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]].
207 207  
208 -\\
209 -
210 210  === Configuring the DAQ monitor ===
211 211  
212 -The DAQ monitor ( and the Offline monitor) can be confgured using DAQdataGUI.
213 -Load a test run containing all relavant propoerties. 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.
214 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/daq_monitor_config.png||alt="daq_monitor_config.png" width="700" height="390"]]
186 +The DAQ monitor ( and the Offline monitor) can be configured using DAQdataGUI.
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.
215 215  
216 -\\
189 +[[image:attach:daq_monitor_config.png||height="400"]]
217 217  
218 -\\
219 -
220 220  === Start and Stop a run ===
221 221  
222 -In order to "activate" and test your configuration you have to start a run with the new configuration. **NOTE: Whenever the configuratio 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 !!!
193 +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 !!!
223 223  
224 -\\
225 225  
226 -To START a run - meaning starting to save the experiment related data - one has to press the "start" button in the Run Control GUI. This opens a confirmation window asking if you really want to start the run ("in default mode"). Press yes. Now it takes about 20 seconds for the system to start up and start recording data. Indication is the "Run Control: RUN" and "DAQ: RUN" greenish indicators on the upper left side of the run control.
196 +**To START** a run - meaning starting to save the experiment related data - one has to press the "start" button in the Run Control GUI. This opens a confirmation window asking if you really want to start the run ("in default mode"). Press yes. Now it takes about 20 seconds for the system to start up and start recording data. Indication is the "Run Control: RUN" and "DAQ: RUN" greenish indicators on the upper left side of the run control.
227 227  
228 -To STOP a run one has to press the "stop" button. This opens a window for comments. This contains already the actual Experiment name by default. Please leave this information in. Add a comment for your run. This comment will be printed into the logbook and can later on be used to identify individual runs ... note you are required to type in something otherwise the run will not stop.
198 +**To STOP** a run one has to press the "stop" button. This opens a window for comments. This contains already the actual Experiment name by default. Please leave this information in. Add a comment for your run. This comment will be printed into the logbook and can later on be used to identify individual runs ... note you are required to type in something otherwise the run will not stop.
229 229  
230 230  The stopping also needs about 20 seconds.*_IT IS IMPORTANT_ not to start and stop the DAQ while it is still ramping up or down. So please wait before restarting the DAQ.*
231 231  
232 232  After the run use the DAQ data GUI to check if the data intended is saved properly.
233 233  
234 -\\
235 235  
236 -\\
237 -
238 -\\
239 -
240 240  === Load/Save the configuration ===
241 241  
207 +[[image:attach:whitelist.jpg||height="250"]]
242 242  
243 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/whitelist.jpg||alt="whitelist.jpg" width="532" height="370"]]
244 -
245 -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.
246 -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.
247 -\\The filename convention for the White Lists are arranged in the way:
209 +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.
210 +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.
211 +\\The filename convention for the White Lists are arranged in the way:
248 248  //DAQ name// - //Date of creation// - //name of the PI / Experiment// - //optional comment on the type of data//
249 249  
250 250  The whitelists are stored in separate folders for each beamline.
251 251  
252 -\\
253 253  
254 -\\
217 +=== Choosing the file size ===
255 255  
256 -\\
219 +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.
257 257  
258 -=== Assigning the DAQ to the beamline in jddd ===
221 +The size can be configured to be 100 MB, 350 MB or 1000 MB (default)
259 259  
260 -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.
223 +Few things to consider (in case of doubt talk to the expert (Erland ...)):
261 261  
262 -\\
225 +* 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.
226 +* 350 MB: Often a good compromise ...
227 +* 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.
263 263  
264 -\\
229 +To choose the desired file size one has to choose a run mode configuration in the RunControlGUI
265 265  
266 -\\
231 +[[~[~[image:attach:image2020-1-17_13-39-38.png~|~|height="400"~]~]>>attach:image2020-1-17_13-39-38.png]]
267 267  
268 -\\
233 +This will however the clear the definition of selected subsystems and one has to reload the whitelist of the experiment again.
269 269  
235 +
236 +
237 +
238 +
239 +=== Assigning the DAQ to the beamline in jddd ===
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.
242 +
243 +[[image:attach:image2022-9-9_9-51-8.png||height="150"]]
244 +
245 +
270 270  === Setting the logbook to print in / putting the Whitelist name in jddd ===
271 271  
272 -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:FLASHUSER.Electronic Logbooks]]
248 +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:FLASHUSER.Data Acquisition and controls.DAQ and controls overview.E-Logbooks.WebHome]]
273 273  
274 274  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)
275 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/setting_parameters.jpg||alt="setting_parameters.jpg" width="500" height="300"]]
276 276  
277 -\\
252 +[[image:attach:setting_parameters.jpg||height="400"]]
278 278  
279 -\\
280 280  
281 -\\
282 282  
283 -\\
284 -
285 285  == In case something goes wrong: Troubleshooting ==
286 286  
287 -\\
288 -
289 289  === No //START// or //STOP// buttons are visible in the DAQ control panel ===
290 290  
291 -~* 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 ...
260 +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 ...
292 292  
293 -\\
294 294  
295 295  === The DAQ does not start a run ===
296 296  
297 -\\
298 298  
299 -* Mainly the DAQ works fine but one of the properties that should be saved is not available or somehow corrupted. There the {{code language="none"}}RC logfile{{/code}} helps (see below) to determine where to localize the problem. The pragmatic way is to exclude the subsystems which may contain the properties with problems. Thus exclude the "critical" subsystems. Start a run. If this works, include one by one the excluded subsystems and start runs. That way one should find out which subsystem causes the problem. Now one can investigate this one in more detail. Is the property available in DOOCS? Does it update? maybe restart the server providing the property ...
266 +* Mainly the DAQ works fine but one of the properties that should be saved is not available or somehow corrupted. There the {{code language="none"}}RC logfile{{/code}} helps (see below) to determine where to localize the problem. The pragmatic way is to exclude the subsystems which may contain the properties with problems. Thus exclude the "critical" subsystems. Start a run (starting with the RCGUI not with jddd DAQ control ). If this works, include one by one the excluded subsystems and start runs. That way one should find out which subsystem causes the problem. Now one can investigate this one in more detail. Is the property available in DOOCS? Does it update? maybe restart the server providing the property ...
300 300  
301 -\\
268 + as example: [[image:url:https://ttfinfo.desy.de/FELPGMelog/data/2017/15/11.04/2017-04-11T02:56:05-00.PNG||height="250"]]
302 302  
303 -\\
304 304  
305 305  === Data seems not properly saved ===
306 306  
273 +[[image:attach:RC_logfile.jpg||height="250"]]
307 307  
308 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/RC_logfile.jpg||alt="RC_logfile.jpg" width="518" height="300"]]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.
309 309  
276 + 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.
277 +
310 310  * 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 ...
311 311  * 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.
312 312  * 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.
... ... @@ -313,100 +313,139 @@
313 313  * Sometimes also a restart of the DAQ (see below) helps ... This however is more the case if the DAQ does not start at all or saves no data at all ...
314 314  * in several cases the reason is a configuration problem of the server. Then 2 servers are sending on the same "address". Then one property usually is saved without loss while the second one is only saved once in a while ( 1-5%). Here the server has to be fixed. As fast cure one can only exclude the less important subsystem and save the more important properly ...
315 315  
316 -\\
317 317  
318 -\\
319 319  
320 -\\
321 321  
322 322  === Restarting the DAQ ===
323 323  
324 -\\
325 325  
326 326  * If the RCGUI does not respond (and also the clock display does not count up) one has to restart the GUI. Usually the DAQ is not affected by the RCGUI hang up ...
327 327  
328 -\\
329 329  
330 -* Generally there 3 ways to "restart" the DAQ
331 -** 1. The least interferring way is the "all to INITIALIZE" that tries to reset the DAQ processes ... helps for simple "hickups"
332 -** 2. The "re-start DAQ" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
333 -** 3. In very hard and severe cases there is the ultimate restart button: "re-start DAQ (no RCSHM)"
293 +* Generally there** 3 ways to "restart" the DAQ**
294 +** 1. The least interfering way is the "**all to INITIALIZE**" that tries to reset the DAQ processes ... helps for simple "hickups"
295 +** 2. The "**re-start DAQ**" really reboots the whole DAQ process. The settings still should be as before ... this is the "Usual" restart
296 +** 3. In very hard and severe cases there is the **ultimate restart button: "re-start DAQ (no RCSHM)"**
334 334  
335 335  
336 -\\*Here in more detail:*
299 +//**Here in more detail:**//
337 337  
338 -\\
339 339  
340 340  * 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.
341 -** 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 (Aug 2018) 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"}}jFLASH{{/code}} command. Click on "Photons" -> Experimental Hall "Photons main panel"
342 -** The DAQ "expert" panel can be reached from the User DAQ control panel.
343 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_expert.jpg||alt="DAQ_expert.jpg" width="400" height="350"]]
303 +** **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" )
304 +** To Restart the DAQs you need the **"expert" Tab** of the  User DAQ control panel.
344 344  
345 -\\
306 + [[image:attach:image2022-9-9_10-57-31.png||height="400"]]
307 +
346 346  
347 -\\
309 +There is some description of the different ways to restart the DAQ in the panel:
348 348  
349 -*
350 -** Then you see the following "DAQ expert panel":
351 -** 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.
311 +==== **all to INITIALIZE** ====
352 352  
353 353  
354 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/UserDAQ_status.jpg||alt="UserDAQ_status.jpg" width="500" height="400"]]
314 +*
315 +** 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.
316 +** If there is no window coming up or closing right away there may be a problem with the rights. In this case you:
317 +*** may try to login at the flashlxuser machines and try there again
318 +*** or use the red "DAQ restart" Button one below. This button reacts technically different and can circumvent rights problems ... 
355 355  
356 -\\
320 +
321 + Initialize script: [[image:attach:image2022-9-9_11-6-38.png||height="250"]] parts of the DAQ are in different "states":[[image:url:https://ttfinfo.desy.de/Flash_THzStreakingelog/data/2020/49/2020-12-02T13:53:01.jpg||height="250"]]
357 357  
358 -* 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".
359 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/DAQ_restart_msg.jpg||alt="DAQ_restart_msg.jpg" width="400" height="350"]]
360 360  
361 -\\
324 +==== Restart the DAQ ====
362 362  
363 -* 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.
364 364  
365 -\\
327 +* If the "initialize"  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".
328 +* There are **actually 2 buttons** to "restart" the DAQ. They start the same restarting script - however in different ways. Thus, if one for what ever reason does not work with your configuration you may use the second one ... 
366 366  
367 -* **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.
368 -** in the jddd control the list of subsystems sais "empty"
369 -** in the RCGUI in the lower part it sais "RUN mode is not set"
370 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/restart_RCM_no_runmode.jpg||alt="restart_RCM_no_runmode.jpg" width="400" height="400"]]
330 + Script window:  [[image:attach:DAQ_restart_msg.jpg||height="400"]] Restart: [[image:attach:image2022-9-9_11-30-33.png||height="400"]]
371 371  
372 -\\
373 373  
374 -*
375 -** one has to go to the "Run Modes" tab and select the run mode {{code language="none"}}FLASH1_EXP{{/code}} by clicking on it !
376 -[[image:url:http://hasfweb.desy.de/pub/Setup/DAQjddd/runmode_set.jpg||alt="runmode_set.jpg" width="400" height="400"]]
377 -** then one has to go back to the {{code language="none"}}Subsystems{{/code}} . now all subsystems are included.
378 -** finally you have to select your White list and start a run ...
333 +* 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.
379 379  
380 -\\
335 +==== "Ultimate" restart ====
381 381  
382 -\\
337 +* **IF the DAQ still does not work properly** the final option is the: " "Ultimate" 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.
338 +** in the jddd control the list of subsystems sais "empty" [[image:attach:image2022-9-9_11-36-1.png||thumbnail="true" height="250"]]
339 +** and you have to reload the parameters to be saved from the  Whitelist.
340 +** you can use the "Runcontrol"  button right below the  "Ultimate" re-start DAQ (no RCSHM)" to start the RunControl window
341 +** choose the files ize ( best default: 1GB)[[image:attach:image2022-9-9_11-39-3.png||thumbnail="true" height="250"]]
342 +** goto "Subsystems" tab and load your Whitelist
343 +** and start a run ...
383 383  
345 +
384 384  * If there are still components not working after the "re-start DAQ (no RCSHM)" you have to call the photon coordinator (4455) and pray ...
385 385  
386 -\\
387 387  
388 -=== what else ??? ===
389 389  
390 -\\
350 +----
391 391  
392 -\\
352 +== [[Some more details for experts ...>>doc:FLASH.Collection of Detailsof the DAQ from various times \.\.\. not for public use]] ==
393 393  
394 -----
354 +=== Re-read the data base ===
395 395  
396 -[[Some more details for experts ...>>url:http://hasfweb.desy.de/bin/view/Setup/DaqDetails||shape="rect" class="twikiLink"]]
356 +If there are new Properties included by Vladimir et al one has to reread the data base.
397 397  
398 -\\
358 +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.
399 399  
400 -=== Re-read the data base ===
401 401  
402 -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:
361 +OR one can do the hard way:
403 403  
404 -{{code language="none"}}Options -> "Show Expert Menu"{{/code}}
363 +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:
405 405  
365 +{{code language="none"}}
366 +Options -> "Show Expert Menu"
367 +{{/code}}
368 +
406 406  Then you go to {{code language="none"}}"Expert" -> "Run Control Commands" -> "Remove SHM"{{/code}} (occasionally twice).
407 407  
408 408  After you see a message in the RCGUI messages window that the SHM was removed you do:
409 409  
410 -{{code language="none"}}"expert" -> "Run Control Commands" -> "Re-init SHM"{{/code}}
373 +{{code language="none"}}
374 +"expert" -> "Run Control Commands" -> "Re-init SHM"
375 +{{/code}}
411 411  
412 412  Now close the RCGUI and start it again. Switch to the tab "subsystems", wait for the subsystems to be reloaded and load the whitelist you want to use.
378 +
379 +
380 +Tracking DAQ restarts
381 +
382 +A system was implemented (March 2020) where each restart of a user DAQ is recorded in a log file
383 +
384 +One can see all log files in :
385 +
386 +/home/doocsadm/bm/rcdb/restartslog/
387 +
388 +=== data base errors ===
389 +
390 +The red flags next to the  different stream indicators tell something about data base errors
391 +
392 +
393 +[[image:attach:2021-02-10 15_23_20-How to save data in the User DAQ - FS-FLASH USER - DESY Confluence.png||width="600"]]
394 +
395 +upper flag:  There was a problem to read run catalogue
396 +
397 +lower flag: There was a problem to read dccp catalogue.
398 +
399 +In both cases there are counters of failures to read a catalogue. If this counter is not incrementing with every attempt to read a catalogue, then it's no problem. It can be monitored and reset in the panel that one gets by pressing on "green" area.
400 +
401 +
402 +=== raw writers ===
403 +
404 +(all user DAQs are using stream 2) [[image:attach:image-2023-12-14_13-50-19.png||width="318"]]
405 +
406 +what raw writers are used ? ... They are defined in {{code language="none"}}FLASH.DAQ/FLxUSERy.EVENTBUILDER/EVB.STREAM.2/EVB.ROOT.SRVRS {{/code}} as XML string
407 +
408 +what is the current raw writer? ... {{code language="none"}}FLASH.DAQ/FLxUSERy.EVENTBUILDER/EVB.STREAM.2/CUR.RAW.WRITER{{/code}}
409 +
410 +OR
411 +
412 +one can have a look at the Offline monitor :[[image:attach:image-2023-12-14_13-51-33.png||width="406"]]
413 +
414 +FLASH.DAQ/FL1USER1.DAQ.OFFL.MONITOR/MONITOR/LAST.FILE
415 +
416 +FLASH.DAQ/FL1USER1.DAQ.OFFL.MONITOR/MONITOR/CUR.WRITER
417 +
418 +
419 +
2021-02-10 15_23_20-How to save data in the User DAQ - FS-FLASH USER - DESY Confluence.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +43.7 KB
Content
DAQ_expert.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +91.2 KB
Content
DAQ_restart_msg.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +114.4 KB
Content
DAQgui1.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +243.3 KB
Content
DAQgui2.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +192.6 KB
Content
RCGUI_2.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +139.3 KB
Content
RCGUI_properties.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +178.5 KB
Content
RC_logfile.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +154.7 KB
Content
UserDAQ_status.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +92.8 KB
Content
daq_monitor_config.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +82.3 KB
Content
daqgui3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +86.7 KB
Content
image-2023-12-14_13-50-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +6.5 KB
Content
image-2023-12-14_13-51-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +24.0 KB
Content
image2019-10-24_15-29-36.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +282.7 KB
Content
image2019-10-24_15-32-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +370.6 KB
Content
image2020-1-17_13-39-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +343.1 KB
Content
image2022-9-8_10-50-53.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +242.2 KB
Content
image2022-9-8_10-57-56.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +278.7 KB
Content
image2022-9-8_11-14-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +62.0 KB
Content
image2022-9-9_10-57-31.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +447.8 KB
Content
image2022-9-9_11-23-34.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +81.5 KB
Content
image2022-9-9_11-24-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +1.1 MB
Content
image2022-9-9_11-30-33.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +376.2 KB
Content
image2022-9-9_11-36-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +38.2 KB
Content
image2022-9-9_11-39-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +52.8 KB
Content
image2022-9-9_11-6-38.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +190.5 KB
Content
image2022-9-9_9-51-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +155.3 KB
Content
jddd_DAQ-control-manual-how_to_get.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +240.6 KB
Content
jddd_DAQ-control-manual2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +208.4 KB
Content
restart_RCM_no_runmode.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +131.4 KB
Content
runmode_set.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +78.0 KB
Content
setting_parameters.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +42.1 KB
Content
whitelist.jpg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +26.4 KB
Content