Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/02/06 10:55
From version 58.1
edited by sndueste
on 2022/09/07 17:20
Change comment: There is no comment for this version
To version 38.1
edited by sndueste
on 2021/02/09 10:51
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  
... ... @@ -19,38 +19,27 @@
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 +== The current 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 organized 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:attach:HDF5_structure.jpg||height="400"]]
35 35  
36 -Reference implementation, which follows the concept of Python libraries like Pandas, Xarray, or Dask, is given below.
32 +A detailed description of (most) channels can be found in the lower part of the hdf5 viewer:
33 +[[image:attach:HDF5_structure_desc.jpg||thumbnail="true" height="250"]]
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,67 +63,26 @@
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}}
57 +== The new (starting 2021) HDF5 format ==
80 80  
81 -{{layout-cell}}
82 -* The //average// FEL pulse energy as example for the **slow** **data** (different e.g. 1 Hz):
59 +Here is [[some documentation on the changes of the HDF5 format>>doc:FLASHUSER.HDF5 format]] that well be available in 2021 (work in progress)
83 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}}
90 -
91 -{{layout-cell}}
92 -* (((
93 -//zraw// group contains the **original DAQ (DOOCS) names**
94 -)))
95 -
96 - of the properties saved in the DESY internal raw format. (For experts)
97 -
98 98  \\
99 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 -== Complete list of recordable parameters ==
119 -
120 -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"]].
121 -\\
122 -
123 123  == Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
124 124  
125 125  {{id name="DOOCSparameters"/}}
126 126  
69 +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"]].
70 +The most common and often used ones are summarized below:
71 +
127 127  Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
128 128  
129 129  \\
... ... @@ -130,6 +130,8 @@
130 130  
131 131  === FLASH1 ===
132 132  
78 +\\
79 +
133 133  ==== Beamline info (FLASH1) ====
134 134  
135 135  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
... ... @@ -204,13 +204,12 @@
204 204  
205 205  \\
206 206  
207 -==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]]) ====
154 +==== 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) ====
208 208  
209 -{{expand title="Discontinued GMD format (used until 2021)"}}
210 -(% style="color: rgb(0,0,0);" %)**Discontinued GMD data recording / evaluation  (VME + PhotonFlux ML server)**
211 -
212 212  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
213 -//always saved (PBD)//
157 +//always saved (PBD)//
158 +(% style="color: rgb(165,173,186);" %)New MTCA Version: DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)
159 +(% style="color: rgb(165,173,186);" %)New MTCA Version: DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}
214 214  
215 215  (% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT04/VAL{{/code}} (%%)
216 216  (% style="color: rgb(0,0,0);" %)DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENPULSEIC{{/code}}(%%)
... ... @@ -220,6 +220,9 @@
220 220  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
221 221  //always saved (PBD)//
222 222  
169 +(% style="color: rgb(193,199,208);" %)New MTCA Version: DOOCS prop : 
170 +{{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TD{{/code}}New MTCA Version: DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TD{{/code}}
171 +
223 223  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
224 224  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
225 225  desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
... ... @@ -235,6 +235,9 @@
235 235  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
236 236  //always saved (PBD)//
237 237  
187 +(% style="color: rgb(165,173,186);" %)New MTCA Version: DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.BDA/PHOTONFLUX.UJ{{/code}} (%%)
188 +(% style="color: rgb(165,173,186);" %)New MTCA Version: DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.BDA/PHOTONFLUX.UJ{{/code}}
189 +
238 238  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT05/VAL{{/code}}
239 239  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENPULSEIC{{/code}}
240 240  desc : calibrated average SASE Energy/pulse measured in the BDA (in the experimental hall) after the attenuator (ion current)
... ... @@ -243,6 +243,8 @@
243 243  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA{{/code}}
244 244  //always saved (PBD)//
245 245  
198 +(% style="color: rgb(193,199,208);" %)New MTCA Version: DOOCS prop : 
199 +{{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.BDA/INTENSITY.TD{{/code}}New MTCA Version: DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL1.BDA/INTENSITY.TD{{/code}}(%%)
246 246  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
247 247  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
248 248  desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
... ... @@ -254,59 +254,9 @@
254 254  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
255 255  desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
256 256  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]]**
257 -{{/expand}}
258 258  
259 259  \\
260 260  
261 -(% style="letter-spacing: 0px; color: rgb(0, 0, 0)" %)**NEW (since 2021) GMD data recording / evaluation  (same format as FLASH2 and XFEL)**
262 -
263 -{{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
264 -//always saved (PBD)//
265 -(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)
266 -(% style="color: rgb(0,0,0);" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}
267 -
268 -desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator
269 -units : microJ
270 -
271 -\\
272 -
273 -{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
274 -//always saved (PBD)//
275 -
276 -(% style="color: rgb(0,0,0);" %)DOOCS prop : 
277 -{{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}}
278 -
279 -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)
280 -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]]**
281 -
282 -{{info title="GMD pulse resolved data structure"}}
283 -For every pulse in the pulse train the information is saved:
284 -
285 -
286 -1. **Intensity per pulse** (a.u. (more or less µJ ))
287 -1. Intensity per pulse (auxillary GMD) - not used
288 -1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
289 -1. Position vertical (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
290 -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)(%%))
291 -1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
292 -1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
293 -1. Combined warning and error flags
294 -
295 -The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this 
296 -file
297 -
298 -
299 -[[image:attach:image2021-2-9_10-51-6.png||height="250"]]
300 -
301 -\\
302 -{{/info}}
303 -
304 -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 !
305 -
306 -\\
307 -
308 -Besides  pulse energy the GMD also provides information about the beam position
309 -
310 310  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal{{/code}}
311 311  //always saved (PBD)//
312 312  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
... ... @@ -335,10 +335,6 @@
335 335  desc :Beam position of the photon Beam determined by the GMD (TUNNEL, y=vertical)
336 336  units : mm
337 337  
338 -\\
339 -
340 -==== Spectrometer (FLASH1) ====
341 -
342 342  {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength{{/code}}
343 343  _always saved (when Spectrum is measured !!) (PBD) _
344 344  DOOCS prop : {{code language="none"}}TTF2.EXP/PHOTONWL.ML/WAVE_LENGTH/VAL.TD{{/code}}
... ... @@ -416,27 +416,8 @@
416 416  units: nC
417 417  
418 418  =====
419 -arrival time (BAM) =====
319 +arrival time =====
420 420  
421 -{{info title="BAM information: updates 2022"}}
422 -* The data format of the BAM has been completely altered in the 2022 shutdown
423 -* 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 ...
424 -* THIS is now different. there are new parameters for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second)
425 -* There has been also a renaming  (and relocation) of the BAMs.
426 -** acc:  4DBC3 → FL0.DBC2
427 -** FL1: 1SFELC →  FL1.SFELC
428 -** FL2: FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5
429 -* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
430 -* [[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"]]
431 -* [[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]]
432 -* a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
433 -{{/info}}
434 -
435 -\\
436 -
437 -{{expand title="Discontinued BAM format (used until end 2021)"}}
438 -(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording **
439 -
440 440  {{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
441 441  //always saved (PBD)//
442 442  DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
... ... @@ -444,70 +444,17 @@
444 444  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).
445 445  units: ps (bigger numbers indicate later arrivaltime of the electrons)
446 446  
447 -\\
448 -
449 449  {{code language="none"}}/FL1/Electron Diagnostic/BAM/1SFELC/electron bunch arrival time (low charge){{/code}}
450 450  //always saved (PBD)//
451 451  DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/1SFELC/LOW_CHARGE_ARRIVAL_TIME{{/code}}
452 452  DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/1SFELC.LOW_CHARGE_ARRIVAL_TIME{{/code}}
453 453  desc: Electron bunch arrival time measured with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020.
454 -units: ps (bigger numbers indicate later arrival time of the electrons)
455 -{{/expand}}
333 +units: ps (bigger numbers indicate later arrivaltime of the electrons)
456 456  
457 -(% style="color: rgb(255,102,0);" %)DBC2/electron bunch arrival time{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
458 -//always saved (PBD)//
459 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.absolute.SA1
460 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.absolute.SA1 (%%)
461 -desc: Electron bunch arrival time measured with the BAM inside the accelerator (after bunch compressor 2) - It shows a very good correlation to the arrival time  of the XUV pulses in the experiment (see help).  The SA1 indicates the data is recorded for the first time slot at FLASh, typically used for FLASH1
462 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
463 -
464 -\\
465 -
466 -(% style="color: rgb(255,102,0);" %)DBC2/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
467 -//always saved (PBD)//
468 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%)
469 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%)
470 -desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
471 -
472 -\\
473 -
474 -(% style="color: rgb(255,102,0);" %)DBC2/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
475 -//always saved (PBD)//
476 -DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%)
477 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS(%%)
478 -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
479 -
480 -\\
481 -
482 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/electron bunch arrival time{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
483 -//always saved (PBD)//
484 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIME.absolute.SA1
485 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.absolute.SA1 (%%)
486 -desc: Electron bunch arrival time measured  with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020.  The SA1 indicates the data is recorded for the first time slot at FLASh, typically used for FLASH1
487 -units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
488 -
489 -\\
490 -
491 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
492 -//always saved (PBD)//
493 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%)
494 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(255,102,0);" %)/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 -
499 -(% style="color: rgb(23,43,77);" %)SFELC(% style="color: rgb(255,102,0);" %)/error{{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
500 -//always saved (PBD)//
501 -DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%)
502 -DAQ channel: (% style="color: rgb(255,102,0);" %)FLASH.SDIAG/BAM/(% style="color: rgb(255, 102, 0); color: rgb(23, 43, 77)" %)FL1.SFELC(% style="color: rgb(255,102,0);" %)/ARRIVAL_TIME.BAMSTATUS(%%)
503 -desc: (% style="" %) 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
504 -
505 -\\
506 -
507 507  {{info title="BAM hints"}}
508 508  * besides the arrivaltime from FLASH1 there is also the FLASH2/3 electron arrival time saved.In case of doubt ask your local contact
509 509  * [[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]]
510 -* [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
338 +* [[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"]]
511 511  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
512 512  {{/info}}
513 513  
... ... @@ -541,7 +541,7 @@
541 541  ===== electron bunch energy =====
542 542  
543 543  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/average electron energy{{/code}}
544 -//always saved (PBD)//
372 +_always saved (PBD)
545 545  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
546 546  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
547 547  desc: electron bunch energy (average over the bunch train)
... ... @@ -549,7 +549,7 @@
549 549  \\
550 550  
551 551  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
552 -//always saved (PBD)//
380 +_always saved (PBD)
553 553  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD{{/code}}
554 554  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_SPECT{{/code}}
555 555  desc: electron bunch energy bunch resolved
... ... @@ -558,7 +558,7 @@
558 558  \\
559 559  
560 560  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average{{/code}}
561 -//always saved (PBD)//
389 +_always saved (PBD)
562 562  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL{{/code}}
563 563  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
564 564  desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
... ... @@ -606,7 +606,7 @@
606 606  //always saved (PBD)//
607 607  DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
608 608  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
609 -desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
437 +desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH1)
610 610  units:
611 611  \\
612 612  
... ... @@ -679,7 +679,7 @@
679 679  //always saved (PBD)//
680 680  DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
681 681  DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
682 -desc: delay time between the optical laser and the FEL units: ps
510 +desc: delaytime between the optical laser and the FEL units: ps
683 683  
684 684  \\
685 685  
... ... @@ -689,7 +689,7 @@
689 689  
690 690  ==== User Data (FLASH1) ====
691 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.
520 +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.
693 693  
694 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 695  
... ... @@ -717,13 +717,13 @@
717 717  {{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}}
718 718  
719 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.
548 +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.
721 721  DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}}
722 722  
723 723  In addition there are also additional parameters saved like:
724 724  
725 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
554 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
727 727  * {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error
728 728  
729 729  ===== MHz ADCs =====
... ... @@ -736,7 +736,7 @@
736 736  In addition there are also additional parameters saved like:
737 737  
738 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
567 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
740 740  
741 741  [[Contents>>doc:||anchor="Contents"]]
742 742  
... ... @@ -752,12 +752,12 @@
752 752  
753 753  ==== Beamline info (FLASH2) ====
754 754  
755 -{{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}
756 -(% style="color: rgb(0,0,0);" %)//always saved (PBD2)// (%%)
757 -(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
758 -(% style="color: rgb(0,0,0);" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
759 -(% style="color: rgb(0,0,0);" %)desc: set pressure in the gas attenuator (%%)
760 -(% style="color: rgb(0,0,0);" %)units: mbar(%%)
583 +(% style="color: rgb(255,153,0);" %)(not yet available){{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}(%%)
584 +(% style="color: rgb(193,199,208);" %)//always saved (PBD2)// (%%)
585 +(% style="color: rgb(193,199,208);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
586 +(% style="color: rgb(193,199,208);" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
587 +(% style="color: rgb(193,199,208);" %)desc: set pressure in the gas attenuator (%%)
588 +(% style="color: rgb(193,199,208);" %)units: mbar(%%)
761 761  \\
762 762  
763 763  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
... ... @@ -776,13 +776,11 @@
776 776  units: degree
777 777  \\
778 778  
779 -/FL2/Beamlines/Filter wheel/position wheel 2
780 -always saved (PBD2)
781 -DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
782 -DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
783 -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]]
784 -units: degree
785 785  
608 +//always saved (PBD2)//
609 +\\\\**[[here>>doc:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]**
610 +{{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}}
611 +
786 786  \\
787 787  
788 788  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
... ... @@ -811,14 +811,13 @@
811 811  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)
812 812  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]]**
813 813  
814 -{{info title="GMD pulse resolved data structure"}}
815 815  For every pulse in the pulse train the information is saved:
816 816  
817 817  
818 818  1. **Intensity per pulse** (a.u. (more or less µJ ))
819 819  1. Intensity per pulse (auxillary GMD) - not used
820 -1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
821 -1. Position vertical (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
645 +1. Position horizontal (mm, for a single pulse the position informytion may be very noisy  - talk to your local contact)
646 +1. Position vertical (mm, for a single pulse the position informytion may be very noisy  - talk to your local contact)
822 822  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)(%%))
823 823  1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
824 824  1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
... ... @@ -830,10 +830,8 @@
830 830  
831 831  [[image:attach:image2021-2-9_10-51-6.png||height="250"]]
832 832  
833 -\\
834 -{{/info}}
835 835  
836 -\\
659 +{{code language="none"}}{{/code}}
837 837  
838 838  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 !
839 839  
... ... @@ -861,15 +861,13 @@
861 861  
862 862  \\
863 863  
864 -/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x
865 -always saved (PBD2)
866 -DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TD
867 -DAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2
868 -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 ...)
869 -units : mm   
870 870  
871 -(x=horizontal, y = vertial)
688 +//always saved (PBD2)//
689 +\\\\{{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
690 +{{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}}
872 872  
692 +{{code language="none"}}(x=horizontal, y = vertial){{/code}}
693 +
873 873  again the same parameter set is available for the **HALL GMD**
874 874  
875 875  \\
... ... @@ -897,7 +897,7 @@
897 897  // saved opon request (PBD2)//
898 898  DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
899 899  DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
900 -desc : mean wavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
721 +desc : meanwavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
901 901  units : nm
902 902  
903 903  \\
... ... @@ -911,11 +911,11 @@
911 911  
912 912  \\
913 913  
914 -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"]])
735 +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"]])
915 915  
916 916  \\
917 917  
918 -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 ...
739 +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 ...
919 919  
920 920  \\
921 921  
... ... @@ -934,21 +934,8 @@
934 934  
935 935  \\
936 936  
937 -===== electron bunch energy =====
758 +===== undulator settings =====
938 938  
939 -{{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}}
940 -//always saved (PBD2)//
941 -DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}}
942 -DAQ channel: (% style="color: rgb(94,108,132);" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%)
943 -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
944 -
945 -(% style="letter-spacing: 0.0px;" %)units: (% class="twikiNewLink" %)MeV
946 -
947 -\\
948 -
949 -(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %)
950 -undulator settings
951 -
952 952  {{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
953 953  //always saved (PBD2)//
954 954  DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
... ... @@ -1278,6 +1278,68 @@
1278 1278  [[Contents>>doc:||anchor="Contents"]]
1279 1279  
1280 1280  \\
1281 -{{/layout-cell}}
1282 -{{/layout-section}}
1283 -{{/layout}}
1089 +
1090 +== Example code showing how to access HDF5 files ==
1091 +
1092 +\\
1093 +
1094 +=== Samples how to read HDF5 with Matlab ===
1095 +
1096 +The examples apply to HDF files with HDF tree version before vers. 0.3.0.
1097 +
1098 +(% 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
1099 +
1100 +(% 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
1101 +
1102 +(% style="color: rgb(0,128,0);" %)% read a Number per 10 Hz pulse train:
1103 +
1104 +(% class="code" %)
1105 +(((
1106 +FEL_Wavelength_energy_server=h5read(hdf5file,'/Photon Diagnostic/Wavelength/Calculated by energy/wavelength' );
1107 +)))
1108 +
1109 +(% 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');
1110 +
1111 +(% 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)
1112 +
1113 +\\
1114 +
1115 +(% class="code" %)
1116 +(((
1117 +Start_event= 500 ; % define the first 10 Hz event
1118 + Number_of_events = 20; % how many 10 Hz events to load
1119 +)))
1120 +
1121 +(% style="color: rgb(0,128,0);" %)% read only part of the data:
1122 +
1123 +(% class="code" %)
1124 +(((
1125 +Gotthard_data=h5read(hdf5file,'/Experiment/Gotthard1/BL.0',[2 650 Start_event],[50 85 Number_of_events]);
1126 +)))
1127 +
1128 +(% 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 ]
1129 +
1130 +(% class="code" %)
1131 +(((
1132 +VLS_Spectrum=h5read(hdf5file,'/Photon Diagnostic/Wavelength/VLS online spectrometer/PCO.ROI.X',[400 Start_event],[200 Number_of_events] );
1133 +
1134 +)))
1135 +
1136 +(% 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 ]
1137 +
1138 +(% style="color: rgb(0,128,0);" %)%GMD data
1139 +
1140 +(% class="code" %)
1141 +(((
1142 +GMD_Spectrum=h5read(hdf5file,'/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA',[1 Start_event],[40 Number_of_events] );
1143 +)))
1144 +
1145 +[[Contents>>doc:||anchor="Contents"]]
1146 +
1147 +\\
1148 +
1149 +== HDF5 and DOOCS ==
1150 +
1151 +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
1152 +
1153 +[[Contents>>doc:||anchor="Contents"]]