Skip to Content

Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2026-01-19 14:35
From version 103.1
edited by sndueste
on 2025-11-12 14:55
Change comment: There is no comment for this version
To version 104.2
edited by sndueste
on 2025-12-15 13:12
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  
... ... @@ -61,25 +61,17 @@
61 61  {{/expand}}
62 62  
63 63  === HDF examples: ===
64 -{{/layout-cell}}
65 -{{/layout-section}}
66 66  
67 -{{layout-section ac:type="three_equal"}}
68 -{{layout-cell}}
69 69  * ADC data as example for **fast** **data** (10 Hz):            
70 70  
71 71  [[image:attach:image2020-11-16_15-26-28.png||height="250"]]
72 -{{/layout-cell}}
73 73  
74 -{{layout-cell}}
75 75  * The //average// FEL pulse energy as example for the **slow** **data**. Here the data is not saved with 10 Hz  - thus not for every FEL pulse train.  The data is typically saved with 1 Hz if the values are changing (like the FEL energy) and every about 20 sec if there is no change for longer time ( e.g. motor set values). Thus to use the data together with the "fast" one, one has to interpolate the data as explained in the examples in the repos below show (e.g. {{code language="none"}}df['GMD_T_average'] = df['GMD_T_average'].interpolate(method='linear'){{/code}})
76 76  
77 77   ( as example only every 10th train ID is listed in the HDF group "index")
78 78  
79 79  [[image:attach:image2020-11-16_15-31-45.png||height="250"]]
80 -{{/layout-cell}}
81 81  
82 -{{layout-cell}}
83 83  * (((
84 84  //zraw// group contains the **original DAQ (DOOCS) names**
85 85  )))
... ... @@ -88,11 +88,7 @@
88 88  
89 89  
90 90  [[image:attach:image2020-11-16_16-26-3.png||height="400"]]
91 -{{/layout-cell}}
92 -{{/layout-section}}
93 93  
94 -{{layout-section ac:type="single"}}
95 -{{layout-cell}}
96 96  {{info}}
97 97  === There are different options that help you to work with the FLASH HDF5 data in Python ===
98 98  
... ... @@ -101,9 +101,6 @@
101 101  
102 102  (% class="Object" %)See also the collection of Demo data and sample scripts : [[Collection of HDF5 sample data from different beamlines>>doc:FLASHUSER.Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[DEMO - Working with FLASH data>>doc:FLASHUSER.Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]
103 103  {{/info}}
104 -{{/layout-cell}}
105 -{{/layout-section}}
106 -{{/layout}}
107 107  
108 108  
109 109  
... ... @@ -878,6 +878,8 @@
878 878  units :
879 879  
880 880  
863 +
864 +
881 881  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"]])
882 882  
883 883