Skip to Content
Last modified by sndueste on 2025-09-08 15:36
From version 27.1
edited by erlandm
on 2021-06-17 15:46
Change comment: There is no comment for this version
To version 28.1
edited by sndueste
on 2022-09-08 11:18
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.erlandm
1 +XWiki.sndueste
Content
... ... @@ -7,7 +7,7 @@
7 7  == General Concept ==
8 8  
9 9  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.
10 -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)
10 +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 two at FLASH 2 (FLASH2_USER1, FLASH2_USER2)
11 11  How to save this experiment related "User-Data" will be explained briefly in this page:
12 12  
13 13  \\
... ... @@ -20,19 +20,20 @@
20 20  
21 21  === DAQ control panel ===
22 22  
23 -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}}
23 +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}}
24 24  
25 -[[image:attach:jddd_DAQ-control-manual-how_to_get.png||height="400"]]
25 +[[image:attach:jddd_DAQ-control-manual-how_to_get.png||width="500"]][[image:attach:image2022-9-8_10-50-53.png||width="450"]]
26 26  \\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:
27 27  
28 -[[image:attach:jddd_DAQ-control-manual2.png||height="400"]]
28 +[[image:attach:jddd_DAQ-control-manual2.png||width="800"]]
29 29  \\\\
30 30  
31 31  \\
32 32  
33 -* 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:FLASH.Electronic Logbooks]] (DESY internal link)
34 -* After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
35 -* 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 ...
33 +* 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]].
34 +* 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"]]
35 +* NOTE: After starting, the stop button appears only after saving abut 200 shots to prevent too early stopping which may disturb the DAQ.
36 +* 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 ...
36 36  
37 37  \\
38 38  
... ... @@ -81,7 +81,7 @@
81 81  
82 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,flashlxuser2{{/code}} or {{code language="none"}}flashlxuser3{{/code}} and start {{code language="none"}}DAQdataGUI{{/code}} from the command line.
85 +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 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).
85 85  
86 86  
87 87  \\To access the desired data one has to:
... ... @@ -135,12 +135,16 @@
135 135  [[image:attach:RCGUI_2.jpg||height="400"]]
136 136  \\
137 137  
138 -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}}.
139 -Log in with the beamline account (bl1user, bl2user, ..., fl24user...) either via X-Win32 from windows or via ssh from Linux machines.
140 -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:
141 -
142 142  \\
143 143  
141 +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}}.
142 +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.
143 +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 :
144 +
145 +[[image:attach:image2022-9-8_11-14-7.png||border="true" width="343" height="250"]]
146 +
147 +Or in the command line:
148 +
144 144  (% class="wrapped" %)
145 145  |(((
146 146  Unix command
... ... @@ -175,7 +175,16 @@
175 175  )))|(((
176 176  FLASH2_USER1 DAQ
177 177  )))
183 +|(% colspan="1" %)(((
184 +{{code language="none"}}
185 +RCGUIFL2USER2
186 +{{/code}}
187 +)))|(% colspan="1" %)(((
188 +FLASH2_USER2 DAQ
189 +)))
178 178  
191 +\\
192 +
179 179  Which DAQ to use is decided by the FLASH DAQ team according to the beamtime schedule.
180 180  
181 181  [[image:attach:RCGUI_properties.jpg||height="400"]]
... ... @@ -182,7 +182,7 @@
182 182  
183 183  \\
184 184  
185 -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]].
199 +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:FLASHUSER.Configuring the user DAQs]].
186 186  
187 187  \\
188 188