Wiki source code of The FLASH HDF5 structure

Version 84.1 by sndueste on 2024/05/17 11:22

Show last authors
1 {{layout}}
2 {{layout-section ac:type="single"}}
3 {{layout-cell}}
4 == Contents ==
5
6
7
8 {{toc/}}
9
10
11 == General information about HDF5 ==
12
13 HDF5 is a data format maintained by the HDF group. For detailed general information see [[here>>url:https://portal.hdfgroup.org/display/support||shape="rect"]]
14
15 To download the HDF5 Viewer click [[here>>url:https://portal.hdfgroup.org/display/support/Download+HDFView||shape="rect"]]
16
17 For use on the DESY Maxwell or PAL (max-fsc or pal) **hdfview** is available in the xray module :
18 {{code language="none"}}> module load xray{{/code}}
19 {{code language="none"}}> hdfview{{/code}}
20
21 or you can use
22
23 {{code language="none"}}
24 > silx view
25 {{/code}}
26
27
28 [[Contents>>doc:||anchor="Contents"]]
29
30 == The FLASH HDF5 format ==
31
32 FLASH provides a conversion of its data acquisition (DAQ) to the commonly used [[HDF5>>url:https://www.hdfgroup.org/solutions/hdf5/||shape="rect"]] format. Correlated  data are mapped by a primary index called **train ID**. Every data set has an individual index of train IDs to identify the data even when data are missing or deviate in update rate. If the data set of choice contains gaps,  users have to decide how to treat missing values. DAQ channels are spread across various files with one file name pattern for each DAQ. This means users have to assemble data from different files if necessary.
33
34 The hierarchy is realized using a human readable named HDF tree with each DAQ channel containing the data sets "//value//" and "//index//". Additionally, the HDF group //zraw// contains a tree of the original DAQ channel names.
35
36 Reference implementation, which follows the concept of Python libraries like Pandas, Xarray, or Dask, is given below.
37
38 {{expand title="Discontinued HDF formats"}}
39 === Comparison to FLASH's deprecated HDF formats ===
40
41 Before 2021, FLASH provided two different HDF formats formally known as //near-online// and //offline// HDF files.
42
43 All data sets were aligned by the same global index by filling in missing data. Fast DAQ channels  (pulse synchronous data - update 10 Hz) are filled in by NaN or 0, slow channels (not pulse synchronous data - update e.g. 1 Hz ) are interpolated by the DAQs libraries, by keeping the value constant up to the next change.
44
45 While the near-online HDF files were converted live during the beamtime, the offline HDF files were manually compiled weeks/months later. Near-online HDF files were used by a provided API [[BeamtimeDaqAccess>>url:https://confluence.desy.de/display/FLASHUSER/Near-Online+data+analysis#Near-Onlinedataanalysis-BriefUserGuidetoBeamtimeDAQAccess||shape="rect"]], which also searches for DAQ channels in files. With assembled files "by run", all DAQ channels were existing in the same HDF file. While shorter runs usually fitted into one file, longer runs still had to be aggregated over several files. The creation of the assembled type of files still involves the use of fairly unstable DAQ Mex-functions As the environment required for using the Mex-functions is already deprecated, its continued existence is uncertain.
46
47 The HDF hierarchy is almost identical in all formats. While in the the recent format each DAQ channel contains the data sets "value" and "index", the deprecated format had one data set for each DAQ channel. The deprecated formats supplies no time axis parameters for spectra data types.
48
49
50 **HDF5 example files (old format)**
51
52 Here we have a few HDF5 samples (User data combined with Photon diagnostics data) from a few beamtimes showing the different kind options.
53
54 [[image:attach:image2019-10-21_17-2-50.png||thumbnail="true" width="300"]] [[download HDF5 (Images @ FL2)>>url:https://desycloud.desy.de/index.php/s/nyEgeCWJFC4gao2||shape="rect"]]
55
56
57 [[~[~[image:attach:image2019-10-22_10-52-27.png~|~|thumbnail="true" width="300"~]~]download HDF5 (GHz ADC and OPIS @ FL2)>>url:https://desycloud.desy.de/index.php/s/AeA2kPNNnZgX95A||shape="rect"]]
58
59
60
61 {{/expand}}
62
63 === HDF examples: ===
64 {{/layout-cell}}
65 {{/layout-section}}
66
67 {{layout-section ac:type="three_equal"}}
68 {{layout-cell}}
69 * ADC data as example for **fast** **data** (10 Hz):            
70
71 [[image:attach:image2020-11-16_15-26-28.png||height="250"]]
72 {{/layout-cell}}
73
74 {{layout-cell}}
75 * The //average// FEL pulse energy as example for the **slow** **data**. Here the data is not saved with 10 Hz  - thus not for every FEL pulse train.  The data is typically saved with 1 Hz if the values are changing (like the FEL energy) and every about 20 sec if there is no change for longer time ( e.g. motor set values). Thus to use the data together with the "fast" one, one has to interpolate the data as explained in the examples in the repos below show (e.g. {{code language="none"}}df['GMD_T_average'] = df['GMD_T_average'].interpolate(method='linear'){{/code}})
76
77 ( as example only every 10th train ID is listed in the HDF group "index")
78
79 [[image:attach:image2020-11-16_15-31-45.png||height="250"]]
80 {{/layout-cell}}
81
82 {{layout-cell}}
83 * (((
84 //zraw// group contains the **original DAQ (DOOCS) names**
85 )))
86
87 of the properties saved in the DESY internal raw format. (For experts)
88
89
90 [[image:attach:image2020-11-16_16-26-3.png||height="400"]]
91 {{/layout-cell}}
92 {{/layout-section}}
93
94 {{layout-section ac:type="single"}}
95 {{layout-cell}}
96 {{info}}
97 === There are different options that help you to work with the FLASH HDF5 data in Python ===
98
99 * The currently developed option for large data sets: [[the FAB package>>url:https://hasfcpkg.desy.de/fab/fab.html||shape="rect"]] ... see below
100 * and for smaller projects:  (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]]
101
102 (% class="Object" %)See also the collection of Demo data and sample scripts : [[doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]
103 {{/info}}
104 {{/layout-cell}}
105 {{/layout-section}}
106
107 {{layout-section ac:type="single"}}
108 {{layout-cell}}
109
110
111 == Complete list of recordable parameters ==
112
113 The complete list for the relation between DOOCS names and HDF5 names for the recordable parameters can be found in [[DESY's Repository>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat||shape="rect"]].
114
115
116 == Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
117
118 {{id name="DOOCSparameters"/}}
119
120 Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
121
122
123 === FLASH1 ===
124
125 ==== Beamline info (FLASH1) ====
126
127 {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
128 //always saved (PBD)//
129 DOOCS prop : {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
130 DAQ channel: {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
131 desc: set pressure in the gas attenuator
132 units: mbar
133
134
135 {{code language="none"}}/FL1/Beamlines/BL/Fast shutter/open{{/code}}
136 //always saved (PBD)//
137 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/BL.SHUTTER/CH00.TD{{/code}}
138 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/BL.SHUTTER{{/code}}
139 desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
140 units: none
141
142 {{code language="none"}}/FL1/Beamlines/PG/Fast shutter/open{{/code}}
143 //always saved (PBD)//
144 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/PG.SHUTTER/CH00.TD{{/code}}
145 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL1FS/PG.SHUTTER{{/code}}
146 desc: PG Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
147 units: none
148
149 {{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 1{{/code}}
150 //always saved (PBD)//
151 DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
152 DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
153 desc: Position of the BL filter wheel 1 - to correlate with the filter material please look [[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
154 units: degree
155
156
157 {{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 2{{/code}}
158 //always saved (PBD)//
159 DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
160 DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
161 desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
162 units: degree
163
164
165 {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 1{{/code}}
166 //always saved (PBD)//
167 DOOCS prop : = TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS=
168 DAQ channel: {{code language="none"}}TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS{{/code}}
169 desc: Position of the PG filter wheel 1
170 units: degree
171
172
173 {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 2{{/code}}
174 //always saved (PBD)//
175 DOOCS prop : {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
176 DAQ channel: {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
177 desc: Position of the PG filter wheel 2
178 units: degree
179
180
181 {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 3{{/code}}
182 //always saved (PBD)//
183 DOOCS prop : {{code language="none"}}TTF2.FEL/PGFILTERS/PGFILTERS/FW.MOTOR.POS{{/code}}
184 DAQ channel: {{code language="none"}}TTF2.FEL/PGFILTERS/PGFILTERS/FW.MOTOR.POS{{/code}}
185 desc: Position of the PG filter wheel 3
186 units: degree
187
188
189
190 NOTE: Aperture positions in the beamline as well as the positions of the beam steering mirrors are also saved. For more Info contact your local contact
191
192 [[Contents>>doc:||anchor="Contents"]]
193
194
195 ==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]]) ====
196
197 {{expand title="Discontinued GMD format (used until 2021)"}}
198 (% style="color:#000000" %)**Discontinued GMD data recording / evaluation  (VME + PhotonFlux ML server)**
199
200 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
201 //always saved (PBD)//
202
203 (% style="color:#000000" %)DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT04/VAL{{/code}} (%%)
204 (% style="color:#000000" %)DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENPULSEIC{{/code}}(%%)
205 desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator (ion current)
206 units : microJ
207
208 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
209 //always saved (PBD)//
210
211 DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
212 DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
213 desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
214 units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) **[[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
215
216 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel (raw){{/code}}
217 //always saved (PBD)//
218 DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT14/VAL{{/code}}
219 DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.FF{{/code}}
220 desc :Energy per pulse Tunnel (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
221 units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) **[[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
222
223 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
224 //always saved (PBD)//
225
226 DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT05/VAL{{/code}}
227 DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENPULSEIC{{/code}}
228 desc : calibrated average SASE Energy/pulse measured in the BDA (in the experimental hall) after the attenuator (ion current)
229 units : microJ
230
231 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA{{/code}}
232 //always saved (PBD)//
233
234 DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
235 DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
236 desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
237 units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) **[[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
238
239 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA (raw){{/code}}
240 //always saved (PBD)//
241 DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT15/VAL{{/code}}
242 DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
243 desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
244 units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision)** [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
245 {{/expand}}
246
247
248 (% style="color:#000000; letter-spacing:0px" %)**NEW (since 2021) GMD data recording / evaluation  (same format as FLASH2 and XFEL)**
249
250 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
251 //always saved (PBD)//
252 (% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)
253 (% style="color:#000000" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}
254
255 desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator
256 units : microJ
257
258
259 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
260 //always saved (PBD)//
261
262 (% style="color:#000000" %)DOOCS prop : 
263 {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TD{{/code}}DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TD{{/code}}
264
265 desc : Energy per pulse measured in the Tunnel.  In addition measurement errors and beam position are included for EACH pulse in the pulse train  !! (see below)
266 units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision)** [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
267
268 {{info title="GMD pulse resolved data structure"}}
269 For every pulse in the pulse train the information is saved:
270
271
272 1. **Intensity per pulse** (a.u. (more or less µJ ))
273 1. Intensity per pulse (auxillary GMD) - not used
274 1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
275 1. Position vertical (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
276 1. **Intensity per pulse sigma** (a.u. (more or less µJ ), (% style="color:#000000" %)This parameter gives an indication of the error of the measurement of the pulse energy. This takes signal to noise,  detector resolution, uncertainties in crossection etc into account. (it is NOT the measurement of the statistical fluctuation of the SASE pulses)(%%))
277 1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
278 1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
279 1. Combined warning and error flags
280
281 The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this 
282 file
283
284
285 [[image:attach:image2021-2-9_10-51-6.png||height="250"]]
286
287
288 {{/info}}
289
290 All values for the GMD are also available for the** BDA GMD **which is located in the experimental hall down stream the gas attenuator. If the attenuator is on the ratio between BDA and Tunnel signal shows the attenuation. **BUT NOTE** that the filter units  are downstream the GMD. So if filters  are used this influence is NOT measured by the GMD BDA !
291
292
293 Besides  pulse energy the GMD also provides information about the beam position
294
295 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal{{/code}}
296 //always saved (PBD)//
297 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
298 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
299 desc :Beam position of the photon Beam determined by the GMD (BDA, x=horizontal)
300 units : mm
301
302 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA vertical{{/code}}
303 //always saved (PBD)//
304 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS{{/code}}
305 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS{{/code}}
306 desc :Beam position of the photon Beam determined by the GMD (BDA, y=vertical)
307 units : mm
308
309 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position tunnel horizontal{{/code}}
310 //always saved (PBD)//
311 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS{{/code}}
312 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS{{/code}}
313 desc :Beam position of the photon Beam determined by the GMD (TUNNEL, x=horizontal)
314 units : mm
315
316 {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position tunnel vertical{{/code}}
317 //always saved (PBD)//
318 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS{{/code}}
319 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS{{/code}}
320 desc :Beam position of the photon Beam determined by the GMD (TUNNEL, y=vertical)
321 units : mm
322
323
324 ==== Spectrometer (FLASH1) ====
325
326 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength{{/code}}
327 _always saved (when Spectrum is measured !!) (PBD) _
328 DOOCS prop : {{code language="none"}}TTF2.EXP/PHOTONWL.ML/WAVE_LENGTH/VAL.TD{{/code}}
329 DAQ channel: {{code language="none"}}PBD.PHOTONWL.ML/WAVE_LENGTH{{/code}}
330 desc : XUV Spectrum measured with the "tunnel spectrometer"
331 units :
332
333 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength start value{{/code}}
334 _always saved (when Spectrum is measured !!) (PBD) _
335 DOOCS prop : {{code language="none"}}TTF2.EXP/PBD.PHOTONWL.ML/BSTART/VAL{{/code}}
336 DAQ channel: {{code language="none"}}TTF2.EXP/PBD.PHOTONWL.ML/BSTART/VAL{{/code}}
337 desc : start value (in nm) for the wavelength axis of the XUV Spectrum measured with the "tunnel spectrometer"
338 units : nm
339
340 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength increment{{/code}}
341 _always saved (when Spectrum is measured !!) (PBD) _
342 DOOCS prop : ==
343 DAQ channel: ==
344 desc : increment value (in nm) for each pixel for the wavelength axis of the XUV Spectrum measured with the "tunnel spectrometer"
345 units : nm
346
347 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy{{/code}}
348 //saved on DEMAND (PBD spectrometer stream)//
349 DOOCS prop : ==
350 DAQ channel: {{code language="none"}}PBD.PHOTONEN.ML/PHOTON_ENERGY{{/code}}
351 desc : XUV Spectrum in eV measured with the "PG2 spectrometer"
352 units :
353
354 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy start value{{/code}}
355 //saved on DEMAND (PBD spectrometer stream)//
356 DOOCS prop : ==
357 DAQ channel: ==
358 desc : start value (in eV) for the wavelength axis of the XUV Spectrum measured with the "PG2 spectrometer"
359 units : eV
360
361 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy increment{{/code}}
362 //saved on DEMAND (PBD spectrometer stream)//
363 DOOCS prop : ==
364 DAQ channel: ==
365 desc : increment value (in eV) for each pixel for the wavelength axis of the XUV Spectrum measured with the "PG spectrometer"
366 units : eV
367
368 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength{{/code}}
369 //saved on DEMAND (PBD spectrometer stream)//
370 DOOCS prop : ==
371 DAQ channel: {{code language="none"}}PHOTONEN.ML/PHOTON_WAVE_LEN{{/code}}
372 desc : XUV Spectrum in nm measured with the "PG2 spectrometer"
373 units :
374
375 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength increment{{/code}}
376 //saved on DEMAND (PBD spectrometer stream)//
377 DOOCS prop : ==
378 DAQ channel: ==
379 desc : start value (in nm) for the wavelength axis of the XUV Spectrum measured with the "PG2 spectrometer"
380 units : nm
381
382 {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength start value{{/code}}
383 //saved on DEMAND (PBD spectrometer stream)//
384 DOOCS prop : ==
385 DAQ channel: ==
386 desc : increment value (in nm) for each pixel for the wavelength axis of the XUV Spectrum measured with the "PG spectrometer"
387 units : nm
388
389 [[Contents>>doc:||anchor="Contents"]]
390
391 ==== Electron Beam properties (FLASH1) ====
392
393 ===== bunch charge =====
394
395 {{code language="none"}}/FL1/Electron Diagnostic/Bunch charge/after undulator{{/code}}
396 //always saved (PBD)//
397 DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/12EXP/CHARGE.FLASH1{{/code}}
398 DAQ channel: {{code language="none"}}FLASH.DIAG/TOROID/12EXP{{/code}}
399 desc: electron bunch charge (FLASH1)
400 units: nC
401
402 =====
403 arrival time (BAM) =====
404
405 {{info title="BAM information: updates 2022"}}
406 * see: [[Info collection about the BAMs and how to use the BAM data>>url:https://confluence.desy.de/display/FLASHUSER/Info+collection+for+the+BAM||shape="rect"]]
407 * The data format of the BAM has been completely altered in the 2022 shutdown
408 * before 2022 BAMs were always saving the arrival time information for each 1µs bucked regardless if there were electrons in the accelerator or not. IN addition the arrival times for  FL1 and FL2 were saved in the same parameter ...
409 * THIS is now different. There are new parameters saving only the arrival times for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second)
410 * There has been also a renaming  (and relocation) of the BAMs.
411 ** acc:  4DBC3 → FL0.DBC2
412 ** FL1: 1SFELC →  FL1.SFELC
413 ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
414 * for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
415 * [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]]
416 * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
417 {{/info}}
418
419 {{expand title="Discontinued BAM format (used until end 2021)"}}
420 (% style="color:#000000" %)**Discontinued BAM data recording **
421
422 {{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
423 //always saved (PBD)//
424 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
425 DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
426 desc: Electron bunch arrival time measured with the BAM inside the accelerator - however shows a very good correlation to the arrivaltime  of the XUV pulses in the experiment (pulse resolved data).
427 units: ps (bigger numbers indicate later arrivaltime of the electrons)
428
429
430 {{code language="none"}}/FL1/Electron Diagnostic/BAM/1SFELC/electron bunch arrival time (low charge){{/code}}
431 //always saved (PBD)//
432 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/1SFELC/LOW_CHARGE_ARRIVAL_TIME{{/code}}
433 DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/1SFELC.LOW_CHARGE_ARRIVAL_TIME{{/code}}
434 desc: Electron bunch arrival time measured with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020.
435 units: ps (bigger numbers indicate later arrival time of the electrons)
436 {{/expand}}
437
438 ====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
439
440 (% style="color:#ff6600" %)**DBC2**/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)(%%)
441 //always saved (PBD)//
442 {{code language="none"}}/FL1/Electron Diagnostic/BAM/ {{/code}}DOOCS prop : FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
443 DAQ (% style="color:#000000" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA1.COMP (%%)
444 desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). The property contains only the arrival time of the bunches sent to FL1 (e.g. if there are 30 bunches in FL1 the first 30 values are the arrival time the remaining numbers  still may have arbitrary numbers looking like a signal which they are not ). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time  of the XUV pulses in the experiment (see help).
445
446 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
447
448
449 (% style="color:#ff6600" %)DBC2/electron bunch arrival time (raw)  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
450 //always saved (PBD)//
451 DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE
452 DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE (%%)
453 desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 1 in the first part. they may be separated by several "0" values if the reprate is different from 1 MHz ...  - It shows a very good correlation to the arrival time  of the XUV pulses in the experiment (see help). 
454 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
455
456
457 (% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
458 //always saved (PBD)//
459 DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E.bamError(%%)
460 DAQ channel: (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%)
461 desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
462
463
464 (% style="color:#ff6600" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
465 //always saved (PBD)//
466 DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color:#000000" %)E..bamStatus.//1//(%%)
467 DAQ channel(% style="color:#000000" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.1(%%)
468 desc: (% style="letter-spacing:0.0px" %) status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting;  mostly check for bit 0 == 1 is sufficient
469
470
471 ====== **BAM FL1.SFELC**{{code language="none"}}{{/code}} ======
472
473 (% style="font-family:SFMono-Medium,~"SF Mono~",~"Segoe UI Mono~",~"Roboto Mono~",~"Ubuntu Mono~",Menlo,Courier,monospace; letter-spacing:0.0px" %)/FL1/Electron Diagnostic/BAM/**SFELC**(% style="color:#ff6600" %)/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)
474
475 //always saved (PBD)//
476 (% style="color:#172b4d" %)**FL1.SFELC**(%%)
477 (% style="color:#000000" %)channel: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
478 {{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ {{/code}}(% style="letter-spacing:0.0px" %)desc: Electron bunch arrival time measured  with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020.. The property contains only the arrival time of the bunches sent to FL1 (e.g. if there are 30 bunches in FL1 the first 30 values are the arrival time the remaining numbers still may have arbitrary numbers looking like a signal which they are not). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time  of the XUV pulses in the experiment (see help).
479 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
480
481
482
483 (% style="color:#172b4d" %)SFELC(% style="color:#ff6600" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
484 //always saved (PBD)//
485 DOOCS prop : FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(%%)/ARRIVAL_TIME.ABSOLUTE
486 DAQ channel:** **(% style="color:#000000" %)FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.ABSOLUTE (%%)
487 desc: Electron bunch arrival time measured  with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020. Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 1 in the first part. they may be separated by several "0" values if the reprate is different from 1 MHz ...  - It shows a very good correlation to the arrival time  of the XUV pulses in the experiment (see help). 
488 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
489
490
491 (% style="color:#172b4d" %)SFELC(% style="color:#ff6600" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
492 //always saved (PBD)//
493 DOOCS prop : FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color:#000000" %)E.bamError(%%)
494 DAQ channel(% style="color:#000000" %): FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMERROR(%%)
495 desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
496
497
498 (% style="color:#172b4d" %)SFELC(% style="color:#ff6600" %)/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
499 //always saved (PBD)//
500 DOOCS prop : FLASH.SDIAG/BAM/(% style="color:#172b4d" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color:#000000" %)E..bamStatus.//1//(%%)
501 DAQ chann(% style="color:#000000" %)el: FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMSTATUS.1(%%)
502 desc: status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting;  mostly check for bit 0 == 1 is sufficient
503
504
505
506 ===== electron beam profile =====
507
508 {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile{{/code}}
509 //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
510 DOOCS prop : {{code language="none"}}TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/OUT.PROF.CCCED{{/code}}
511 DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED{{/code}}
512 desc: temporal profile of electron bunch, y axis in Ampers (FLASH1)
513 units: pixel
514
515
516 {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant{{/code}}
517 //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
518 DOOCS prop : {{code language="none"}}TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/CALIB.CONST.T{{/code}}
519 DAQ channel: = PBD.BEAM.PROF.ML/CCT=
520 desc: TDS calibration constant for the x-axis of the profiles: fs per pixel
521 units: fs per pixel
522
523
524 {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms{{/code}}
525 //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
526 DOOCS prop : {{code language="none"}}TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/SOWS.W.CCTED{{/code}}
527 DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/PROFWIDTHCCTED{{/code}}
528 desc: rms pulse width of the measures TDS electron bunch profile
529 units: fs
530
531 ===== electron bunch energy =====
532
533 {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/average electron energy{{/code}}
534 //always saved (PBD)//
535 DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
536 DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
537 desc: electron bunch energy (average over the bunch train)
538 units: (% class="twikiNewLink" %)MeV(%%)
539
540
541 {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
542 //always saved (PBD)//
543 DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD{{/code}}
544 DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_SPECT{{/code}}
545 desc: electron bunch energy bunch resolved
546 units: (% class="twikiNewLink" %)MeV
547
548
549 {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average{{/code}}
550 //always saved (PBD)//
551 DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL{{/code}}
552 DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
553 desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
554 units: nm
555
556
557 [[Contents>>doc:||anchor="Contents"]]
558
559
560 ==== Timing information, rep rate etc.  (FLASH1) ====
561
562 ===== bunch repetition rate =====
563
564 {{code language="none"}}/FL1/Timing/repetition rate{{/code}}
565 //always saved (PBD)//
566 DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}}
567 DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}
568 desc: repetition rate of the bunches / pulses within the burst (FLASH1)
569 units: kHz
570
571
572 ===== set number of pulses =====
573
574 (% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/FL1/Timing/set number of bunches {{/code}}(%%)
575 //always saved (PBD)//
576 DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
577 DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
578 desc: Number of bunches set in the control (timing) system.  The property contains 4 numbers. the last one is the number of pulses (see also [[doc:FLASH.Timing properties]] (internal link)).  If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated and thus the actual number of pulses may be smaller than the set one 
579 units:
580
581 ===== actual number of pulses =====
582
583 {{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
584 //always saved (PBD)//
585 DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/12EXP/NUMBEROFBUNCHES.FLASH1{{/code}}
586 DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
587 desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH1)
588 units:
589
590
591 ===== actual pulse pattern recorded after the undulator =====
592
593 {{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
594 //always saved (PBD)//
595 DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
596 DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
597 desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
598 units:
599
600
601 ===== Train ID =====
602
603 {{code language="none"}}/Timing/train ID{{/code}}
604 //always saved (PBD)//
605 DOOCS prop : {{code language="none"}}none{{/code}}
606 DAQ channel: {{code language="none"}}none{{/code}}
607 desc: Each 10 Hz burst has its unique train ID. For the HDF5 data set the ID is the same for all parameters with the same index (note camera images may be shifted by 1 ID - talk to the experts !)
608 units:
609
610
611 ===== Train time =====
612
613 {{code language="none"}}/Timing/train time{{/code}}
614 desc:Local time as array of day, hour, minute, second, and centisecond. This data set is meant for visualization purposes only. For correlations use the train ID or the Unix time of the time stamp
615 units: d h min s cs
616
617
618 {{code language="none"}}/Timing/time stamp{{/code}}
619 desc:first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date ~-~-date='@1553617729' or matlab, python etc
620 second column: microseconds
621 third column: Train ID of FLASH
622
623
624 [[Contents>>doc:||anchor="Contents"]]
625
626
627 ==== Pump Probe Laser (FLASH1) ====
628
629 **PIGLET (PG laser)**
630
631 **{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}**
632
633 {{info width="30%"}}
634 list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
635
636 Download the PDF:
637
638 {{view-file att--filename="FSLADAQ-DAQParameterlistPiGLET.pdf"}}{{/view-file}}
639
640
641
642 {{/info}}
643
644 {{expand title="Parameters used until 2021"}}
645 {{code language="none"}}
646 /FL1/Experiment/Pump probe laser/laser attenuation
647 {{/code}}
648
649 //always saved (PBD)//
650 DOOCS prop : {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/ROT2.CURRENT{{/code}}
651 DAQ channel: {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/ROT2.CURRENT{{/code}}
652 desc: attenuation of the PPLaser (rotation of a waveplate)
653 units : 0 no transmission , 1: full transmission
654
655
656 {{code language="none"}}/FL1/Experiment/Pump probe laser/laser delay{{/code}}
657 //always saved (PBD)//
658 DOOCS prop : {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/DLY1.CURRENT{{/code}}
659 DAQ channel: {{code language="none"}}TTF2.FEL/PPDELAYCAL/PPDELAYCAL/DLY1.CURRENT{{/code}}
660 desc: delay of the Pump probe laser - measured by the read back position of the motor. only read out every secound ... better use the encoder
661 units : ps ( pos delay means IR comes later)
662
663
664 {{code language="none"}}/FL1/Experiment/Pump probe laser/delay line IK220.0/ENC.DELAY{{/code}}
665 //always saved (PBD)//
666 DOOCS prop : {{code language="none"}}TTF2.FEL/DELLINE.ENC/IK220.0/ENC.DELAY{{/code}}
667 DAQ channel: {{code language="none"}}TTF2.FEL/DELLINE.ENC/IK220.0:ENC.DELAY{{/code}}
668 subsystem: {{code language="none"}}DELLINE.ENC{{/code}} desc : delay of the Pump probe laser - measured by an encoder. The position is read out with 10Hz train synchronized and should be used to determine the actual laser delay (the motor position is only read out about every second
669 units : ps ( pos delay means IR comes later)
670
671
672 {{code language="none"}}/FL1/Experiment/Pump probe laser/Synchronization/timing jitter RMS GECCO{{/code}}
673 //always saved (PBD)//
674 DOOCS prop : {{code language="none"}}FLASH.SYNC/F1PPL.LASER_LOCK/28C.F1PPL1.CONTROLLER/ADV_CTRL_MANAGER.0.PID_INPUT_JITTER.2.RD{{/code}}
675 DAQ channel: {{code language="none"}}FLASH.SYNC/F1PPL.LASER_LOCK/28C.F1PPL1.CONTROLLER/ADV_CTRL_MANAGER.0.PID_INPUT_JITTER.2.RD{{/code}}
676 desc: rms jitter of the GECCO (% class="twikiNewLink" %)TiSa(%%) Oscillator units: fs
677
678
679 {{code language="none"}}/FL1/Experiment/Pump probe laser/streak camera delay time{{/code}}
680 //always saved (PBD)//
681 DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
682 DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
683 desc: delay time between the optical laser and the FEL units: ps
684 {{/expand}}
685
686
687 [[Contents>>doc:||anchor="Contents"]]
688
689
690 ==== User Data (FLASH1) ====
691
692 The data saved specifically for detectors at an experiment will show up in /Experiment/ there is a large number of options for cameras or monitoring of slow properties (motor positions etc) for user experiments. For details please ask your local contact.
693
694 NOTE: If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with the DOOCS names
695
696 The most common and permanently installed device used by experiment are our ADCs:
697
698 ===== GHz ADCs =====
699
700 ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found** [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]**
701 //saved on DEMAND in the user DAQ//
702 \\The HDF5 names for the ADC traces are depending on the beamline :
703 \\PG Beamline:
704 {{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH00/TD{{/code}}
705 {{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH01/TD{{/code}}
706 {{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH02/TD{{/code}}
707 {{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH03/TD{{/code}}
708
709 BL Beamlines:
710 {{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH00/TD{{/code}}
711 {{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH01/TD{{/code}}
712 {{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH02/TD{{/code}}
713 {{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH03/TD{{/code}}
714 \\{{code language="none"}}/FL1/Experiment/BL2/ADQ412 GHz ADC/CH00/TD{{/code}}
715 {{code language="none"}}/FL1/Experiment/BL2/ADQ412 GHz ADC/CH01/TD{{/code}}
716 \\{{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH02/TD{{/code}}
717 {{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}}
718
719 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD  or CH00.DAQ.TD{{/code}}
720 here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} contains only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferably.
721 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}}
722
723 In addition there are also additional parameters saved like:
724
725 * {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
726 * {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
727 * {{code language="none"}}error (ADC):{{/code}}0 indicates that there was no error
728
729 ===== MHz ADCs =====
730
731 similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
732 {{code language="none"}}/FL1/Experiment/BL1/SIS8300 100MHz ADC/CH2/TD{{/code}}
733 DOOCS prop : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02/CH00.TD
734 DAQ channel: : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02
735
736 In addition there are also additional parameters saved like:
737
738 * {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
739 * {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
740
741 [[Contents>>doc:||anchor="Contents"]]
742
743
744
745
746 === FLASH2 ===
747
748 There is analog to FLASH1 a permanently running "PhotonDagnostic DAQ FLASH2" (PBD2) and 2 User DAQs
749
750 ==== Beamline info (FLASH2) ====
751
752 {{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}
753 (% style="color:#000000" %)//always saved (PBD2)// (%%)
754 (% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
755 (% style="color:#000000" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
756 (% style="color:#000000" %)desc: set pressure in the gas attenuator (%%)
757 (% style="color:#000000" %)units: mbar(%%)
758
759
760 {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
761 //always saved (PBD2)//
762 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER/CH00.TD{{/code}}
763 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER{{/code}}
764 desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
765 units: none
766
767
768 {{code language="none"}}/FL2/Beamlines/Filter wheel/position wheel 1{{/code}}
769 //always saved (PBD2)//
770 DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS{{/code}}
771 DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS
772 desc: Position of the BL filter wheel 1 - to correlate with the filter material please look **[[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]**
773 units: degree
774
775
776 /FL2/Beamlines/Filter wheel/position wheel 2
777 always saved (PBD2)
778 DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
779 DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
780 desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
781 units: degree
782
783
784 NOTE: Aperture positions in the beamline as well as the positions of the beam steering mirrors are also saved. for more Info contact your local contact
785
786 [[Contents>>doc:||anchor="Contents"]]
787
788
789
790 ==== Photon Diagnostics SASE ([[XGMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]] - FLASH2) ====
791
792 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
793 //always saved (PBD2)//
794 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}}
795 DAQ channel:{{code language="none"}} FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ{{/code}}
796 desc : calibrated average ( ~~ 20 sec averaging time ) SASE Energy/pulse measured in the TUNNEL before the attenuator (ion current)
797 units : microJ
798
799
800 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
801 //always saved (PBD2)//
802 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
803 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
804 desc : Energy per pulse measured in the Tunnel  (in front of the gas attenuator and the apertures in the Hall) In addition measurement errors and beam position are included for EACH pulse in the pulse train  !! (see below)
805 units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision)** [[see here for help>>doc:FLASHUSER.jddd-linked help pages.Calibrating the pulse resolved (electron) data from GMD.WebHome]]**
806
807 {{info title="GMD pulse resolved data structure"}}
808 For every pulse in the pulse train the information is saved:
809
810
811 1. **Intensity per pulse** (a.u. (more or less µJ ))
812 1. Intensity per pulse (auxillary GMD) - not used
813 1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
814 1. Position vertical (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
815 1. **Intensity per pulse sigma** (a.u. (more or less µJ ), (% style="color:#000000" %)This parameter gives an indication of the error of the measurement of the pulse energy. This takes signal to noise,  detector resolution, uncertainties in crossection etc into account. (it is NOT the measurement of the statistical fluctuation of the SASE pulses)(%%))
816 1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
817 1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
818 1. Combined warning and error flags
819
820 The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this 
821 file
822
823
824 [[image:attach:image2021-2-9_10-51-6.png||height="250"]]
825
826
827 {{/info}}
828
829
830 All values for the GMD are also available for the** HALL GMD **which is located in the experimental hall down stream the gas attenuator. If the attenuator is on the ratio between Hall and Tunnel signal shows the attenuation. **BUT NOTE** that the filter unit and the Aperture 4 are downstream the GMD. So if filters and aperture are used this influence is NOT measured by the GMD hall !
831
832
833 Besides  pulse energy the GMD also provides information about the beam position
834
835
836 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel horizontal{{/code}}
837 //always saved (PBD2)//
838 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
839 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
840 desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
841 units : mm
842
843
844 {{code language="none"}}/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel vertical{{/code}}
845 //always saved (PBD2)//
846 DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
847 DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
848 desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
849 units : mm
850
851
852 /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x
853 always saved (PBD2)
854 DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TD
855 DAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2
856 desc: Besides the well calibrated averaged beam position information there is also the option to measure the beam position on a single bunch level. HOWEVER this methide needs a perfectly adjusted signal level (talk to your local contact !!) and also then the signal to noise is rather small and one needs some averaging ... BUT with this option one can determine if there was a spatial slope on a burst (say forst bunches were lower than the last ones or so ...)
857 units : mm   
858
859 (x=horizontal, y = vertial)
860
861 again the same parameter set is available for the **HALL GMD**
862
863
864
865 ==== Photon Diagnostics OPIS[[ >>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]](FLASH2) ====
866
867 for more info see:** [[ OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]]**
868
869 (The OPIS hall is not installed yet ...)
870
871
872 {{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean photon energy{{/code}}
873 // saved opon request (PBD2)//
874 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}}
875 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042{{/code}}
876 desc : mean photon energy ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
877 units : eV
878
879
880 {{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean wavelength{{/code}}
881 // saved opon request (PBD2)//
882 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
883 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
884 desc : mean wavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
885 units : nm
886
887
888 {{code language="none"}}/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/number of analyzed bunch        (in older version this can be found in OPIS tunnel/Expert stuff/General operation parameters/){{/code}}
889 // saved opon request (PBD2)//
890 DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
891 DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
892 desc : The bunch number of the bunch used for the wavelength calculation
893 units :
894
895
896 If Opis is running typically on the the averaged data is saved. For several experiments it may make sense to save the information for each single bunch. This is up to now done by saving the complete ADC trace of the TOF setup. This is a huge amount of data and needs processing. This has to be performed after the beamtime in close contact to [[Markus Braune>>mailto:markus.braune@desy.de||shape="rect"]] ( responsible for [[OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]])
897
898
899 In case OPIS was not operating there is still information about the **set wavelength** for the undulators (see below) which may differ by up to 5 % from the actual wavelength due to different settings in the FEL ...
900
901
902
903 ==== Electron Beam properties (FLASH2) ====
904
905 ===== bunch charge =====
906
907 {{code language="none"}}/FL2/Electron Diagnostic/Bunch charge/after undulator{{/code}}
908 //always saved (PBD2)//
909 DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
910 DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
911 desc: electron bunch charge FLASH2 (average value for each bunchtrain).
912 units: nC
913
914
915 ===== electron bunch energy =====
916
917 {{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}}
918 //always saved (PBD2)//
919 DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}}
920 DAQ channel: (% style="color:#5e6c84" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%)
921 desc: electron bunch energy measured behind the undulator. Data is saved with 10 Hz - BUT (for computation reasons) only the energy of the FIRST bunch is recorded. The data is also available for (% style="color:#5e6c84" %)extraction and septum  in the beginning of FLASH2
922
923 (% style="letter-spacing:0.0px" %)units: (% class="twikiNewLink" %)MeV
924
925
926 (% style="color: rgb(94, 108, 132); font-weight: 600; letter-spacing: 0px;" %)
927 ===== undulator settings =====
928
929 {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
930 //always saved (PBD2)//
931 DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
932 DAQ channel:  {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
933 desc: Set value for the anticipated wavelength . This parameter is used to set the undulator gap. It may however deviate from the actual wavelength by several % ...
934 units: nm
935
936 {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE14 gap{{/code}}
937 //always saved (PBD2)//
938 DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
939 DAQ channel:  {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
940 desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper
941 units: mm
942
943 The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall.
944
945 =====
946 arrival time (BAM) =====
947
948 {{info title="BAM information: updates 2022"}}
949 * see: [[Info collection about the BAMs and how to use the BAM data>>url:https://confluence.desy.de/display/FLASHUSER/Info+collection+for+the+BAM||shape="rect"]]
950 * The data format of the BAM has been completely altered in the 2022 shutdown
951 * before 2022 BAMs were always saving the arrival time information for each 1µs bucked regardless if there were electrons in the accelerator or not. I addition the arrival times for  FL1 and FL2 were saved in the same parameter ...
952 * THIS is now different. There are new parameters saving only the arrival times for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second)
953 * There has been also a renaming  (and relocation) of the BAMs.
954 ** acc:  4DBC3 → FL0.DBC2
955 ** FL1: 1SFELC →  FL1.SFELC
956 ** FL2: 8FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
957 * for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
958 * [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]]
959 * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
960 {{/info}}
961
962 {{expand title="Discontinued BAM format (used until end 2021)"}}
963 (% style="color:#000000" %)**Discontinued BAM data recording **
964
965 {{code language="none"}}/FL2/Electron Diagnostic/BAM/8FL2XTDS/electron bunch arrival time (low charge){{/code}}
966 //always saved (PBD2)//
967 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/8FL2XTDS/LOW_CHARGE_ARRIVAL_TIME{{/code}}
968 DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/8FL2XTDS.LOW_CHARGE_ARRIVAL_TIME{{/code}}
969 desc: Electron bunch arrival time measured with the BAM after the FLASH2 undulator (pulse resolved data)
970 units: ps (bigger numbers indicate later arrivaltime of the electrons)
971
972 **FL1**{{code language="none"}}//Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
973 //always saved (PBD2)//
974 DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
975 DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
976 desc: Electron bunch arrival time measured with the BAM  in the accelerator  (pulse resolved data)
977 units: ps (bigger numbers indicate later arrivaltime of the electrons)
978
979 {{info title="BAM hints"}}
980 * The BAM 4DBC3 measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !).
981 * The BAM 8FL2XTDS measures only for FLASH2 BUT has the same data structure as the other BAMS ... thus there are also (random) values in in the  FLASH1 time slot 
982 ** Structure: The first values are for FLASH1 bunches. After a gap of about 70 micros ( 70 colums)  with  as entry for the switching between FLASH 1 and 2 the values for the electrons used in FLASH2 start.  The start time of FLASH2 is also recorded in the DAQ. FLASH1 start time is for historic reasons 700. thus if e.g. the start time of FLASH2 ( property name see below) is 1200 it means that FLASH starts at column 500 (1200-700) ... .In case of doubt ask your local contact
983 * [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments >>doc:FLASHUSER.Additional helpful things.FLASH beamlines and instruments references.WebHome]]
984 * [[LINK to detailed infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]]
985 * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
986 {{/info}}
987 {{/expand}}
988
989
990 ====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
991
992 (% style="color:#ff6600" %)**DBC2**/electron bunch arrival time  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}
993
994 {{code language="none"}}
995 /zraw/FLASH.SDIAG/BAM.DAQ/FL0.DBC2.ARRIVAL_TIME.ABSOLUTE.SA2.COMP/dGroup/
996 {{/code}}
997
998 //always saved (PBD)//
999 **FL0.DBC2**
1000 (% style="color:#000000" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA2.COMP
1001 {{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA2.COMPDAQ {{/code}}(% style="letter-spacing:0.0px" %)desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). The property contains only the arrival time of the bunches sent to FL2 (e.g. if there are 30 bunches in FL2 the first 30 values are the arrival time the remaining numbers still may have arbitrary numbers looking like a signal which they are not0). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time  of the XUV pulses in the experiment (see help).
1002 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1003
1004
1005 (% style="color:#ff6600" %)DBC2/electron bunch arrival time (raw)  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}
1006
1007 {{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.DBC2.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/{{/code}}
1008 //always saved (PBD)//
1009 {{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE{{/code}}
1010 (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel: {{/code}}(%%)
1011 desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2). Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 2 in the second part. they may be separated by several "0" values if the reprate is different from 1 MHz ...  - It shows a very good correlation to the arrival time  of the XUV pulses in the experiment (see help). 
1012 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1013
1014
1015 (% style="color:#ff6600" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1016 //always saved (PBD)//
1017 (% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1018 (% style="color:#000000" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%)
1019 desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1020
1021
1022 (% style="color:#ff6600" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1023 //always saved (PBD)//
1024 (% style="color:#000000" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1025 (% style="color:#000000" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%)
1026 desc: status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting;  mostly check for bit 0 == 1 is sufficient
1027
1028
1029 ====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ======
1030
1031 /FL2/Electron Diagnostic/BAM/**SEED5**(% style="color:#ff6600" %)/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)
1032
1033 (% style="color:#000000" %){{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2.COMP/dGroup/{{/code}}
1034
1035 //always saved (PBD)//
1036 (% style="color:#172b4d" %)**FL2.SEED5**(%%)
1037 (% style="color:#000000" %)channel: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
1038 {{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ {{/code}}(%%)desc: Electron bunch arrival time measured  with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020.. The property contains only the arrival time of the bunches sent to FL2 (e.g. if there are 30 bunches in FL2 the first 30 values are the arrival time the remaining numbers still may have arbitrary numbers looking like a signal which they are not). These are the same values as the "raw" data below - just "cleaned". The values show a very good correlation to the arrival time  of the XUV pulses in the experiment (see help).
1039 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1040
1041
1042
1043 (% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}
1044
1045 (% style="color:#000000" %){{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/{{/code}}(%%)
1046 //always saved (PBD)//
1047 (% style="color:#172b4d" %)**FL2.SEED5**{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE{{/code}}(%%)
1048 **~ **(% style="color:#000000" %)FLASH.SDIAG/BAM/(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel:{{/code}}(%%)
1049 desc: Electron bunch arrival time measured  with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020. Here the complete bunch train from the FEL is recorded (FLASH1 and FLASH2 pulses). Thus there are values from FLASH 2 in the second part. they may be separated by several "0" values if the reprate is different from 1 MHz ...  - It shows a very good correlation to the arrival time  of the XUV pulses in the experiment (see help). 
1050 units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1051
1052
1053 (% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1054 //always saved (PBD)//
1055 (% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1056 (% style="color:#000000" %): FLASH.SDIAG/BAM/(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel{{/code}}(%%)
1057 desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1058
1059
1060 (% style="color:#172b4d" %)SEED5(% style="color:#ff6600" %)/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1061 //always saved (PBD)//
1062 (% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)E.bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1063 (% style="color:#000000" %)el: FLASH.SDIAG/BAM/(% style="color:#172b4d" %)**FL2.SEED5**(% style="color:#000000" %)/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ chann{{/code}}(%%)
1064 desc: status bit: 0 - data is valid; 1 - beam present; 2 - calibration ongoing; 3 - feedback enabled; 4 - feedback acting;  mostly check for bit 0 == 1 is sufficient
1065
1066
1067 [[Contents>>doc:||anchor="Contents"]]
1068
1069
1070 ==== Timing information, rep rate etc.  (FLASH2) ====
1071
1072 ===== start time of FLASH2 =====
1073
1074 {{code language="none"}}/FL2/Timing/start time flash2{{/code}}
1075 //always saved (PBD2)//
1076 DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
1077 DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
1078 desc: The max 600 µs acceleration time of FLASH is devided between FLASH1 and FLASH2. This 600 µs window starts with FLASH1 (up to now)  at a time"label" of 700 µs (for historic reasons). Thus the first bunch of FLASH 1 comes at "700" and the last possibel bunch comes at 1300 (700+600). After FLASH1 train is over ther is a about 70µs switching time with no bunches. Then comes the first FLASH2 bunch.  Thus if e.g. the start time of FLASH2 is 1200 it means that FLASH2 starts at column 500 (1200-700)  in the HDF5 files. (However for yet unknown reasons this may change by 2-3 colums ...)
1079 units: µs
1080
1081 ===== bunch repetition rate =====
1082
1083 {{code language="none"}}/FL2/Timing/repetition rate{{/code}}
1084 //always saved (PBD2)//
1085 DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
1086 DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
1087 desc: repetition rate of the bunches / pulses within the burst (FLASH2)
1088 units: kHz
1089
1090
1091 ===== set number of pulses =====
1092
1093 (% style="color:#ff6600" %)(HDF5 name not yet implemented - see zraw)(% style="color:#ff0000" %){{code language="none"}}/FL2/Timing/set number of bunches {{/code}}(%%)
1094 //always saved (PBD2)//
1095 DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]{{/code}}
1096 DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]{{/code}}
1097 desc: Number of bunches set in the control (timing) system.  The property contains 4 numbers. the last one is the number of pulses (see also [[doc:FLASH.Timing properties]] (internal link)).  If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated and thus the actual number of pulses may be smaller than the set one 
1098 units:
1099
1100 ===== actual number of pulses =====
1101
1102 {{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
1103 //always saved (PBD2)//
1104 DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
1105 DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
1106 desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH2)
1107 units:
1108
1109
1110 ===== actual pulse pattern recorded after the undulator =====
1111
1112 {{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
1113 //always saved (PBD2)//
1114 DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
1115 DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
1116 desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
1117 units:
1118
1119
1120 ===== Train ID =====
1121
1122 {{code language="none"}}/Timing/train ID{{/code}}
1123 //always saved (PBD2)//
1124 DOOCS prop : {{code language="none"}}none{{/code}}
1125 DAQ channel: {{code language="none"}}none{{/code}}
1126 desc: Each 10 Hz burst has its unique train ID. For the HDF5 dataset the ID is the same for all parameters with the same index (note camera images may be shifted by 1 ID - talk to the experts !)
1127 units:
1128
1129
1130 ===== Train time =====
1131
1132 //always saved (PBD2)//
1133 {{code language="none"}}/Timing/train time{{/code}}
1134 desc:Local time as array of day, hour, minute, second, and centisecond. This dataset is meant for visualisation purposes only. For correlations use the train ID or the Unix time of the time stamp
1135 units: d h min s cs
1136
1137
1138 {{code language="none"}}
1139 /Timing/time stamp
1140 {{/code}}
1141
1142 //always saved (PBD2)//
1143 desc: first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date ~-~-date='@1553617729' or matlab, python etc
1144 second column: microseconds
1145 third column: Train ID of FLASH
1146
1147
1148 [[Contents>>doc:||anchor="Contents"]]
1149
1150
1151 ==== User Data (FLASH2) ====
1152
1153 The data saved specifically for detectors at an experiment will show up in /Experiment/ there is a large number of options for cameras or monitoring pslow properties (motor positons etc) for user experiments. For details please ask your local contact.
1154
1155 NOTE: If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with the DOOCS names
1156
1157 The most common and permanently installed device used by experiment are our ADCs:
1158
1159 ===== GHz ADCs =====
1160
1161 ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found** [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]**
1162 //saved on DEMAND in the user DAQ//
1163 \\Up to now there are 4 channels available at FL24
1164 \\\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD{{/code}}
1165 {{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH01/TD{{/code}}
1166 \\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH02/TD{{/code}}{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH03/TD{{/code}}
1167
1168
1169 DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00/CH00.TD  or CH00.DAQ.TD{{/code}}
1170 here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} conatins only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferablly.
1171 DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00{{/code}}
1172
1173 In addition there are also additional parameters saved like:
1174
1175 * {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
1176 * {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
1177 * {{code language="none"}}error (ADC):{{/code}}0 indicates that there was no error
1178 * {{code language="none"}}/CH0-CH3/offset{{/code}}: To use the full dynamic range of the ADC one can shift the base line . This offset is saved here.
1179
1180 ===== MHz ADCs =====
1181
1182 similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
1183 {{code language="none"}}/FL2/Experiment/MTCA-EXP1/SIS8300 100MHz ADC/CH2/TD{{/code}}
1184 DOOCS prop : FLASH.FEL/ADC.SIS.FL2EXP1/FL2EXP1.CH02/CH00.TD
1185 DAQ channel: : FLASH.FEL/ADC.SIS.FL2EXP1/FL2EXP1.CH02
1186
1187 In addition there are also additional parameters saved like:
1188
1189 * {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
1190 * {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
1191
1192 [[Contents>>doc:||anchor="Contents"]]
1193
1194
1195
1196 ==== FL 24 Pump Probe Laser (FLASH2) ====
1197
1198 {{info width="30%"}}
1199 list of saved parameters status May 2024 (up to now the parameters can be found in /zraw/ ... )
1200
1201 [[attach:FSLADAQ-DAQParameterlistULGAN-2.pdf||target="_blank"]]
1202
1203 [[attach:FSLADAQ-DAQParameterlistFL23-2.pdf||target="_blank"]]
1204
1205 [[attach:FSLADAQ-DAQParameterlistFL24-2.pdf||target="_blank"]]
1206
1207
1208 {{view-file att--filename="FSLADAQ-DAQParameterlistFL23-2.pdf"}}{{/view-file}}
1209
1210
1211 {{/info}}
1212
1213
1214 These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**//
1215
1216 **User delay**
1217
1218 Delay (set value):
1219
1220 {{code language="none"}}
1221 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR
1222 {{/code}}
1223
1224 Delay (readback):
1225
1226 {{code language="none"}}
1227 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD
1228 {{/code}}
1229
1230 (% style="letter-spacing:0.0px" %)Delay (encoder readback):
1231
1232 {{code language="none"}}
1233 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.ENCODER_POSITION.RD
1234 {{/code}}
1235
1236 OXC. jitter:
1237
1238 {{code language="none"}}
1239 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD
1240 {{/code}}
1241
1242
1243
1244 **FL24 Pulse resolved energy:**
1245
1246 OPCPA output (photodiode signal raw ADC trace 16000 samples):
1247
1248 {{code language="none"}}
1249 /zraw/FLASH.LASER/FLASH2CPUULGAN1.ADCSCOPE/CH23.TD/dGroup
1250 {{/code}}
1251
1252 (% style="letter-spacing:0.0px" %)Upper breadboard Photodiode (THG) burst (photodiode signal raw ADC trace 16000 samples)::
1253
1254 {{code language="none"}}
1255 /zraw/FLASH.LASER/FLASH2CPUULGAN1.ADCSCOPE/CH26.TD/dGroup
1256 {{/code}}
1257
1258 Upper breadboard Photodiode (THG) energy (analyzed signal. integration over pulses in the ADC trace. contains for each laser pulse the pulse energy in a.u.)
1259
1260 {{code language="none"}}
1261 /zraw/FLASH.LASER/MOD24.PES/FL24_userPD/dGroup
1262 {{/code}}
1263
1264
1265 **FL24 LAM (Laser Arrivaltime Monitor)  pulse resolved data:**
1266
1267 Signal of Photodiode1  - for experts only... (analyzed signal. integration over pulses in the ADC trace. )
1268
1269 {{code language="none"}}
1270 /zraw/FLASH.LASER/MOD24.PES/LAM.PD1/dGroup
1271 {{/code}}
1272
1273 Signal of Photodiode2  - for experts only...  (analyzed signal. integration over pulses in the ADC trace.)
1274
1275 {{code language="none"}}
1276 /zraw/FLASH.LASER/MOD24.PES/LAM.PD2/dGroup
1277 {{/code}}
1278
1279 "Actual" LAM Signal - to be calibrated ......  (analyzed signal. integration over pulses in the ADC trace.)
1280
1281 {{code language="none"}}
1282 /zraw/FLASH.LASER/MOD24.PES/LAM.PDBAL/dGroup
1283 {{/code}}
1284
1285 The delay feedback(% style="letter-spacing:0.0px" %)
1286
1287 {{code language="none"}}
1288 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26 
1289 {{/code}}
1290
1291 The LAM delay feedback(% style="letter-spacing:0.0px" %) (the pulse energy signal, which is saved in the above but maybe it’s good to have this also as slow, in the case these two numbers are not the same the sysdc was active instead of the LAM):
1292
1293 {{code language="none"}}
1294 FLASH.LASER/MOD24.PES/LAM.PDBAL/PULSEENERGY.MEAN
1295 {{/code}}
1296
1297 LAM Delay line act:
1298
1299 {{code language="none"}}FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.POSITION.RD{{/code}}
1300 LAM Delay line set:
1301
1302 {{code language="none"}}
1303 FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.POSITION_SET.WR
1304 {{/code}}
1305
1306 LAM Delay line encoder:
1307
1308 {{code language="none"}}
1309 FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.ENCODER_POSITION.RD
1310 {{/code}}
1311
1312 Temperature feedback:
1313
1314 {{code language="none"}}
1315 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE24
1316 {{/code}}
1317
1318 **Feedback mode** (if this is not =1 the delay FB is not active, then it’s either temp feedback controlled or failsave, maybe it’s good to have):
1319
1320 {{code language="none"}}
1321 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.INTS/INTEGER30
1322 {{/code}}
1323
1324
1325 **FL24 Attenuator angle:**
1326
1327 {{code language="none"}}
1328 FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS
1329 {{/code}}
1330
1331 **FL24 Polarization control:**
1332
1333 {{code language="none"}}
1334 FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL24/FPOS
1335 {{/code}}
1336
1337 **SysDC delay error:**
1338
1339 {{code language="none"}}
1340 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
1341 {{/code}}
1342
1343
1344 **Timing error: (these two need to be observed and both=0 means no error)**
1345
1346 {{code language="none"}}
1347 FLASH/CPUULGAN1.TIMING/ULGAN1/dT_alarm
1348 {{/code}}
1349
1350 {{code language="none"}}
1351 FLASH/CPUULGAN1.TIMING/ULGAN1/dMPN
1352 {{/code}}
1353
1354 **Laser error status:**
1355
1356
1357 **FL24 Virtual camera X and Y history, beam size: (use slow data)**
1358
1359 {{code language="none"}}
1360 FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.X
1361 {{/code}}
1362
1363 {{code language="none"}}
1364 FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.Y
1365 {{/code}}
1366
1367 {{code language="none"}}
1368 FLASH.LASER/MOD24.CAM/UV.14.VF/ROI_SPECTRUM.X.SIG
1369 {{/code}}
1370
1371 {{expand title="Parameters used until 2021"}}
1372 //{{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/attenuator position{{/code}}always saved (PBD2)//
1373 DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
1374 DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
1375 desc: attenuation of the PPLaser in the FL24 hutch (rotation of a waveplate)
1376 units : deg.
1377
1378
1379
1380 //{{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/polarization position{{/code}}always saved (PBD2)//
1381 DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR2.FL24/FPOS{{/code}}
1382 DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR2.FL24/FPOS{{/code}}
1383 desc: attenuation of the PPLaser in the FL24 hutch (rotation of a waveplate)
1384 units : deg.
1385
1386
1387 {{code language="none"}}/FL1/Experiment/Pump probe laser/laser delay readback{{/code}}
1388 //always saved (PBD2)//
1389 DOOCS prop : {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION.RD{{/code}}
1390 DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION.RD{{/code}}
1391 desc: delay of the Pump probe laser - measured by the read back position of the motor. There is also the set value available ( upto now these values are only updating every 1-2 seconds. There is no fast encoder property as on FLASH1 available)
1392 units : ps )
1393
1394
1395 {{code language="none"}}/FL1/Experiment/Pump probe laser/Synchronization/timing jitter RMS{{/code}}
1396 //always saved (PBD)//
1397 DOOCS prop : {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}}
1398 DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}}
1399 desc: rms jitter of the fs-Oscillator
1400 units: fs
1401 {{/expand}}
1402
1403
1404 ==== FL 26 Pump Probe Laser (FLASH2) ====
1405
1406 These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL26**//
1407
1408
1409 **User delay**
1410
1411 Delay (set value):
1412
1413 {{code language="none"}}
1414 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR
1415 {{/code}}
1416
1417 Delay (readback):
1418
1419 {{code language="none"}}
1420 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD
1421 {{/code}}
1422
1423 Delay (encoder readback):
1424
1425 {{code language="none"}}
1426 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.ENCODER_POSITION.RD
1427 {{/code}}
1428
1429 OXC. jitter:
1430
1431 {{code language="none"}}
1432 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD
1433 {{/code}}
1434
1435
1436 **Parameters for FL26**
1437
1438 (% class="wrapped" %)
1439 |(((
1440 FL2PPL FL26 REMI Attenuation: HWP motor current position
1441 )))|(((
1442 FLASH.FEL/FLAPP2BEAMLINES/MOTOR11.FL26B/FPOS
1443 )))
1444 |(((
1445 FL2PPL FL26 REMI Polarization: linear polarization angle
1446 )))|(((
1447 FLASH.FEL/FLAPP2BEAMLINES/MOTOR12.FL26B/FPOS
1448 )))
1449 |(((
1450 FL2PPL FL26 REMI Diagnostics: NIR spectrum
1451 )))|(((
1452 FLASH.LASER/MOD26.SPECT/REMI/DAQ_CHANNEL
1453 )))
1454 |(((
1455 FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - pulse energy mean
1456 )))|(((
1457 FLASH.LASER/MOD26.PES/RE_OUT/PULSEENERGY.MEAN
1458 )))
1459 |(((
1460 FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - intra burst pulse energy
1461 )))|(((
1462 FLASH.LASER/MOD26.PES/RE_OUT/DAQ_CHANNEL
1463 )))
1464 |(((
1465 FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - raw adc
1466 )))|(((
1467 FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH04.TD
1468 )))
1469 |(((
1470 FL2PPL FL26 REMI Diagnostics: photo diode input REMI - pulse energy mean
1471 )))|(((
1472 FLASH.LASER/MOD26.PES/INC_BOX/PULSEENERGY.MEAN
1473 )))
1474 |(((
1475 FL2PPL FL26 REMI Diagnostics: photo diode input REMI - intra burst pulse energy
1476 )))|(((
1477 FLASH.LASER/MOD26.PES/INC_BOX/DAQ_CHANNEL
1478 )))
1479 |(((
1480 FL2PPL FL26 REMI Diagnostics: photo diode input REMI - raw adc
1481 )))|(((
1482 FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH05.TD
1483 )))
1484 |(((
1485 FL2PPL FL26 REMI In coupling: filter wheel 1 position
1486 )))|(((
1487 FLASH/MOD26.FW1/FLASH2MOD26/pos
1488 )))
1489 |(((
1490 FL2PPL FL26 REMI In coupling: filter wheel 2 position
1491 )))|(((
1492 FLASH/MOD26.FW2/FLASH2MOD26/pos
1493 )))
1494 |(((
1495 FL2PPL FL26 REMI: Energy meter REMI incoupling breadboard
1496 )))|(((
1497 FLASH.LASER/MOD26.OPHIRE/REINC.54/DAQ_CHANNEL
1498 )))
1499 |(((
1500 FL2PPL FL26 REMI Incoupling: focusing lens position
1501 )))|(((
1502 FLASH.FEL/FLAPP2BEAMLINES/MOTOR3.FL26B/FPOS
1503 )))
1504 |(((
1505 FL2PPL FL26 REMI Incoupling: nearfield
1506 )))|(((
1507 FLASH.LASER/MOD26.CAM/REINC.21.NF/DAQ_CHANNEL
1508 )))
1509 |(((
1510 FL2PPL FL26 REMI Incoupling: focus
1511 )))|(((
1512 FLASH.LASER/MOD26.CAM/REINC.22.FF/DAQ_CHANNEL
1513 )))
1514 |(((
1515 FL2PPL FL26 REMI Drift: relative arrival time intra burst LAM balanced - calb. in the PES
1516 )))|(((
1517 FLASH.LASER/MOD26.PES/LAM_DIFF/DAQ_CHANNEL
1518 )))
1519 |(((
1520 FL2PPL FL26 REMI Drift: forward signal (PD1)  raw
1521 )))|(((
1522 FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH00.TD
1523 )))
1524 |(((
1525 FL2PPL FL26 REMI Drift: backward signal (PD2) raw
1526 )))|(((
1527 FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH01.TD
1528 )))
1529 |(((
1530 FL2PPL FL26 REMI Drift: mean relative burst arrival time - avarage of the calib value
1531 )))|(((
1532 FLASH.LASER/MOD26.PES/LAM_DIFF/PULSEENERGY.MEAN
1533 )))
1534 |(((
1535 FL2PPL FL26 REMI Drift: delay line position (ODL of the LAM REMI)
1536 )))|(((
1537 FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL26B/FPOS
1538 )))
1539 |(((
1540 FL2PPL FL26 Laser Hutch: delay line position (ODL of the osc. Sync / user delay)
1541 )))|(((
1542 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD
1543 )))
1544 |(((
1545 FL2PPL FL26 REMI Drift: delay line encoder position (ODL REMI raw value)
1546 )))|(((
1547 FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.0.ENCODER_POSITION.RD
1548 )))
1549 |(((
1550 Jiiter between oscillator and MLO (inloop jitter osc. Sync)
1551 )))|(((
1552 FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD
1553 )))
1554 |(((
1555 Temperature controlled fiber (PWM signal to the temperature controlled fiber delay sysdc)
1556 )))|(((
1557 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE23
1558 )))
1559 |(((
1560 Temperature controlled fiber (Temp of the fiber delay sysdc)
1561 )))|(((
1562 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE24
1563 )))
1564 |(((
1565 Sydc feedback data if LAM is not activated (sysdc delay)
1566 )))|(((
1567 FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
1568 )))
1569
1570 [[Contents>>doc:||anchor="Contents"]]
1571
1572
1573 === "/uncategorized/" ===
1574
1575 If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with their DOOCS names
1576
1577
1578 === HDF5 structure revisions ===
1579
1580 Starting with Beamblock 4, August 2018, the hierarchy of the HDF group names have been adapted to reflect the new situation at FLASH. FLASH2 is operating for users quite some time now. Therefore, both accelerators appear equally in their respective HDF groups, namely "/FL1" and "/FL2". The root group of proper, by run organised HDF files have an attribute called "version". This version attribute has changed from "0.2.x" to "0.3.x". The changes in detail:
1581
1582
1583 * All FLASH1 related HDF groups moved to group "/FL1", i.e. a new prefix "/FL1" is added to their HDF path.
1584 * The ambigious term "pulse" has been replaced by "train" to refer to "pulse train". Most notably, the dataset "/Timing/pulse ID" has changed to "/Timing/train ID".
1585 * A number of inconsistent names have been streamlined. The relevant changes are listed in the following table.
1586
1587 (% class="wrapped" %)
1588 |=(((
1589 earlier HDF path (vers. 0.2)
1590 )))|=(((
1591 is now (vers. 0.3)
1592 )))
1593 |(((
1594 /Photon Diagnostic/GMD/Beam position/position BDA x
1595 )))|(((
1596 /FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal
1597 )))
1598 |(((
1599 /Photon Diagnostic/GMD/Beam position/position BDA y
1600 )))|(((
1601 /FL1/Photon Diagnostic/GMD/Beam position/position BDA vertical
1602 )))
1603 |(((
1604 /Photon Diagnostic/GMD/Beam position/position tunnel x
1605 )))|(((
1606 /FL1/Photon Diagnostic/GMD/Beam position/position tunnel horizontal
1607 )))
1608 |(((
1609 /Photon Diagnostic/GMD/Beam position/position tunnel y
1610 )))|(((
1611 /FL1/Photon Diagnostic/GMD/Beam position/position tunnel vertical
1612 )))
1613 |(((
1614 /Experiment/Pump probe laser/BPM/position x
1615 )))|(((
1616 /FL1/Experiment/Pump probe laser/BPM/position horizontal
1617 )))
1618 |(((
1619 /Experiment/Pump probe laser/BPM/position y
1620 )))|(((
1621 /FL1/Experiment/Pump probe laser/BPM/position vertical
1622 )))
1623 |(((
1624 /FL2/Photon Diagnostic/GMD/Beam position/Average/position hall horizontal
1625 )))|(((
1626 /FL2/Photon Diagnostic/GMD/Average beam position/position hall horizontal
1627 )))
1628 |(((
1629 /FL2/Photon Diagnostic/GMD/Beam position/Average/position hall vertical
1630 )))|(((
1631 /FL2/Photon Diagnostic/GMD/Average beam position/position hall vertical
1632 )))
1633 |(((
1634 /FL2/Photon Diagnostic/GMD/Beam position/Average/position tunnel horizontal
1635 )))|(((
1636 /FL2/Photon Diagnostic/GMD/Average beam position/position tunnel horizontal
1637 )))
1638 |(((
1639 /FL2/Photon Diagnostic/GMD/Beam position/Average/position tunnel vertical
1640 )))|(((
1641 /FL2/Photon Diagnostic/GMD/Average beam position/position tunnel vertical
1642 )))
1643 |(((
1644 /FL2/Photon Diagnostic/GMD/Average energy/hall
1645 )))|(((
1646 /FL2/Photon Diagnostic/GMD/Average energy/energy hall
1647 )))
1648 |(((
1649 /FL2/Photon Diagnostic/GMD/Average energy/hall (raw)
1650 )))|(((
1651 /FL2/Photon Diagnostic/GMD/Average energy/energy hall (raw)
1652 )))
1653 |(((
1654 /FL2/Photon Diagnostic/GMD/Average energy/tunnel
1655 )))|(((
1656 /FL2/Photon Diagnostic/GMD/Average energy/energy tunnel
1657 )))
1658 |(((
1659 /FL2/Photon Diagnostic/GMD/Average energy/tunnel (raw)
1660 )))|(((
1661 /FL2/Photon Diagnostic/GMD/Average energy/energy tunnel (raw)
1662 )))
1663 |(((
1664 /FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/hall x
1665 )))|(((
1666 /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall horizontal
1667 )))
1668 |(((
1669 /FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/hall y
1670 )))|(((
1671 /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall vertical
1672 )))
1673 |(((
1674 /FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/tunnel x
1675 )))|(((
1676 /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel horizontal
1677 )))
1678 |(((
1679 /FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/tunnel y
1680 )))|(((
1681 /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel vertical
1682 )))
1683
1684 [[Contents>>doc:||anchor="Contents"]]
1685
1686
1687 {{/layout-cell}}
1688 {{/layout-section}}
1689 {{/layout}}