Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/09/10 11:43

From 89.9 to 89.8 From 93.7 to 93.6

From version 93.6

edited by sndueste
on 2025/05/19 16:49

Change comment: There is no comment for this version

To version 89.9

edited by sndueste
on 2025/04/23 14:41

Change comment: Renamed back-links.

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Parent

@@ -1,1 +1,1 @@
--FLASHUSER.Offline data analysis (DAQ).WebHome
++FS-FLASH USER tmp.Offline data analysis (DAQ).WebHome

Content

@@ -111,20 +111,17 @@
  == Complete list of recordable parameters ==
  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"]].
++
  == Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
  {{id name="DOOCSparameters"/}}
++Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
++
  === FLASH1 ===
--
--In the Shutdown 2024 / 2025  the complete photon diagnostic and experiment control was renewed and thus the Doocs names and also some HDF5 names had to be changed. The new naming will be documented here as soon as the systems are online again.
--
--The previously used naming scheme (2024 and before) can be found here:
--
--
  ==== Beamline info (FLASH1) ====
  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
@@ -133,6 +133,7 @@
  DAQ channel: {{code language="none"}}FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE{{/code}}
  desc: set pressure in the gas attenuator
  units: mbar
++
  {{code language="none"}}/FL1/Beamlines/BL/Fast shutter/open{{/code}}
  //always saved (PBD)//
@@ -154,6 +154,7 @@
  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
  desc: Position of the BL filter wheel 1 - to correlate with the filter material please look [[here>>doc:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
  units: degree
++
  {{code language="none"}}/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 2{{/code}}
  //always saved (PBD)//
@@ -161,6 +161,7 @@
  DAQ channel: {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
  desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
  units: degree
++
  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 1{{/code}}
  //always saved (PBD)//
@@ -168,6 +168,7 @@
  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS{{/code}}
  desc: Position of the PG filter wheel 1
  units: degree
++
  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 2{{/code}}
  //always saved (PBD)//
@@ -175,6 +175,7 @@
  DAQ channel: {{code language="none"}}TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS{{/code}}
  desc: Position of the PG filter wheel 2
  units: degree
++
  {{code language="none"}}/FL1/Beamlines/PG/Filters/position filter 3{{/code}}
  //always saved (PBD)//
@@ -265,6 +265,7 @@
  {{info title="GMD pulse resolved data structure"}}
  For every pulse in the pulse train the information is saved:
++
 . **Intensity per pulse** (a.u. (more or less µJ ))
 . Intensity per pulse (auxillary GMD) - not used
@@ -409,7 +409,7 @@
  ** FL1: 1SFELC →  FL1.SFELC
  ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
  * for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
--* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FS-FLASH USER tmp.Additional helpful things1.FLASH beamlines and instruments references.WebHome]]
++* [[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]]
  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
  {{/info}}
@@ -508,6 +508,7 @@
  DAQ channel: {{code language="none"}}PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED{{/code}}
  desc: temporal profile of electron bunch, y axis in Ampers (FLASH1)
  units: pixel
++
  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant{{/code}}
  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
@@ -515,6 +515,7 @@
  DAQ channel: = PBD.BEAM.PROF.ML/CCT=
  desc: TDS calibration constant for the x-axis of the profiles: fs per pixel
  units: fs per pixel
++
  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms{{/code}}
  //always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)//
@@ -530,7 +530,8 @@
  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
  desc: electron bunch energy (average over the bunch train)
--units: (% class="twikiNewLink" %)MeV
++units: (% class="twikiNewLink" %)MeV(%%)
++
  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
  //always saved (PBD)//
@@ -546,6 +546,7 @@
  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
  desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
  units: nm
++
  [[Contents>>doc:||anchor="Contents"]]
@@ -560,6 +560,7 @@
  DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}
  desc: repetition rate of the bunches / pulses within the burst (FLASH1)
  units: kHz
++
  ===== set number of pulses =====
@@ -578,6 +578,7 @@
  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
  desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH1)
  units:
++
  ===== actual pulse pattern recorded after the undulator =====
@@ -587,6 +587,7 @@
  DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
  desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
  units:
++
  ===== Train ID =====
@@ -596,34 +596,24 @@
  DAQ channel: {{code language="none"}}none{{/code}}
  desc: Each 10 Hz burst has its unique train ID. For the HDF5 data set the ID is the same for all parameters with the same index (note camera images may be shifted by 1 ID - talk to the experts !)
  units:
