Changes for page The FLASH HDF5 structure
Last modified by sndueste on 2026-01-19 14:35
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,3 +1,6 @@ 1 +{{layout}} 2 +{{layout-section ac:type="single"}} 3 +{{layout-cell}} 1 1 == Contents == 2 2 3 3 ... ... @@ -58,17 +58,25 @@ 58 58 {{/expand}} 59 59 60 60 === HDF examples: === 64 +{{/layout-cell}} 65 +{{/layout-section}} 61 61 67 +{{layout-section ac:type="three_equal"}} 68 +{{layout-cell}} 62 62 * ADC data as example for **fast** **data** (10 Hz): 63 63 64 64 [[image:attach:image2020-11-16_15-26-28.png||height="250"]] 72 +{{/layout-cell}} 65 65 74 +{{layout-cell}} 66 66 * 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}}) 67 67 68 68 ( as example only every 10th train ID is listed in the HDF group "index") 69 69 70 70 [[image:attach:image2020-11-16_15-31-45.png||height="250"]] 80 +{{/layout-cell}} 71 71 82 +{{layout-cell}} 72 72 * ((( 73 73 //zraw// group contains the **original DAQ (DOOCS) names** 74 74 ))) ... ... @@ -77,7 +77,11 @@ 77 77 78 78 79 79 [[image:attach:image2020-11-16_16-26-3.png||height="400"]] 91 +{{/layout-cell}} 92 +{{/layout-section}} 80 80 94 +{{layout-section ac:type="single"}} 95 +{{layout-cell}} 81 81 {{info}} 82 82 === There are different options that help you to work with the FLASH HDF5 data in Python === 83 83 ... ... @@ -84,8 +84,11 @@ 84 84 * The currently developed option for large data sets: [[the FAB package>>url:https://hasfcpkg.desy.de/fab/fab.html||shape="rect"]] ... see below 85 85 * and for smaller projects: (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]] 86 86 87 -(% class="Object" %)See also the collection of Demo data and sample scripts : [[ Collection ofHDF5sampledatafrom differentbeamlines>>doc:FLASHUSER.Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[DEMO - Working with FLASHdata>>doc:FLASHUSER.Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]102 +(% class="Object" %)See also the collection of Demo data and sample scripts : [[doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[doc:FS-FLASH USER tmp.Data Acquisition and controls 1.DAQ and controls overview.Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]] 88 88 {{/info}} 104 +{{/layout-cell}} 105 +{{/layout-section}} 106 +{{/layout}} 89 89 90 90 91 91 ... ... @@ -93,7 +93,7 @@ 93 93 94 94 The complete list for the relation between DOOCS names and HDF5 names for the recordable parameters can be found in [[DESY's Repository>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat||shape="rect"]]. 95 95 96 -== Most popular FLASH parameters and their names in HDF5, DOOCS and ( .raw) DAQ ==114 +== Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ == 97 97 98 98 {{id name="DOOCSparameters"/}} 99 99 ... ... @@ -105,7 +105,7 @@ 105 105 106 106 The previously used naming scheme (2024 and before) can be found here: 107 107 108 -{{expand expanded="false" title="FLASH1 naming scheme used until 2024"}}126 +{{expand expanded="false" title="FLASH1 Naming scheme used until 2024"}} 109 109 ==== (% id="cke_bm_8853497S" style="display:none" %) (%%)Beamline info (FLASH1) ==== 110 110 111 111 {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}} ... ... @@ -860,8 +860,6 @@ 860 860 units : 861 861 862 862 863 - 864 - 865 865 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"]]) 866 866 867 867 ... ... @@ -893,19 +893,19 @@ 893 893 (% style="color: rgb(94, 108, 132); font-weight: 600; letter-spacing: 0px;" %) 894 894 ===== undulator settings ===== 895 895 896 -{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength 1{{/code}}897 -DOOCS prop : {{code language="none"}}F LASH.FEL/FL2.WAVELENGTHCONTROL/FLASH2.COLOR1/WAVELENGTH{{/code}}898 -DAQ channel: {{code language="none"}}F LASH.FEL/FL2.WAVELENGTHCONTROL/FLASH2.COLOR1/WAVELENGTH{{/code}}899 -desc: Set value for the anticipated wavelength 1. This parameter is used to set the undulator gap. It may however deviate from the actual wavelength by several % ...For 2 color operation there is also the same parameter for COLOR 2912 +{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}} 913 +DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}} 914 +DAQ channel: {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}} 915 +desc: Set value for the anticipated wavelength . This parameter is used to set the undulator gap. It may however deviate from the actual wavelength by several % ... 900 900 units: nm 901 901 902 -{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE1 3gap{{/code}}903 -DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE1 3/GAP{{/code}}904 -DAQ channel: {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE1 3/GAP{{/code}}905 -desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper .918 +{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE14 gap{{/code}} 919 +DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}} 920 +DAQ channel: {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}} 921 +desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper 906 906 units: mm 907 907 908 -The gap values are saved for all 12 undulators (Nr 2to 13). Undulator 13is the one closest to the experimental hall.924 +The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall. 909 909 910 910 ===== 911 911 arrival time (BAM) ===== ... ... @@ -1189,7 +1189,7 @@ 1189 1189 1190 1190 {{view-file att--filename="FSLADAQ-DAQParameterlistFL24-2.pdf"}}{{/view-file}} 1191 1191 1192 - internallink to parameter list: [[FS-LA DAQ - XWiki>>url:https://xwiki.desy.de/xwiki/bin/view/FSLADAQ/]]1208 + 1193 1193 {{/info}} 1194 1194 1195 1195 {{expand title="Laser parameters used until 2023"}}