Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/02/06 10:55
From version 68.1
edited by sndueste
on 2023/01/26 15:17
Change comment: There is no comment for this version
To version 29.1
edited by sndueste
on 2019/10/22 10:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +4,3 @@
1 -{{layout}}
2 -{{layout-section ac:type="single"}}
3 -{{layout-cell}}
4 4  == Contents ==
5 5  
6 6  
... ... @@ -11,46 +11,35 @@
11 11  
12 12  == General information about HDF5 ==
13 13  
14 -HDF5 is a data format maintained by the HDF group. For detailed general information see [[here~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://portal.hdfgroup.org/display/support||shape="rect"]]
11 +HDF5 is a data format maintained by the HDF group. For detailed general information see [[here~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://www.hdfgroup.org/HDF5/||shape="rect"]]
15 15  
16 -To download the HDF5 Viewer click [[here~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://portal.hdfgroup.org/display/support/Download+HDFView||shape="rect"]]
13 +To download the HDF5 Viewer click [[here~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://support.hdfgroup.org/products/java/hdfview/index.html||shape="rect"]]
17 17  
18 18  For use on the DESY Maxwell or PAL (max-fsc or pal) **hdfview** is available in the xray module :
19 19  {{code language="none"}}> module load xray{{/code}}
20 20  {{code language="none"}}> hdfview{{/code}}
21 21  
22 -or you can use
23 -
24 -{{code language="none"}}> silx view{{/code}}
25 -
26 -\\
27 -
28 28  [[Contents>>doc:||anchor="Contents"]]
29 29  
30 -== The FLASH HDF5 format ==
21 +== FLASH HDF5 structure ==
31 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.
23 +The photon diagnostic, electron diagnostic and beamline information as well as the information about the pump-probe laser and the infrastructure offered for users (GHz/MHz ADCs) can be included in one HDF5 file which is organised according to train IDs. The general structure is:
33 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.
25 +* Electron Diagnostic
26 +* Photon Diagnostics
27 +* Beamlines
28 +* Experiment
29 +* Timing
30 +[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/HDF5main/HDF5_structure.jpg~|~|alt="HDF5_structure.jpg" width="700" height="500"~]~]>>attach:HDF5_structure.jpg]]
35 35  
36 -Reference implementation, which follows the concept of Python libraries like Pandas, Xarray, or Dask, is given below.
32 +A detailled description of (most) channels can be found in the lower part of the hdf5 viewer:
33 +[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/HDF5main/HDF5_structure_desc.jpg~|~|alt="HDF5_structure_desc.jpg" width="341" height="413"~]~]>>attach:HDF5_structure_desc.jpg]]
37 37  
38 -\\
35 +[[Contents>>doc:||anchor="Contents"]]
39 39  
40 -{{expand title="Discontinued HDF formats"}}
41 -=== Comparison to FLASH's deprecated HDF formats ===
42 -
43 -Before 2021, FLASH provided two different HDF formats formally known as //near-online// and //offline// HDF files.
44 -
45 -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.
46 -
47 -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.
48 -
49 -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.
50 -
51 51  \\
52 52  
53 -**HDF5 example files (old format)**
39 +== HDF5 example files ==
54 54  
55 55  Here we have a few HDF5 samples (User data combined with Photon diagnostics data) from a few beamtimes showing the different kind options.
56 56  
... ... @@ -63,69 +63,18 @@
63 63  \\
64 64  
65 65  \\
66 -{{/expand}}
67 67  
68 -=== HDF examples: ===
69 -{{/layout-cell}}
70 -{{/layout-section}}
53 +[[Contents>>doc:||anchor="Contents"]]
71 71  
72 -{{layout-section ac:type="three_equal"}}
73 -{{layout-cell}}
74 -* ADC data as example for **fast** **data** (10 Hz):           
75 -
76 76  \\
77 77  
78 -[[image:attach:image2020-11-16_15-26-28.png||height="250"]]
79 -{{/layout-cell}}
80 -
81 -{{layout-cell}}
82 -* The //average// FEL pulse energy as example for the **slow** **data** (different e.g. 1 Hz):
83 -
84 - ( every 10th train ID is listed in the HDF group "index")
85 -
86 86  \\
87 87  
88 -[[image:attach:image2020-11-16_15-31-45.png||height="250"]]
89 -{{/layout-cell}}
59 +== Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
90 90  
91 -{{layout-cell}}
92 -* (((
93 -//zraw// group contains the **original DAQ (DOOCS) names**
94 -)))
61 +The complete list for the relation between DOOCS names and HDF5 names for the recordable parameters can be found in [[DESY's Repository~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat||shape="rect"]].
62 +The most common and often used ones are summarized below:
95 95  
96 - of the properties saved in the DESY internal raw format. (For experts)
97 -
98 -\\
99 -
100 -[[image:attach:image2020-11-16_16-26-3.png||height="400"]]
101 -{{/layout-cell}}
102 -{{/layout-section}}
103 -
104 -{{layout-section ac:type="single"}}
105 -{{layout-cell}}
106 -{{info}}
107 -=== Reference implementation (Python) ===
108 -
109 -(imperative)  (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]]
110 -
111 -(% class="Object" %)(object oriented) [[https:~~/~~/gitlab.desy.de/christopher.passow/fdh-builder>>url:https://gitlab.desy.de/christopher.passow/fdh-builder.git||shape="rect"]]
112 -{{/info}}
113 -{{/layout-cell}}
114 -{{/layout-section}}
115 -
116 -{{layout-section ac:type="single"}}
117 -{{layout-cell}}
118 -
119 -
120 -== Complete list of recordable parameters ==
121 -
122 -The complete list for the relation between DOOCS names and HDF5 names for the recordable parameters can be found in [[DESY's Repository~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat||shape="rect"]].
123 -\\
124 -
125 -== Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
126 -
127 -{{id name="DOOCSparameters"/}}
128 -
129 129  Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
130 130  
131 131  \\
... ... @@ -132,6 +132,8 @@
132 132  
133 133  === FLASH1 ===
134 134  
70 +\\
71 +
135 135  ==== Beamline info (FLASH1) ====
136 136  
137 137  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
... ... @@ -200,28 +200,23 @@
200 200  \\
201 201  
202 202  
203 -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
140 +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
204 204  
205 205  [[Contents>>doc:||anchor="Contents"]]
206 206  
207 207  \\
208 208  
209 -==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]]) ====
146 +==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]]) / Spectrometer (FLASH1) ====
210 210  
211 -{{expand title="Discontinued GMD format (used until 2021)"}}
212 -(% style="color: rgb(0,0,0);" %)**Discontinued GMD data recording / evaluation  (VME + PhotonFlux ML server)**
213 -
214 214  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
215 -//always saved (PBD)//
216 -
217 -(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT04/VAL{{/code}} (%%)
218 -(% style="color: rgb(0,0,0);" %)DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENPULSEIC{{/code}}(%%)
219 -desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator (ion current)
149 +//always saved (PBD)//
150 +DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT04/VAL{{/code}}
151 +DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENPULSEIC{{/code}}
152 +desc : calibrated average SASE Energy/pulse measured in the TUNNEL before the attenuator (ion current)
220 220  units : microJ
221 221  
222 222  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
223 -//always saved (PBD)//
224 -
156 +//always saved (PBD)//
225 225  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
226 226  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
227 227  desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
... ... @@ -235,8 +235,7 @@
235 235  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]]**
236 236  
237 237  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
238 -//always saved (PBD)//
239 -
170 +//always saved (PBD)//
240 240  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT05/VAL{{/code}}
241 241  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENPULSEIC{{/code}}
242 242  desc : calibrated average SASE Energy/pulse measured in the BDA (in the experimental hall) after the attenuator (ion current)
... ... @@ -243,8 +243,7 @@
243 243  units : microJ
244 244  
245 245  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA{{/code}}
246 -//always saved (PBD)//
247 -
177 +//always saved (PBD)//
248 248  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
249 249  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
250 250  desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
... ... @@ -256,59 +256,7 @@
256 256  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
257 257  desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
258 258  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]]**
259 -{{/expand}}
260 260  
261 -\\
262 -
263 -(% style="letter-spacing: 0px; color: rgb(0, 0, 0)" %)**NEW (since 2021) GMD data recording / evaluation  (same format as FLASH2 and XFEL)**
264 -
265 -{{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
266 -//always saved (PBD)//
267 -(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)
268 -(% style="color: rgb(0,0,0);" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}
269 -
270 -desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator
271 -units : microJ
272 -
273 -\\
274 -
275 -{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
276 -//always saved (PBD)//
277 -
278 -(% style="color: rgb(0,0,0);" %)DOOCS prop : 
279 -{{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}}
280 -
281 -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)
282 -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]]**
283 -
284 -{{info title="GMD pulse resolved data structure"}}
285 -For every pulse in the pulse train the information is saved:
286 -
287 -
288 -1. **Intensity per pulse** (a.u. (more or less µJ ))
289 -1. Intensity per pulse (auxillary GMD) - not used
290 -1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
291 -1. Position vertical (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
292 -1. **Intensity per pulse sigma** (a.u. (more or less µJ ), (% style="color: rgb(0,0,0);" %)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)(%%))
293 -1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
294 -1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
295 -1. Combined warning and error flags
296 -
297 -The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this 
298 -file
299 -
300 -
301 -[[image:attach:image2021-2-9_10-51-6.png||height="250"]]
302 -
303 -\\
304 -{{/info}}
305 -
306 -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 !
307 -
308 -\\
309 -
310 -Besides  pulse energy the GMD also provides information about the beam position
311 -
312 312  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal{{/code}}
313 313  //always saved (PBD)//
314 314  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
... ... @@ -337,10 +337,6 @@
337 337  desc :Beam position of the photon Beam determined by the GMD (TUNNEL, y=vertical)
338 338  units : mm
339 339  
340 -\\
341 -
342 -==== Spectrometer (FLASH1) ====
343 -
344 344  {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength{{/code}}
345 345  _always saved (when Spectrum is measured !!) (PBD) _
346 346  DOOCS prop : {{code language="none"}}TTF2.EXP/PHOTONWL.ML/WAVE_LENGTH/VAL.TD{{/code}}
... ... @@ -418,122 +418,16 @@
418 418  units: nC
419 419  
420 420  =====
421 -arrival time (BAM) =====
295 +arrival time =====
422 422  
423 -{{info title="BAM information: updates 2022"}}
424 -* 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"]]
425 -* The data format of the BAM has been completely altered in the 2022 shutdown
426 -* 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 ...
427 -* 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)
428 -* There has been also a renaming  (and relocation) of the BAMs.
429 -** acc:  4DBC3 → FL0.DBC2
430 -** FL1: 1SFELC →  FL1.SFELC
431 -** FL2: FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5
432 -* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
433 -* [[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]]
434 -* a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
435 -{{/info}}
436 -
437 -\\
438 -
439 -{{expand title="Discontinued BAM format (used until end 2021)"}}
440 -(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording **
441 -
442 442  {{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
443 443  //always saved (PBD)//
444 444  DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
445 445  DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
446 -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).
447 -units: ps (bigger numbers indicate later arrivaltime of the electrons)
301 +desc: Electron bunch arrival time measured with the BAM (more or less) before the undulator (pulse resolved data)
302 +units: ps (bigger numbers indicate later arrivaltime of the electrons)
303 +note: besides the arivaltime from FLASH1 there is also the FLASH2/3 electron arrival time saved. [[LINK to detailled infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]] and to a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
448 448  
449 -\\
450 -
451 -{{code language="none"}}/FL1/Electron Diagnostic/BAM/1SFELC/electron bunch arrival time (low charge){{/code}}
452 -//always saved (PBD)//
453 -DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/1SFELC/LOW_CHARGE_ARRIVAL_TIME{{/code}}
454 -DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/1SFELC.LOW_CHARGE_ARRIVAL_TIME{{/code}}
455 -desc: Electron bunch arrival time measured with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020.
456 -units: ps (bigger numbers indicate later arrival time of the electrons)
457 -{{/expand}}
458 -
459 -====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
460 -
461 -(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)(%%)
462 -//always saved (PBD)//
463 -**FL0.DBC2**
464 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA1.COMP (%%)
465 -{{code language="none"}}/FL1/Electron Diagnostic/BAM/ DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ 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 should be only 0). These are the same values as the "raw" data below - just "cleaned". The values{{/code}}(% style="font-family: SFMono-Medium , ~"SF Mono~" , ~"Segoe UI Mono~" , ~"Roboto Mono~" , ~"Ubuntu Mono~" , Menlo , Courier , monospace;letter-spacing: 0.0px;" %) show a very good correlation to the arrival time  of the XUV pulses in the experiment (see help).
466 -
467 -{{code language="none"}}units: fs (bigger numbers (typically) indicate later arrival times of the electrons).{{/code}}
468 -
469 -\\
470 -
471 -(% style="color: rgb(255,102,0);" %)DBC2/electron bunch arrival time (raw)  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
472 -//always saved (PBD)//
473 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE
474 -DAQ channel: (% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE (%%)
475 -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). 
476 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
477 -
478 -\\
479 -
480 -(% style="color: rgb(255,102,0);" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
481 -//always saved (PBD)//
482 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%)
483 -DAQ channel: (% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%)
484 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
485 -
486 -\\
487 -
488 -(% style="color: rgb(255,102,0);" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
489 -//always saved (PBD)//
490 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%)
491 -DAQ channel(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.1(%%)
492 -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
493 -
494 -\\
495 -
496 -====== **BAM FL1.SFELC**{{code language="none"}}{{/code}} ======
497 -
498 -(% 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: rgb(255,102,0);" %)/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)
499 -
500 -//always saved (PBD)//
501 -(% style="color: rgb(23,43,77);" %)**FL1.SFELC**(%%)
502 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
503 -{{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 should be only 0). 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).
504 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
505 -
506 -\\
507 -
508 -\\
509 -
510 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
511 -//always saved (PBD)//
512 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIME.ABSOLUTE
513 -DAQ channel:** **(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.ABSOLUTE (%%)
514 -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). 
515 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
516 -
517 -\\
518 -
519 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
520 -//always saved (PBD)//
521 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%)
522 -DAQ channel(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMERROR(%%)
523 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
524 -
525 -\\
526 -
527 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
528 -//always saved (PBD)//
529 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%)
530 -DAQ chann(% style="color: rgb(0,0,0);" %)el: FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMSTATUS.1(%%)
531 -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
532 -
533 -\\
534 -
535 -\\
536 -
537 537  ===== electron beam profile =====
538 538  
539 539  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile{{/code}}
... ... @@ -562,7 +562,7 @@
562 562  ===== electron bunch energy =====
563 563  
564 564  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/average electron energy{{/code}}
565 -//always saved (PBD)//
333 +_always saved (PBD)
566 566  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
567 567  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
568 568  desc: electron bunch energy (average over the bunch train)
... ... @@ -570,7 +570,7 @@
570 570  \\
571 571  
572 572  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
573 -//always saved (PBD)//
341 +_always saved (PBD)
574 574  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD{{/code}}
575 575  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_SPECT{{/code}}
576 576  desc: electron bunch energy bunch resolved
... ... @@ -579,7 +579,7 @@
579 579  \\
580 580  
581 581  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average{{/code}}
582 -//always saved (PBD)//
350 +_always saved (PBD)
583 583  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL{{/code}}
584 584  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
585 585  desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
... ... @@ -627,7 +627,7 @@
627 627  //always saved (PBD)//
628 628  DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
629 629  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
630 -desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
398 +desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH1)
631 631  units:
632 632  \\
633 633  
... ... @@ -660,22 +660,6 @@
660 660  
661 661  ==== Pump Probe Laser (FLASH1) ====
662 662  
663 -**PIGLET (PG laser)**
664 -
665 -**{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}**
666 -
667 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/DIAG1out/PULSEENERGY.MEAN 
668 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG1_incoupl/PULSEENERGY.MEAN 
669 -FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG2_incoupl/PULSEENERGY.MEAN 
670 -
671 -
672 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION.RD 
673 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION_RAW.RD 
674 -FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.POSITION.RD
675 -
676 -\\
677 -
678 -{{expand title="Parameters used until 2021"}}
679 679  {{code language="none"}}/FL1/Experiment/Pump probe laser/laser attenuation{{/code}}
680 680  
681 681  //always saved (PBD)//
... ... @@ -716,15 +716,10 @@
716 716  //always saved (PBD)//
717 717  DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
718 718  DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
719 -desc: delay time between the optical laser and the FEL units: ps
720 -{{/expand}}
471 +desc: delaytime between the optical laser and the FEL units: ps
721 721  
722 722  \\
723 723  
724 -\\
725 -
726 -\\
727 -
728 728  [[Contents>>doc:||anchor="Contents"]]
729 729  
730 730  \\
... ... @@ -731,7 +731,7 @@
731 731  
732 732  ==== User Data (FLASH1) ====
733 733  
734 -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.
481 +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.
735 735  
736 736  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
737 737  
... ... @@ -759,13 +759,13 @@
759 759  {{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}}
760 760  
761 761  DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD  or CH00.DAQ.TD{{/code}}
762 -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.
509 +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.
763 763  DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}}
764 764  
765 765  In addition there are also additional parameters saved like:
766 766  
767 767  * {{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.
768 -* {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
515 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
769 769  * {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error
770 770  
771 771  ===== MHz ADCs =====
... ... @@ -778,7 +778,7 @@
778 778  In addition there are also additional parameters saved like:
779 779  
780 780  * {{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.
781 -* {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
528 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
782 782  
783 783  [[Contents>>doc:||anchor="Contents"]]
784 784  
... ... @@ -794,12 +794,12 @@
794 794  
795 795  ==== Beamline info (FLASH2) ====
796 796  
797 -{{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}
798 -(% style="color: rgb(0,0,0);" %)//always saved (PBD2)// (%%)
799 -(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
800 -(% style="color: rgb(0,0,0);" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
801 -(% style="color: rgb(0,0,0);" %)desc: set pressure in the gas attenuator (%%)
802 -(% style="color: rgb(0,0,0);" %)units: mbar(%%)
544 +(% style="color: rgb(255,153,0);" %)(not yet available){{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}(%%)
545 +(% style="color: rgb(193,199,208);" %)//always saved (PBD2)// (%%)
546 +(% style="color: rgb(193,199,208);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
547 +(% style="color: rgb(193,199,208);" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
548 +(% style="color: rgb(193,199,208);" %)desc: set pressure in the gas attenuator (%%)
549 +(% style="color: rgb(193,199,208);" %)units: mbar(%%)
803 803  \\
804 804  
805 805  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
... ... @@ -818,13 +818,11 @@
818 818  units: degree
819 819  \\
820 820  
821 -/FL2/Beamlines/Filter wheel/position wheel 2
822 -always saved (PBD2)
823 -DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
824 -DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
825 -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]]
826 -units: degree
827 827  
569 +//always saved (PBD2)//
570 +\\\\**[[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]**
571 +{{code language="none"}}/FL2/Beamlines/Filter wheel/position wheel 2 DOOCS prop : FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS desc: Position of the BL filter wheel 2 - to correlate with the filter material please look units: degree{{/code}}
572 +
828 828  \\
829 829  
830 830  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
... ... @@ -846,37 +846,40 @@
846 846  
847 847  \\
848 848  
594 +(% style="color: rgb(255,204,0);" %)average Sigma    to be included in
595 +
596 +(% style="color: rgb(193,199,208);" %){{code language="none"}}/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel uncertainty{{/code}} (%%)
597 +(% style="color: rgb(193,199,208);" %)//always saved (PBD2)// (%%)
598 +(% style="color: rgb(193,199,208);" %)DOOCS prop : FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ.SIGMA (%%)
599 +(% style="color: rgb(193,199,208);" %)DAQ channel: FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ.SIGMA (%%)
600 +(% style="color: rgb(193,199,208);" %)desc :  This parameter gives an indication of the error of the measurement of the average 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)(%%)
601 +(% style="color: rgb(193,199,208);" %)units : microJ
602 +
603 +\\
604 +
605 +\\
606 +
849 849  {{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
850 850  //always saved (PBD2)//
851 851  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
852 852  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
853 -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)
611 +desc : Energy per pulse measured in the Tunnel  (in fromt of the gas attenuator and the apertures in the Hall)
854 854  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]]**
855 855  
856 -{{info title="GMD pulse resolved data structure"}}
857 -For every pulse in the pulse train the information is saved:
858 -
614 +\\
859 859  
860 -1. **Intensity per pulse** (a.u. (more or less µJ ))
861 -1. Intensity per pulse (auxillary GMD) - not used
862 -1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
863 -1. Position vertical (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
864 -1. **Intensity per pulse sigma** (a.u. (more or less µJ ), (% style="color: rgb(0,0,0);" %)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)(%%))
865 -1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
866 -1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
867 -1. Combined warning and error flags
616 +\\
868 868  
869 -The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this 
870 -file
618 +{{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel uncertainty (sigma){{/code}}
619 +//always saved (PBD2)//
620 +DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.SIGMA.TD{{/code}}
621 +DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL:4{{/code}}
622 +desc :(% style="color: rgb(0,0,0);" %)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)(%%)
623 +units : a.u. (more or less µJ - related to the value of the pulse energy )
871 871  
872 -
873 -[[image:attach:image2021-2-9_10-51-6.png||height="250"]]
874 874  
875 -\\
876 -{{/info}}
626 +{{code language="none"}}{{/code}}
877 877  
878 -\\
879 -
880 880  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 !
881 881  
882 882  \\
... ... @@ -903,15 +903,13 @@
903 903  
904 904  \\
905 905  
906 -/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x
907 -always saved (PBD2)
908 -DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TD
909 -DAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2
910 -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 ...)
911 -units : mm   
912 912  
913 -(x=horizontal, y = vertial)
655 +//always saved (PBD2)//
656 +\\\\{{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TDDAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2 desc: {{/code}}Besides the well calibrated averaged beam position information there is also the option
657 +{{code language="none"}}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 ...)units : mm    {{/code}}
914 914  
659 +{{code language="none"}}(x=horizontal, y = vertial){{/code}}
660 +
915 915  again the same parameter set is available for the **HALL GMD**
916 916  
917 917  \\
... ... @@ -939,7 +939,7 @@
939 939  // saved opon request (PBD2)//
940 940  DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
941 941  DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
942 -desc : mean wavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
688 +desc : meanwavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
943 943  units : nm
944 944  
945 945  \\
... ... @@ -953,11 +953,11 @@
953 953  
954 954  \\
955 955  
956 -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"]])
702 +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 savng the compleate 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"]] ( respobsible for [[OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]])
957 957  
958 958  \\
959 959  
960 -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 ...
706 +In case OPIS was not operating there is still informaton 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 ...
961 961  
962 962  \\
963 963  
... ... @@ -976,21 +976,8 @@
976 976  
977 977  \\
978 978  
979 -===== electron bunch energy =====
725 +===== undulator settings =====
980 980  
981 -{{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}}
982 -//always saved (PBD2)//
983 -DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}}
984 -DAQ channel: (% style="color: rgb(94,108,132);" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%)
985 -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: rgb(94,108,132);" %)extraction and septum  in the beginning of FLASH2
986 -
987 -(% style="letter-spacing: 0.0px;" %)units: (% class="twikiNewLink" %)MeV
988 -
989 -\\
990 -
991 -(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %)
992 -undulator settings
993 -
994 994  {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
995 995  //always saved (PBD2)//
996 996  DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
... ... @@ -1008,130 +1008,21 @@
1008 1008  The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall.
1009 1009  
1010 1010  =====
1011 -arrival time (BAM) =====
744 +arrival time =====
1012 1012  
1013 -{{info title="BAM information: updates 2022"}}
1014 -* 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"]]
1015 -* The data format of the BAM has been completely altered in the 2022 shutdown
1016 -* 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 ...
1017 -* 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)
1018 -* There has been also a renaming  (and relocation) of the BAMs.
1019 -** acc:  4DBC3 → FL0.DBC2
1020 -** FL1: 1SFELC →  FL1.SFELC
1021 -** FL2: 8FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5
1022 -* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
1023 -* [[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]]
1024 -* a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
1025 -{{/info}}
1026 -
1027 -\\
1028 -
1029 -{{expand title="Discontinued BAM format (used until end 2021)"}}
1030 -(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording **
1031 -
1032 -{{code language="none"}}/FL2/Electron Diagnostic/BAM/8FL2XTDS/electron bunch arrival time (low charge){{/code}}
1033 -//always saved (PBD2)//
1034 -DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/8FL2XTDS/LOW_CHARGE_ARRIVAL_TIME{{/code}}
1035 -DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/8FL2XTDS.LOW_CHARGE_ARRIVAL_TIME{{/code}}
1036 -desc: Electron bunch arrival time measured with the BAM after the FLASH2 undulator (pulse resolved data)
1037 -units: ps (bigger numbers indicate later arrivaltime of the electrons)
1038 -
1039 1039  **FL1**{{code language="none"}}//Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
1040 1040  //always saved (PBD2)//
1041 1041  DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
1042 1042  DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
1043 -desc: Electron bunch arrival time measured with the BAM  in the accelerator  (pulse resolved data)
750 +desc: Electron bunch arrival time measured with the BAM (more or less) before the undulator (pulse resolved data)
1044 1044  units: ps (bigger numbers indicate later arrivaltime of the electrons)
1045 1045  
1046 -\\
753 +The BAM measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !). The first values are for FLASH1 bunches.
754 +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) ...
1047 1047  
1048 -{{info title="BAM hints"}}
1049 -* The BAM 4DBC3 measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !).
1050 -* 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 
1051 -** 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
1052 -* [[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]]
1053 -* [[LINK to detailed infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]]
1054 -* a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
1055 -{{/info}}
1056 -{{/expand}}
756 +Docu for BAM:  [[LINK to detailled infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]] and to a recent [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
1057 1057  
1058 -\\
1059 1059  
1060 -====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
1061 -
1062 -(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)(%%)
1063 -//always saved (PBD)//
1064 -**FL0.DBC2**
1065 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA2.COMP
1066 -{{code language="none"}}/FL2/Electron Diagnostic/BAM/ 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 should be only 0). 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).
1067 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1068 -
1069 -\\
1070 -
1071 -(% style="color: rgb(255,102,0);" %)DBC2/electron bunch arrival time (raw)  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1072 -//always saved (PBD)//
1073 -{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE{{/code}}
1074 -(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel: {{/code}}(%%)
1075 -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). 
1076 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1077 -
1078 -\\
1079 -
1080 -(% style="color: rgb(255,102,0);" %)DBC2/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1081 -//always saved (PBD)//
1082 -(% style="color: rgb(0,0,0);" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1083 -(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%)
1084 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1085 -
1086 -\\
1087 -
1088 -(% style="color: rgb(255,102,0);" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1089 -//always saved (PBD)//
1090 -(% style="color: rgb(0,0,0);" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
1091 -(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%)
1092 -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
1093 -
1094 -\\
1095 -
1096 -====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ======
1097 -
1098 -(% style="" %)/FL2/Electron Diagnostic/BAM/(%%)**SEED5**(% style="color: rgb(255,102,0);" %)/electron bunch arrival time  (HDF5 name not yet implemented - see zraw)
1099 -
1100 -//always saved (PBD)//
1101 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**(%%)
1102 -(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
1103 -{{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ {{/code}}(% style="" %)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 should be only 0). 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).
1104 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1105 -
1106 -\\
1107 -
1108 -\\
1109 -
1110 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1111 -//always saved (PBD)//
1112 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE{{/code}}(%%)
1113 -**~ **(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel:{{/code}}(%%)
1114 -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). 
1115 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
1116 -
1117 -\\
1118 -
1119 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/error (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1120 -//always saved (PBD)//
1121 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1122 -(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel{{/code}}(%%)
1123 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
1124 -
1125 -\\
1126 -
1127 -(% style="color: rgb(23,43,77);" %)SEED5(% style="color: rgb(255,102,0);" %)/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
1128 -//always saved (PBD)//
1129 -(% style="color: rgb(23,43,77);" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)E.bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIM{{/code}}(%%)
1130 -(% style="color: rgb(0,0,0);" %)el: FLASH.SDIAG/BAM/(% style="color: rgb(0, 0, 0); color: rgb(23, 43, 77)" %)**FL2.SEED5**(% style="color: rgb(0,0,0);" %)/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ chann{{/code}}(%%)
1131 -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
1132 -
1133 -\\
1134 -
1135 1135  [[Contents>>doc:||anchor="Contents"]]
1136 1136  
1137 1137  \\
... ... @@ -1258,80 +1258,7 @@
1258 1258  
1259 1259  There may be more information available from the "Laser DAQ". laese contact your Laser Local Contact.
1260 1260  
1261 -\\
1262 1262  
1263 -**User delay**
1264 -
1265 -Delay (set value):
1266 -
1267 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR{{/code}}
1268 -
1269 -Delay (encoder readback):
1270 -
1271 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD{{/code}}
1272 -
1273 -OXC. jitter:
1274 -
1275 -{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD{{/code}}
1276 -
1277 -\\
1278 -
1279 -**Pulse resolved energy:**
1280 -
1281 -1a) OPCPA output:
1282 -
1283 -{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH23.TD{{/code}}
1284 -
1285 -1b) OPCPA energy from PES (only fast channel):
1286 -
1287 -FLASH.LASER/CPUULGAN1.PULSEENERGY/OPCPA_Output/DAQ_CHANNEL
1288 -
1289 -2a) Upper breadboard Photodiode (THG) burst:
1290 -
1291 -{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH26.TD{{/code}}
1292 -
1293 -2b) Upper breadboard Photodiode (THG) energy (in-coupling user photodiode, fast)
1294 -
1295 -{{code language="none"}}FLASH.LASER/MOD24.PES/FL24_userPD/DAQ_CHANNEL{{/code}}
1296 -
1297 -\\
1298 -
1299 -**Attenuator angle:**
1300 -
1301 -{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
1302 -
1303 -**Polarization control:**
1304 -
1305 -{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL24/FPOS{{/code}}
1306 -
1307 -**SysDC delay error:**
1308 -
1309 -{{code language="none"}}FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26{{/code}}
1310 -
1311 -\\
1312 -
1313 -**Timing error: (these two need to be observed and both=0 means no error)**
1314 -
1315 -{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dT_alarm{{/code}}
1316 -
1317 -{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dMPN{{/code}}
1318 -
1319 -**Laser error status:**
1320 -
1321 -\\
1322 -
1323 -**Virtual camera X and Y history, beam size: (use slow data)**
1324 -
1325 -{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.X{{/code}}
1326 -
1327 -{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.Y{{/code}}
1328 -
1329 -{{code language="none"}}FLASH.LASER/MOD24.CAM/UV.14.VF/ROI_SPECTRUM.X.SIG{{/code}}
1330 -
1331 -\\
1332 -
1333 -{{expand title="Parameters used until 2021"}}
1334 -
1335 1335  {{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/attenuator position{{/code}}//always saved (PBD2)//
1336 1336  DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
1337 1337  DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
... ... @@ -1364,7 +1364,6 @@
1364 1364  DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}}
1365 1365  desc: rms jitter of the fs-Oscillator
1366 1366  units: fs
1367 -{{/expand}}
1368 1368  
1369 1369  [[Contents>>doc:||anchor="Contents"]]
1370 1370  
... ... @@ -1490,6 +1490,72 @@
1490 1490  [[Contents>>doc:||anchor="Contents"]]
1491 1491  
1492 1492  \\
1493 -{{/layout-cell}}
1494 -{{/layout-section}}
1495 -{{/layout}}
1043 +
1044 +== Example code showing how to access HDF5 files ==
1045 +
1046 +\\
1047 +
1048 +=== Samples how to read HDF5 with Matlab ===
1049 +
1050 +The examples apply to HDF files with HDF tree version before vers. 0.3.0.
1051 +
1052 +(% style="color: rgb(0,128,0);" %)%% read in the needed data p=path; path(p,'D:\mess-daten\DAQ-data\hdf5\Gotthard') % add the actual folder to the path hdf5file='FLASH1_EXP-2016-03-16T1420.h5'; % data with Gotthard and VLS
1053 +
1054 +(% style="color: rgb(0,128,0);" %)% h5disp(hdf5file,'/','min') % to get an idea what is in the file % h5info(hdf5file,'/Experiment/Gotthard1/BL.0') % get info about the individual channel
1055 +
1056 +(% style="color: rgb(0,128,0);" %)% read a Number per 10 Hz pulse train:
1057 +
1058 +(% class="code" %)
1059 +(((
1060 +FEL_Wavelength_energy_server=h5read(hdf5file,'/Photon Diagnostic/Wavelength/Calculated by energy/wavelength' );
1061 +)))
1062 +
1063 +(% style="color: rgb(0,128,0);" %)% read in a 1D array (spectrum) %GMD data GMD_Spectrum=h5read(hdf5file,'/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA');
1064 +
1065 +(% style="color: rgb(0,128,0);" %)% This reads in all the data . One can also limit the amount of data read to a subset of the data stored in the file. e.g. for image Data (Gotthard)
1066 +
1067 +\\
1068 +
1069 +(% class="code" %)
1070 +(((
1071 +Start_event= 500 ; % define the first 10 Hz event
1072 + Number_of_events = 20; % how many 10 Hz events to load
1073 +)))
1074 +
1075 +(% style="color: rgb(0,128,0);" %)% read only part of the data:
1076 +
1077 +(% class="code" %)
1078 +(((
1079 +Gotthard_data=h5read(hdf5file,'/Experiment/Gotthard1/BL.0',[2 650 Start_event],[50 85 Number_of_events]);
1080 +)))
1081 +
1082 +(% style="color: rgb(0,128,0);" %)% start stop increment "manual" for 2 D data : [start bunch number in Gotthard data start pixelin spectrum start sample in 10 Hz trains], % [number of bunches in the Gotthard data number of points in the spectrum number of spectra ]
1083 +
1084 +(% class="code" %)
1085 +(((
1086 +VLS_Spectrum=h5read(hdf5file,'/Photon Diagnostic/Wavelength/VLS online spectrometer/PCO.ROI.X',[400 Start_event],[200 Number_of_events] );
1087 +
1088 +)))
1089 +
1090 +(% style="color: rgb(0,128,0);" %)% start stop increment "manual" for 1D data : [start sample in the spectrum start sample in 10 Hz trains],[number of points in the spectrum number of spectra ]
1091 +
1092 +(% style="color: rgb(0,128,0);" %)%GMD data
1093 +
1094 +(% class="code" %)
1095 +(((
1096 +GMD_Spectrum=h5read(hdf5file,'/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA',[1 Start_event],[40 Number_of_events] );
1097 +)))
1098 +
1099 +[[Contents>>doc:||anchor="Contents"]]
1100 +
1101 +=== How to read HDF5 with Python via FLASHH5 ===
1102 +
1103 +With [[FlashH5>>doc:FLASHUSER.FLASHH5 for easier access of FLASH's HDF5 files]] we provide h5py based examples to access and evaluate FLASH's HDF5 files.
1104 +
1105 +\\
1106 +
1107 +== HDF5 and DOOCS ==
1108 +
1109 +Here is an outdated [[list with the available properties that are always saved (PBD) for FLASH1 as>>attach:FLASH1__DaqChannel2HdfNamePbd.xlsx]] HDF5 names and the corresponding DOOCS names
1110 +
1111 +[[Contents>>doc:||anchor="Contents"]]