++
--===== (% style="color:#e67e22" %)Train time(%%) =====
++===== Train time =====
--(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
++{{code language="none"}}/Timing/train time{{/code}}
  desc:Local time as array of day, hour, minute, second, and centisecond. This data set is meant for visualization purposes only. For correlations use the train ID or the Unix time of the time stamp
  units: d h min s cs
++
--(% style="color:#e67e22" %){{code language="none"}}/Timing/time stamp{{/code}}
++{{code language="none"}}/Timing/time stamp{{/code}}
  desc:first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date ~-~-date='@1553617729' or matlab, python etc
  second column: microseconds
  third column: Train ID of FLASH
++
--currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
--
--{{expand expanded="false" title="Timestamp help for python"}}
-- import time
--
--# epoch time is found in  /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time  #!!! a leading 1 has to be added !!!
--# The time and date of the start of the data taking in the HDF file is encoded in the filename - to roughly check the time
--epoch_time = 1709051499.17  # Replace with your epoch time
--
--formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
--print(formatted_time)
--{{/expand}}
--
--
  [[Contents>>doc:||anchor="Contents"]]
++
  ==== Pump Probe Laser (FLASH1) ====
  **PIGLET (PG laser)**
@@ -754,7 +754,8 @@
  (% style="color:#000000" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
  (% style="color:#000000" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
  (% style="color:#000000" %)desc: set pressure in the gas attenuator (%%)
--(% style="color:#000000" %)units: mbar
++(% style="color:#000000" %)units: mbar(%%)
++
  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
  //always saved (PBD2)//
@@ -770,6 +770,7 @@
  DAQ channel: FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS
  desc: Position of the BL filter wheel 1 - to correlate with the filter material please look **[[here>>doc:FS-FLASH USER tmp.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]**
  units: degree
++
  /FL2/Beamlines/Filter wheel/position wheel 2
  always saved (PBD2)
@@ -804,6 +804,7 @@
  {{info title="GMD pulse resolved data structure"}}
  For every pulse in the pulse train the information is saved:
++
 . **Intensity per pulse** (a.u. (more or less µJ ))
 . Intensity per pulse (auxillary GMD) - not used
@@ -952,7 +952,7 @@
  ** FL1: 1SFELC →  FL1.SFELC
  ** FL2: FL2XTDS → (% style="color:#172b4d" %)FL2.SEED5
  * for more Info: [[LINK to detailed infos from MSK>>doc:SDiag.How-to articles.BAM Data Structure.WebHome||shape="rect"]]
--* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments>>doc:FS-FLASH USER tmp.Additional helpful things1.FLASH beamlines and instruments references.WebHome]]
++* [[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]]
  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
  {{/info}}
@@ -977,7 +977,7 @@
  * The BAM 4DBC3 measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !).
  * 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
  ** 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
--* [[Link a collection of papers related to the BAM and the analysis of pump-probe experiments >>doc:FS-FLASH USER tmp.Additional helpful things1.FLASH beamlines and instruments references.WebHome]]
++* [[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]]
  * [[LINK to detailed infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|height="12" width="13"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]]
  * a recent  [[talk about the working principle of the BAM>>attach:BAM-basics and outlook-2018_DESY-template_16-9Format.pdf]]
  {{/info}}
@@ -1101,6 +1101,7 @@
  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
  desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH2)
  units:
++
  ===== actual pulse pattern recorded after the undulator =====
@@ -1110,6 +1110,7 @@
  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
  desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
  units:
++
  ===== Train ID =====
@@ -1119,40 +1119,26 @@
  DAQ channel: {{code language="none"}}none{{/code}}
  desc: Each 10 Hz burst has its unique train ID. For the HDF5 dataset the ID is the same for all parameters with the same index (note camera images may be shifted by 1 ID - talk to the experts !)
  units:
++
--===== (% style="color:#e67e22" %)Train time(%%) =====
++===== Train time =====
--(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
--(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
++//always saved (PBD2)//
++{{code language="none"}}/Timing/train time{{/code}}
  desc:Local time as array of day, hour, minute, second, and centisecond. This dataset is meant for visualisation purposes only. For correlations use the train ID or the Unix time of the time stamp
  units: d h min s cs
++
  {{code language="none"}}
  /Timing/time stamp
  {{/code}}
--(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
--(% style="color:#e67e22" %)desc: first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date ~-~-date='@1553617729' or matlab, python etc
++//always saved (PBD2)//
++desc: first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date ~-~-date='@1553617729' or matlab, python etc
  second column: microseconds
  third column: Train ID of FLASH
++
--
--(% id="cke_bm_2455529S" style="display:none" %) (%%)currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
--
--{{expand expanded="false" title="Timestamp help for python"}}
-- import time
--
--# epoch time is found in  /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time  #!!! a leading 1 has to be added !!!
--# The time and date of the start of the data taking in the HDF file is encoded in the filename - to roughly check the time
--epoch_time = 1709051499.17  # Replace with your epoch time
--
--formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
--print(formatted_time)
--{{/expand}}
--
--
--
--
  [[Contents>>doc:||anchor="Contents"]]

Changes for page The FLASH HDF5 structure

Summary

Details

Applications

Navigation