Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/02/06 10:55

From 13.1 to 12.1 From 72.1 to 71.1

From version 71.1

edited by sndueste
on 2023/02/22 09:32

Change comment: There is no comment for this version

To version 13.1

edited by sndueste
on 2019/09/17 16:58

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -1,6 +4,3 @@
--{{layout}}
--{{layout-section ac:type="single"}}
--{{layout-cell}}
  == Contents ==
@@ -11,119 +11,39 @@
  == General information about HDF5 ==
--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"]]
++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"]]
--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"]]
++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"]]
  For use on the DESY Maxwell or PAL (max-fsc or pal) **hdfview** is available in the xray module :
  {{code language="none"}}> module load xray{{/code}}
  {{code language="none"}}> hdfview{{/code}}
--or you can use
--
--{{code language="none"}}> silx view{{/code}}
--
--\\
--
  [[Contents>>doc:||anchor="Contents"]]
--== The FLASH HDF5 format ==
++== FLASH HDF5 structure ==
--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.
++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:
--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.
++* Electron Diagnostic
++* Photon Diagnostics
++* Beamlines
++* Experiment
++* Timing
++[[~[~[image:url:http://hasfweb.desy.de/pub/Setup/HDF5main/HDF5_structure.jpg~|~|alt="HDF5_structure.jpg" width="700" height="500"~]~]>>attach:HDF5_structure.jpg]]
--Reference implementation, which follows the concept of Python libraries like Pandas, Xarray, or Dask, is given below.
++A detailled description of (most) channels can be found in the lower part of the hdf5 viewer:
++[[~[~[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]]
--\\
++[[Contents>>doc:||anchor="Contents"]]
--{{expand title="Discontinued HDF formats"}}
--=== Comparison to FLASH's deprecated HDF formats ===
--
--Before 2021, FLASH provided two different HDF formats formally known as //near-online// and //offline// HDF files.
--
--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.
--
--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.
--
--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.
--
  \\
--**HDF5 example files (old format)**
++== Most popular FLASH parameters and their names in HDF5 ==
--Here we have a few HDF5 samples (User data combined with Photon diagnostics data) from a few beamtimes showing the different kind options.
++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"]].
++The most common and often used ones are summarized below:
--[[image:attach:image2019-10-21_17-2-50.png||thumbnail="true" width="300"]]  [[download HDF5 (Images @ FL2)>>url:https://desycloud.desy.de/index.php/s/nyEgeCWJFC4gao2||shape="rect"]]
--
--\\
--
--[[~[~[image:attach:image2019-10-22_10-52-27.png~|~|thumbnail="true" width="300"~]~]download HDF5 (GHz ADC and OPIS @ FL2)>>url:https://desycloud.desy.de/index.php/s/AeA2kPNNnZgX95A||shape="rect"]]
--
--\\
--
--\\
--{{/expand}}
--
--=== HDF examples: ===
--{{/layout-cell}}
--{{/layout-section}}
--
--{{layout-section ac:type="three_equal"}}
--{{layout-cell}}
--*  ADC data as example for **fast** **data** (10 Hz):
--
--\\
--
--[[image:attach:image2020-11-16_15-26-28.png||height="250"]]
--{{/layout-cell}}
--
--{{layout-cell}}
--* 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}})
--
--           ( as example only every 10th train ID is listed in the HDF group "index")
--
--[[image:attach:image2020-11-16_15-31-45.png||height="250"]]
--{{/layout-cell}}
--
--{{layout-cell}}
--* (((
--//zraw// group contains the **original DAQ (DOOCS) names**
--)))
--
--           of the properties saved in the DESY internal raw format. (For experts)
--
--\\
--
--[[image:attach:image2020-11-16_16-26-3.png||height="400"]]
--{{/layout-cell}}
--{{/layout-section}}
--
--{{layout-section ac:type="single"}}
--{{layout-cell}}
--{{info}}
--=== Reference implementation (Python) ===
--
--(imperative)  (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]]
--
--(% class="Object" %)(object oriented) [[https:~~/~~/gitlab.desy.de/christopher.passow/fdh-builder>>url:https://gitlab.desy.de/christopher.passow/fdh-builder.git||shape="rect"]]
--{{/info}}
--{{/layout-cell}}
--{{/layout-section}}
--
--{{layout-section ac:type="single"}}
--{{layout-cell}}
--
--
--== 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~[~[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"]].
--\\
--
--== 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.
  \\
@@ -130,6 +130,8 @@
  === FLASH1 ===
++\\
++
  ==== Beamline info (FLASH1) ====
  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
@@ -160,7 +160,7 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS{{/code}}
  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:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
++desc: Position of the BL filter wheel 1 - to correlate with the filter material please look [[here>>doc:FLASH.Filter history (BL filterwheel 12)]]
  units: degree
  \\
@@ -168,7 +168,7 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS{{/code}}
  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:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]
++desc: Position of the BL filter wheel 2 - to correlate with the filter material please look [[here>>doc:FLASH.Filter history (BL filterwheel 12)]]
  units: degree
  \\
@@ -198,32 +198,27 @@
  \\
--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
++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
  [[Contents>>doc:||anchor="Contents"]]
  \\
--==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]]) ====
++==== 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) ====
--{{expand title="Discontinued GMD format (used until 2021)"}}
--(% style="color: rgb(0,0,0);" %)**Discontinued GMD data recording / evaluation  (VME + PhotonFlux ML server)**
--
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
--//always saved (PBD)//
--
--(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT04/VAL{{/code}} (%%)
--(% style="color: rgb(0,0,0);" %)DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENPULSEIC{{/code}}(%%)
--desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator (ion current)
++//always saved (PBD)//
++DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT04/VAL{{/code}}
++DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENPULSEIC{{/code}}
++desc : calibrated average SASE Energy/pulse measured in the TUNNEL before the attenuator (ion current)
  units : microJ
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
--//always saved (PBD)//
--
++//always saved (PBD)//
  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT34/VAL{{/code}}
  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.USER{{/code}}
  desc :Energy per pulse Tunnel (from e-) - the values are set to "0" if there was no SASE beam in the FEL
--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]]**
++units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASH.Calibrating the pulse resolved (electron) data from GMD]]
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel (raw){{/code}}
  //always saved (PBD)//
@@ -230,11 +230,10 @@
  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT14/VAL{{/code}}
  DAQ channel: {{code language="none"}}PBD.PHFLUX/TUNNEL.ENERGYPULSE.FF{{/code}}
  desc :Energy per pulse Tunnel (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
--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]]**
++units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASH.Calibrating the pulse resolved (electron) data from GMD]]
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy BDA{{/code}}
--//always saved (PBD)//
--
++//always saved (PBD)//
  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT05/VAL{{/code}}
  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENPULSEIC{{/code}}
  desc : calibrated average SASE Energy/pulse measured in the BDA (in the experimental hall) after the attenuator (ion current)
@@ -241,12 +241,11 @@
  units : microJ
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA{{/code}}
--//always saved (PBD)//
--
++//always saved (PBD)//
  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT35/VAL{{/code}}
  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.USER{{/code}}
  desc :Energy per pulse BDA (from e-) - the values are set to "0" if there was no SASE beam in the FEL
--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]]**
++units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASH.Calibrating the pulse resolved (electron) data from GMD]]
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA (raw){{/code}}
  //always saved (PBD)//
@@ -253,65 +253,13 @@
  DOOCS prop : {{code language="none"}}TTF2.DAQ/PHFLUX/OUT15/VAL{{/code}}
  DAQ channel: {{code language="none"}}PBD.PHFLUX/BDA.ENERGYPULSE.FF{{/code}}
  desc :Energy per pulse BDA (from e-) - uncorrected values. There are also values saved if there was no beam ... just background noise
--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]]**
--{{/expand}}
++units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASH.Calibrating the pulse resolved (electron) data from GMD]]
--\\
--
--(% style="letter-spacing: 0px; color: rgb(0, 0, 0)" %)**NEW (since 2021) GMD data recording / evaluation  (same format as FLASH2 and XFEL)**
--
--{{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
--//always saved (PBD)//
--(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}} (%%)
--(% style="color: rgb(0,0,0);" %)DAQ channel: {{code language="none"}}FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ{{/code}}
--
--desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator
--units : microJ
--
--\\
--
--{{code language="none"}}/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
--//always saved (PBD)//
--
--(% style="color: rgb(0,0,0);" %)DOOCS prop :
--{{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}}
--
--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)
--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]]**
--
--{{info title="GMD pulse resolved data structure"}}
--For every pulse in the pulse train the information is saved:
--
--
--1. **Intensity per pulse** (a.u. (more or less µJ ))
--1. Intensity per pulse (auxillary GMD) - not used
--1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
--1. Position vertical  (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
--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)(%%))
--1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
--1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
--1. Combined warning and error flags
--
--The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this
--file
--
--
--[[image:attach:image2021-2-9_10-51-6.png||height="250"]]
--
--\\
--{{/info}}
--
--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 !
--
--\\
--
--Besides  pulse energy the GMD also provides information about the beam position
--
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal{{/code}}
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS{{/code}}
--desc :Beam position of the photon Beam determined by the GMD (BDA, x=horizontal)
++desc :Beam position of the photon Beam determined by the [[GMD>>doc:FLASH.Gas Monitor Detector]] (BDA, x=horizontal)
  units : mm
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position BDA vertical{{/code}}
@@ -318,7 +318,7 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS{{/code}}
  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS{{/code}}
--desc :Beam position of the photon Beam determined by the GMD (BDA, y=vertical)
++desc :Beam position of the photon Beam determined by the [[GMD>>doc:FLASH.Gas Monitor Detector]] (BDA, y=vertical)
  units : mm
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position tunnel horizontal{{/code}}
@@ -325,7 +325,7 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS{{/code}}
  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS{{/code}}
--desc :Beam position of the photon Beam determined by the GMD (TUNNEL, x=horizontal)
++desc :Beam position of the photon Beam determined by the [[GMD>>doc:FLASH.Gas Monitor Detector]] (TUNNEL, x=horizontal)
  units : mm
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Beam position/position tunnel vertical{{/code}}
@@ -332,13 +332,9 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS{{/code}}
  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS{{/code}}
--desc :Beam position of the photon Beam determined by the GMD (TUNNEL, y=vertical)
++desc :Beam position of the photon Beam determined by the [[GMD>>doc:FLASH.Gas Monitor Detector]] (TUNNEL, y=vertical)
  units : mm
--\\
--
--==== Spectrometer (FLASH1) ====
--
  {{code language="none"}}/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength{{/code}}
  _always saved (when Spectrum is measured !!) (PBD) _
  DOOCS prop : {{code language="none"}}TTF2.EXP/PHOTONWL.ML/WAVE_LENGTH/VAL.TD{{/code}}
@@ -416,122 +416,16 @@
  units: nC
  =====
--arrival time (BAM) =====
++arrival time =====
--{{info title="BAM information: updates 2022"}}
--* 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"]]
--* The data format of the BAM has been completely altered in the 2022 shutdown
--* 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 ...
--* 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)
--* There has been also a renaming  (and relocation) of the BAMs.
--** acc:  4DBC3 → FL0.DBC2
--** FL1: 1SFELC →  FL1.SFELC
--** FL2: FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5
--* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
--* [[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}}
--
--\\
--
--{{expand title="Discontinued BAM format (used until end 2021)"}}
--(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording **
--
  {{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
  DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
--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).
--units: ps (bigger numbers indicate later arrivaltime of the electrons)
++desc: Electron bunch arrival time measured with the BAM (more or less) before the undulator (pulse resolved data)
++units: ps (bigger numbers indicate later arrivaltime of the electrons)
++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>>url:https://confluence.desy.de/download/attachments/134216957/BAM-basics_and_outlook-2018_DESY-template_16-9Format.pdf?version=1&modificationDate=1565162143328&api=v2||shape="rect"]]
--\\
--
--{{code language="none"}}/FL1/Electron Diagnostic/BAM/1SFELC/electron bunch arrival time (low charge){{/code}}
--//always saved (PBD)//
--DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/1SFELC/LOW_CHARGE_ARRIVAL_TIME{{/code}}
--DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/1SFELC.LOW_CHARGE_ARRIVAL_TIME{{/code}}
--desc: Electron bunch arrival time measured with the BAM  before the undulator (pulse resolved data). This one was newly installed in 2020.
--units: ps (bigger numbers indicate later arrival time of the electrons)
--{{/expand}}
--
--====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
--
--(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time   (HDF5 name not yet implemented - see zraw)(%%)
--//always saved (PBD)//
--**FL0.DBC2**
--(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA1.COMP (%%)
--{{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).
--
--{{code language="none"}}units: fs (bigger numbers (typically) indicate later arrival times of the electrons).{{/code}}
--
--\\
--
--(% 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}}(%%)
--//always saved (PBD)//
--DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE
--DAQ channel: (% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE (%%)
--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).
--units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
--
--\\
--
--(% style="color: rgb(255,102,0);" %)DBC2/error  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
--//always saved (PBD)//
--DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%)
--DAQ channel: (% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR(%%)
--desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
--
--\\
--
--(% style="color: rgb(255,102,0);" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
--//always saved (PBD)//
--DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%)
--DAQ channel(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.1(%%)
--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
--
--\\
--
--====== **BAM FL1.SFELC**{{code language="none"}}{{/code}} ======
--
--(% 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)
--
--//always saved (PBD)//
--(% style="color: rgb(23,43,77);" %)**FL1.SFELC**(%%)
--(% 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
--{{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).
--units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
--
--\\
--
--\\
--
--(% 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}}(%%)
--//always saved (PBD)//
--DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIME.ABSOLUTE
--DAQ channel:** **(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.ABSOLUTE (%%)
--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).
--units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
--
--\\
--
--(% 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}}(%%)
--//always saved (PBD)//
--DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E.bamError(%%)
--DAQ channel(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMERROR(%%)
--desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
--
--\\
--
--(% 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}}(%%)
--//always saved (PBD)//
--DOOCS prop : FLASH.SDIAG/BAM/(% style="color: rgb(23,43,77);" %)FL1.SFELC(%%)/ARRIVAL_TIM(% style="color: rgb(0,0,0);" %)E..bamStatus.//1//(%%)
--DAQ chann(% style="color: rgb(0,0,0);" %)el: FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.BAMSTATUS.1(%%)
--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
--
--\\
--
--\\
--
  ===== electron beam profile =====
  {{code language="none"}}/FL1/Electron Diagnostic/Electron bunch profile/TDS profile{{/code}}
@@ -560,7 +560,7 @@
  ===== electron bunch energy =====
  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/average electron energy{{/code}}
--//always saved (PBD)//
++_always saved (PBD)
  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)
@@ -568,7 +568,7 @@
  \\
  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
--//always saved (PBD)//
++_always saved (PBD)
  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD{{/code}}
  DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_SPECT{{/code}}
  desc: electron bunch energy bunch resolved
@@ -577,7 +577,7 @@
  \\
  {{code language="none"}}/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average{{/code}}
--//always saved (PBD)//
++_always saved (PBD)
  DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL{{/code}}
  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)
@@ -625,7 +625,7 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
  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)
++desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH1)
  units:
  \\
@@ -635,7 +635,7 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}none{{/code}}
  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 !)
++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:
  \\
@@ -642,7 +642,7 @@
  ===== Train time =====
  {{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
++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
  \\
@@ -658,43 +658,6 @@
  ==== Pump Probe Laser (FLASH1) ====
--**PIGLET (PG laser)**
--
--**{{code language="none"}}/FL1/Experiment/Pump probe laser{{/code}}**
--
--FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/DIAG1out/PULSEENERGY.MEAN
--FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG1_incoupl/PULSEENERGY.MEAN
--FLASH.LASER/FLACPUPGLASER1.PULSEENERGY/PG2_incoupl/PULSEENERGY.MEAN
--FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION.RD
--FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.ENCODER_POSITION_RAW.RD
--FLASH.SYNC/LASER.LOCK.EXP/FLASH1.MOD1.PG.OSC/FMC0.MD22.1.POSITION.RD
--
--**BL - Hidra laser **
--
--Property,Units,Description
--FLASH.LASER/MODBL.CAM/BL1.13.AC/DAQ_CHANNEL,'AU','FL1HIDRAPP1 Autocorrelation (IR) ROI readout'
--FLASH.LASER/MODBL.CAM/BL1.14.VF/DAQ_CHANNEL,'AU','FL1HIDRAPP1 Virtual Focus Camera (IR) ROI readout'
--FLASH.LASER/MODBL.SENSORBOARD/PDTRIG_CAMP/DAQ_CHANNEL,'au','FL1PPL Energy channels'
--FLASH.LASER/MODBL.SPECT/CAMP_IR/DAQ_CHANNEL,'au','FL1PPL BL Table Spectrum'
--FLASH.LASER/HIDRAPP1.SPECTRUM_ANALYSIS/CAMP_IR/DAQ_CHANNEL,'au','FL1PPL Spectrum Analysis'
--FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.POSITION.RD,'ps','FL1PPL Optical Delay Line (act)'
--FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.POSITION_SET.WR,'ps','FL1PPL Optical Delay Line (set)'
--FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/FMC0.MD22.1.ENCODER_POSITION.RD,'ps','FL1PPL Optical Delay Line (Encoder Readback)'
--FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP_Delayline/FPOS,'ps','FL1PPL NIR delay BL1 table (act)'
--FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP_Delayline/FPOS.SET,'ps','FL1PPL NIR delay BL1 table (set)'
--FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP.ATT/FPOS,'degree','FL1PPL Transmission degree (act)'
--FLASH.FEL/FLAPPBEAMLINES.MOTOR/CAMP.ATT/FPOS.SET,'degree','FL1PPL Transmission degree (set)'
--FLASH.FEL/FLAPPBEAMLINES.MOTOR/Camp_Focus_Lens/FPOS,'mm','FL1PPL Focus Mirror Stage Position (act)'
--FLASH.FEL/FLAPPBEAMLINES.MOTOR/Camp_Focus_Lens/FPOS.SET,'mm','FL1PPL Focus Mirror Stage Position (set)'
--FLASH.LASER/MODBL.FEEDFWD/BL1_Att/INPUT.Y,'%','FL1PPL Transmission rate'
--FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/CURRENT_INPUT_JITTER.RD,'fs','FL1PPL Sync. Jitter'
--FLASH.SYNC/LASER.LOCK.EXP/F1.PPL.OSC/LOCK_STATUS.VALUE.RD,'au','FL1PPL Sync. Status'
--
--\\
--
--\\
--
--{{expand title="Parameters used until 2021"}}
  {{code language="none"}}/FL1/Experiment/Pump probe laser/laser attenuation{{/code}}
  //always saved (PBD)//
@@ -735,8 +735,7 @@
  //always saved (PBD)//
  DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
  DOOCS prop : {{code language="none"}}TTF2.FEL/TDOLFEL/TDOLFEL/STREAK.CAM.TIME{{/code}}
--desc: delay time between the optical laser and the FEL units: ps
--{{/expand}}
++desc: delaytime between the optical laser and the FEL units: ps
  \\
@@ -746,15 +746,9 @@
  ==== User Data (FLASH1) ====
--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.
--
--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
--
--The most common and permanently installed device used by experiment are our ADCs:
--
  ===== GHz ADCs =====
--ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found** [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]**
++ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]
  //saved on DEMAND in the user DAQ//
  \\The HDF5 names for the ADC traces are depending on the beamline :
  \\PG Beamline:
@@ -774,15 +774,17 @@
  {{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}}
  DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD  or CH00.DAQ.TD{{/code}}
--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.
++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.
  DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}}
--In addition there are also additional parameters saved like:
++in addition there are also additional parameters saved like:
--* {{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.
--* {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
--* {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error
++* sample frequency (in MHz)
++* error (state)
++* offset
++~|
++
  ===== MHz ADCs =====
  similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
@@ -790,19 +790,10 @@
  DOOCS prop : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02/CH00.TD
  DAQ channel: : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02
--In addition there are also additional parameters saved like:
++\\
--* {{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.
--* {{code language="none"}}number of samples{{/code}}: total number of samples recorded for each 10 Hz trigger
--
  [[Contents>>doc:||anchor="Contents"]]
--\\
--
--\\
--
--\\
--
  === FLASH2 ===
  There is analog to FLASH1 a permanently running "PhotonDagnostic DAQ FLASH2" (PBD2) and 2 User DAQs
@@ -809,12 +809,12 @@
  ==== Beamline info (FLASH2) ====
--{{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}
--(% style="color: rgb(0,0,0);" %)//always saved (PBD2)// (%%)
--(% style="color: rgb(0,0,0);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
--(% style="color: rgb(0,0,0);" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
--(% style="color: rgb(0,0,0);" %)desc: set pressure in the gas attenuator (%%)
--(% style="color: rgb(0,0,0);" %)units: mbar(%%)
++(% style="color: rgb(255,153,0);" %)(not yet available){{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}(%%)
++//always saved (PBD2)//
++DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}}
++DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}}
++desc: set pressure in the gas attenuator
++units: mbar
  \\
  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
@@ -829,17 +829,15 @@
  //always saved (PBD2)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS{{/code}}
  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:FLASHUSER.jddd-linked help pages.Filter-Units.Filter wheels in FLASH1 and FLASH2.WebHome]]**
++desc: Position of the BL filter wheel 1 - to correlate with the filter material please look [[here>>doc:FLASH.Filter history (BL filterwheel 12)]]
  units: degree
  \\
--/FL2/Beamlines/Filter wheel/position wheel 2
--always saved (PBD2)
--DOOCS prop : {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
--DAQ channel: {{code language="none"}}FLASH.FEL/FL20H.PH.MOTOR/MOTOR2.MOT3/FPOS{{/code}}
--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]]
--units: degree
++//always saved (PBD2)//
++\\\\[[here>>doc:FLASH.Filter history (BL filterwheel 12)]]
++{{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}}
++
  \\
  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
@@ -861,37 +861,40 @@
  \\
++(% style="color: rgb(255,204,0);" %)average Sigma    to be included in
++
++(% style="color: rgb(193,199,208);" %){{code language="none"}}/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel uncertainty{{/code}} (%%)
++(% style="color: rgb(193,199,208);" %)//always saved (PBD2)// (%%)
++(% style="color: rgb(193,199,208);" %)DOOCS prop : FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ.SIGMA (%%)
++(% style="color: rgb(193,199,208);" %)DAQ channel: FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ.SIGMA (%%)
++(% 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)(%%)
++(% style="color: rgb(193,199,208);" %)units : microJ
++
++\\
++
++\\
++
  {{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel{{/code}}
  //always saved (PBD2)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD{{/code}}
--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)
--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]]**
++desc : Energy per pulse measured in the Tunnel  (in fromt of the gas attenuator and the apertures in the Hall)
++units : a.u. (more or less µJ but need to be calibrated with the "Average energy" for good precision) [[see here for help>>doc:FLASH.Calibrating the pulse resolved (electron) data from GMD]]
--{{info title="GMD pulse resolved data structure"}}
--For every pulse in the pulse train the information is saved:
--
++\\
--1. **Intensity per pulse** (a.u. (more or less µJ ))
--1. Intensity per pulse (auxillary GMD) - not used
--1. Position horizontal (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
--1. Position vertical  (mm, for a single pulse the position information may be very noisy  - talk to your local contact)
--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)(%%))
--1. Position horizontal sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
--1. Position vertical sigma  (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
--1. Combined warning and error flags
++\\
--The pulse energy and the error are plotted for the first bunch of the pulse trains saved in this
--file
++{{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel uncertainty (sigma){{/code}}
++//always saved (PBD2)//
++DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.SIGMA.TD{{/code}}
++DAQ channel: {{code language="none"}}FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL:4{{/code}}
++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)(%%)
++units : a.u. (more or less µJ - related to the value of the pulse energy )
--
--[[image:attach:image2021-2-9_10-51-6.png||height="250"]]
--\\
--{{/info}}
++{{code language="none"}}{{/code}}
--\\
--
  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 !
  \\
@@ -904,7 +904,7 @@
  //always saved (PBD2)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS{{/code}}
--desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
++desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the [[GMD>>doc:FLASH.Gas Monitor Detector]] (tunnel, x=horizontal)
  units : mm
  \\
@@ -913,20 +913,20 @@
  //always saved (PBD2)//
  DOOCS prop : {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
  DAQ channel: {{code language="none"}}FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS{{/code}}
--desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
++desc : the Average ( ~~ 20 sec averaging time ) Beam position of the photon Beam determined by the [[GMD>>doc:FLASH.Gas Monitor Detector]] (tunnel, x=horizontal)
  units : mm
  \\
--/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x
--always saved (PBD2)
--DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TD
--DAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2
--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 ...)
--units : mm
++\\
--(x=horizontal, y = vertial)
++//always saved (PBD2)//
++\\\\{{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
++{{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}}
++
++{{code language="none"}}(x=horizontal, y = vertial){{/code}}
++
  again the same parameter set is available for the **HALL GMD**
  \\
@@ -933,9 +933,9 @@
  \\
--==== Photon Diagnostics OPIS[[  >>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]](FLASH2) ====
++==== Photon Diagnostics OPIS[[ >>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]](FLASH2) ====
--for more info see:** [[ OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]]**
++for more info see: [[ OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]]
  (The OPIS hall is not installed yet ...)
@@ -954,7 +954,7 @@
  // saved opon request (PBD2)//
  DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
  DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040{{/code}}
--desc : mean wavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
++desc : meanwavelength ( ~~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
  units : nm
  \\
@@ -968,216 +968,121 @@
  \\
--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"]])
++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"]])
  \\
--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 ...
++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 ...
  \\
  \\
++\\
++
  ==== Electron Beam properties (FLASH2) ====
  ===== bunch charge =====
  {{code language="none"}}/FL2/Electron Diagnostic/Bunch charge/after undulator{{/code}}
--//always saved (PBD2)//
++//always saved (PBD)//
  DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
--desc: electron bunch charge FLASH2 (average value for each bunchtrain).
++desc: electron bunch charge (FLASH2)
  units: nC
  \\
--===== electron bunch energy =====
--
--{{code language="none"}}/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2{{/code}}
--DAQ channel: (% style="color: rgb(94,108,132);" %)TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2{{code language="none"}}{{/code}}(%%)
--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
--
--(% style="letter-spacing: 0.0px;" %)units: (% class="twikiNewLink" %)MeV
--
  \\
--(% style="color: rgb(94,108,132);font-weight: 600;letter-spacing: 0.0px;" %)
--undulator settings
++(% class="wrapped" %)
++|(((
++FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP
++)))|(((
++/FL2/Electron Diagnostic/Undulator setting/SASE14 gap
++)))
++|(((
++TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH
++)))|(((
++/FL2/Electron Diagnostic/Undulator setting/set wavelength
++)))
--{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
--DAQ channel:  {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
--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 % ...
--units: nm
--
--{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE14 gap{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
--DAQ channel:  {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
--desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper
--units: mm
--
--The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall.
--
  =====
--arrival time (BAM) =====
++arrival time =====
--{{info title="BAM information: updates 2022"}}
--* 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"]]
--* The data format of the BAM has been completely altered in the 2022 shutdown
--* 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 ...
--* 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)
--* There has been also a renaming  (and relocation) of the BAMs.
--** acc:  4DBC3 → FL0.DBC2
--** FL1: 1SFELC →  FL1.SFELC
--** FL2: 8FL2XTDS → (% style="color: rgb(23,43,77);" %)FL2.SEED5
--* for more Info: [[LINK to detailed infos from MSK>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||shape="rect"]]
--* [[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}}
--
--\\
--
--{{expand title="Discontinued BAM format (used until end 2021)"}}
--(% style="color: rgb(0,0,0);" %)**Discontinued BAM data recording **
--
--{{code language="none"}}/FL2/Electron Diagnostic/BAM/8FL2XTDS/electron bunch arrival time (low charge){{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/8FL2XTDS/LOW_CHARGE_ARRIVAL_TIME{{/code}}
--DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/8FL2XTDS.LOW_CHARGE_ARRIVAL_TIME{{/code}}
--desc: Electron bunch arrival time measured with the BAM after the FLASH2 undulator (pulse resolved data)
--units: ps (bigger numbers indicate later arrivaltime of the electrons)
--
--**FL1**{{code language="none"}}//Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
--//always saved (PBD2)//
++{{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
++//always saved (PBD)//
  DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
  DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
--desc: Electron bunch arrival time measured with the BAM  in the accelerator  (pulse resolved data)
--units: ps (bigger numbers indicate later arrivaltime of the electrons)
++desc: Electron bunch arrival time measured with the BAM (more or less) before the undulator (pulse resolved data)
++units: ps (bigger numbers indicate later arrivaltime of the electrons)
++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>>url:https://confluence.desy.de/download/attachments/134216957/BAM-basics_and_outlook-2018_DESY-template_16-9Format.pdf?version=1&modificationDate=1565162143328&api=v2||shape="rect"]]
  \\
--{{info title="BAM hints"}}
--* 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: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~|~|width="13" height="12"~]~]>>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}}
--{{/expand}}
--
  \\
--====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
--
--(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time   (HDF5 name not yet implemented - see zraw)(%%)
--//always saved (PBD)//
--**FL0.DBC2**
--(% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA2.COMP
--{{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).
--units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
--
  \\
--(% 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}}(%%)
--//always saved (PBD)//
--{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE{{/code}}
--(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE {{code language="none"}}DAQ channel: {{/code}}(%%)
--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).
--units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
++===== electron bunch energy =====
++{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/average electron energy{{/code}}
++_always saved (PBD)
++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(%%)
  \\
--(% style="color: rgb(255,102,0);" %)DBC2/error  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
--//always saved (PBD)//
--(% style="color: rgb(0,0,0);" %)E.bamError{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
--(% style="color: rgb(0,0,0);" %)FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR{{code language="none"}}DAQ channel: {{/code}}(%%)
--desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
++{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
++_always saved (PBD)
++DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD{{/code}}
++DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_SPECT{{/code}}
++desc: electron bunch energy bunch resolved
++units: (% class="twikiNewLink" %)MeV
  \\
--(% style="color: rgb(255,102,0);" %)DBC2/status  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}(%%)
--//always saved (PBD)//
--(% style="color: rgb(0,0,0);" %)E..bamStatus.//2//{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIM{{/code}}(%%)
--(% style="color: rgb(0,0,0);" %): FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2{{code language="none"}}DAQ channel{{/code}}(%%)
--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
--
++{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average{{/code}}
++_always saved (PBD)
++DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL{{/code}}
++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
  \\
--====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ======
++[[Contents>>doc:||anchor="Contents"]]
--/FL2/Electron Diagnostic/BAM/**SEED5**(% style="color: rgb(255,102,0);" %)/electron bunch arrival time   (HDF5 name not yet implemented - see zraw)
--
--//always saved (PBD)//
--(% style="color: rgb(23,43,77);" %)**FL2.SEED5**(%%)
--(% 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
--{{code language="none"}} DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ {{/code}}(%%)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).
--units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
--
  \\
--\\
++==== Timing information, rep rate etc.  (FLASH1) ====
--(% 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}}(%%)
--//always saved (PBD)//
--(% style="color: rgb(23,43,77);" %)**FL2.SEED5**{{code language="none"}}DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE{{/code}}(%%)
--**~ **(% 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}}(%%)
--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).
--units: fs (bigger numbers (typically) indicate later arrival times of the electrons).
++===== bunch repetition rate =====
--\\
--
--(% 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}}(%%)
++{{code language="none"}}/FL1/Timing/repetition rate{{/code}}
  //always saved (PBD)//
--(% 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}}(%%)
--(% 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}}(%%)
--desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
--
++DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}}
++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
  \\
--(% 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}}(%%)
++===== set number of pulses =====
++
++{{code language="none"}}/FL1/Timing/set number of bunches{{/code}}
  //always saved (PBD)//
--(% 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}}(%%)
--(% 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}}(%%)
--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
++DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH1{{/code}}
++DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_NUM{{/code}}
++desc: Number of pulses set at the gun (FLASH1)
++units:
--\\
--
--[[Contents>>doc:||anchor="Contents"]]
--
--\\
--
--==== Timing information, rep rate etc.  (FLASH2) ====
--
--===== start time of FLASH2 =====
--
--{{code language="none"}}/FL2/Timing/start time flash2{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
--DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
--desc: The max 600 µs acceleration time of FLASH is devided between FLASH1 and FLASH2. This 600 µs window starts with FLASH1 (up to now)  at a time"label" of 700 µs (for historic reasons). Thus the first bunch of FLASH 1 comes at "700" and the last possibel bunch comes at 1300 (700+600). After FLASH1 train is over ther is a about 70µs switching time with no bunches. Then comes the first FLASH2 bunch.  Thus if e.g. the start time of FLASH2 is 1200 it means that FLASH2 starts at column 500 (1200-700)  in the HDF5 files. (However for yet unknown reasons this may change by 2-3 colums ...)
--units: µs
--
--===== bunch repetition rate =====
--
--{{code language="none"}}/FL2/Timing/repetition rate{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
--DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
--desc: repetition rate of the bunches / pulses within the burst (FLASH2)
--units: kHz
--
  ===== actual number of pulses =====
  {{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
--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)
++//always saved (PBD)//
++DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/12EXP/NUMBEROFBUNCHES.FLASH1{{/code}}
++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:
  \\
@@ -1184,10 +1184,10 @@
  ===== actual pulse pattern recorded after the undulator =====
  {{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
--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)
++//always saved (PBD)//
++DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
++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 toroide diagnostic BEHIND the undulator. (FLASH1)
  units:
  \\
@@ -1194,7 +1194,7 @@
  ===== Train ID =====
  {{code language="none"}}/Timing/train ID{{/code}}
--//always saved (PBD2)//
++//always saved (PBD)//
  DOOCS prop : {{code language="none"}}none{{/code}}
  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 !)
@@ -1203,16 +1203,13 @@
  ===== Train time =====
--//always saved (PBD2)
--//{{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 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}}
--
--//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
++{{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
  \\
@@ -1221,176 +1221,209 @@
  \\
--==== User Data (FLASH2) ====
--
--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.
--
--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
--
--The most common and permanently installed device used by experiment are our ADCs:
--
--===== GHz ADCs =====
--
--ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found** [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]**
--//saved on DEMAND in the user DAQ//
--\\Up to now there are 4 channels available at FL24
--\\\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD{{/code}}
--{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH01/TD{{/code}}
--\\{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH02/TD{{/code}}{{code language="none"}}/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH03/TD{{/code}}
--
  \\
--DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00/CH00.TD  or CH00.DAQ.TD{{/code}}
--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.
--DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00{{/code}}
--
--In addition there are also additional parameters saved like:
--
--* {{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.
--* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
--* {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error
--* {{code language="none"}}/CH0-CH3/offset{{/code}}: To use the full dynamic range of the ADC one can shift the base line . This offset is saved here.
--
--===== MHz ADCs =====
--
--similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
--{{code language="none"}}/FL2/Experiment/MTCA-EXP1/SIS8300 100MHz ADC/CH2/TD{{/code}}
--DOOCS prop : FLASH.FEL/ADC.SIS.FL2EXP1/FL2EXP1.CH02/CH00.TD
--DAQ channel: : FLASH.FEL/ADC.SIS.FL2EXP1/FL2EXP1.CH02
--
--In addition there are also additional parameters saved like:
--
--* {{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.
--* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
--
--[[Contents>>doc:||anchor="Contents"]]
--
  \\
  \\
--==== Pump Probe Laser (FLASH2) ====
--
--There may be more information available from the "Laser DAQ". laese contact your Laser Local Contact.
--
  \\
--**User delay**
--
--Delay (set value):
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR{{/code}}
--
--Delay (encoder readback):
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD{{/code}}
--
--OXC. jitter:
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD{{/code}}
--
  \\
--**Pulse resolved energy:**
--
--1a) OPCPA output:
--
--{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH23.TD{{/code}}
--
--1b) OPCPA energy from PES (only fast channel):
--
--FLASH.LASER/CPUULGAN1.PULSEENERGY/OPCPA_Output/DAQ_CHANNEL
--
--2a) Upper breadboard Photodiode (THG) burst:
--
--{{code language="none"}}FLASH.LASER/TAMC532DMA/ULGAN1/CH26.TD{{/code}}
--
--2b) Upper breadboard Photodiode (THG) energy (in-coupling user photodiode, fast)
--
--{{code language="none"}}FLASH.LASER/MOD24.PES/FL24_userPD/DAQ_CHANNEL{{/code}}
--
  \\
--**Attenuator angle:**
++(% class="wrapped" %)
++|=(((
++DAQ name
++)))|=(((
++HDF5 name
++)))
++|(((
++FLASH.UTIL/FL2.UND.MOTOR/FL2SASE3/GAP
++)))|(((
++/FL2/Electron Diagnostic/Undulator setting/SASE03 gap
++)))
++|(((
++FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP
++)))|(((
++/FL2/Electron Diagnostic/Undulator setting/SASE14 gap
++)))
++|(((
++TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH
++)))|(((
++/FL2/Electron Diagnostic/Undulator setting/set wavelength
++)))
++|(((
++FLASH.FEL/XGM.PHOTONFLUX/FL2.HALL/PHOTONFLUX.UJ
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average energy/hall
++)))
++|(((
++FLASH.FEL/XGM.PHOTONFLUX/FL2.HALL/PHOTONFLUX
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average energy/hall (raw)
++)))
++|(((
++FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average energy/tunnel
++)))
++|(((
++FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average energy/tunnel (raw)
++)))
++|(((
++FLASH.FEL/XGM.POSMON/FL2.HALL/IX.POS
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average beam position/position hall horizontal
++)))
++|(((
++FLASH.FEL/XGM.POSMON/FL2.HALL/IY.POS
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average beam position/position hall vertical
++)))
++|(((
++FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average beam position/position tunnel horizontal
++)))
++|(((
++FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS
++)))|(((
++/FL2/Photon Diagnostic/GMD/Average beam position/position tunnel vertical
++)))
++|(((
++FLASH.FEL/XGM.BPM/FL2.HALL:0
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall horizontal
++)))
++|(((
++FLASH.FEL/XGM.BPM/FL2.HALL:1
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall vertical
++)))
++|(((
++FLASH.FEL/XGM.BPM/FL2.TUNNEL:0
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel horizontal
++)))
++|(((
++FLASH.FEL/XGM.BPM/FL2.TUNNEL:1
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel vertical
++)))
++|(((
++FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL:1
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy aux tunnel
++)))
++|(((
++FLASH.FEL/XGM.INTENSITY/FL2.HALL
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy hall
++)))
++|(((
++FLASH.FEL/XGM.INTENSITY/FL2.HALL:0
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy hall
++)))
++|(((
++FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel
++)))
++|(((
++FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL:0
++)))|(((
++/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel
++)))
++|(((
++FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042
++)))|(((
++/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean phtoton energy
++)))
++|(((
++FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040
++)))|(((
++/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean wavelengt
++)))
++|(((
++FLASH.FEL/ADC.ADQ/OPIS1.CH02
++)))|(((
++/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Raw data/CH02
++)))
++|(((
++FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2
++)))|(((
++/FL2/Electron Diagnostic/Bunch charge/after undulator
++)))
++|(((
++FLASH.DIAG/PBD2.TOROID.ML/3GUN/CHARGE.FLASH2
++)))|(((
++/FL2/Electron Diagnostic/Bunch charge/at gun
++)))
++|(((
++FLASH.FEL/FL20T.PH.MOTOR/MOTOR1.MOT1/FPOS
++)))|(((
++/FL2/Beamlines/Tunnel Apertures/position aperture1 horizontal
++)))
++|(((
++FLASH.FEL/FL20T.PH.MOTOR/MOTOR2.MOT1/FPOS
++)))|(((
++/FL2/Beamlines/Tunnel Apertures/position aperture1 vertical
++)))
++|(((
++FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER
++)))|(((
++/FL2/Beamlines/FL20/Shutter/channel 0
++)))
++|(((
++FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00
++)))|(((
++/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD
++)))
++|(((
++FLASH.FEL/ADC.SIS.FL2EXP1/FL2EXP1.CH00
++)))|(((
++/FL2/Experiment/MTCA-EXP1/SIS8300 100MHz ADC/CH0/TD
++)))
++|(((
++FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD
++)))|(((
++/FL2/Experiment/Pump probe laser/Synchronization/timing jitter RMS
++)))
++|(((
++FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/LOCK_STATUS.VALUE.RD
++)))|(((
++/FL2/Experiment/Pump probe laser/Synchronization/timing jitter RMS GECCO
++)))
++|(((
++FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION.RD
++)))|(((
++/FL2/Experiment/Pump probe laser/laser delay readback
++)))
++|(((
++FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION_SET.WR
++)))|(((
++/FL2/Experiment/Pump probe laser/laser delay set value
++)))
++|(((
++FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS
++)))|(((
++/FL2/Experiment/Pump probe laser/FL24/attenuator position
++)))
++|(((
++FLASH.FEL/FLAPP2BEAMLINES/MOTOR2.FL24/POS
++)))|(((
++/FL2/Experiment/Pump probe laser/FL24/polarization position
++)))
--{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
--
--**Polarization control:**
--
--{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL24/FPOS{{/code}}
--
--**SysDC delay error:**
--
--{{code language="none"}}FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26{{/code}}
--
  \\
--**Timing error: (these two need to be observed and both=0 means no error)**
--
--{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dT_alarm{{/code}}
--
--{{code language="none"}}FLASH/CPUULGAN1.TIMING/ULGAN1/dMPN{{/code}}
--
--**Laser error status:**
--
--\\
--
--**Virtual camera X and Y history, beam size: (use slow data)**
--
--{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.X{{/code}}
--
--{{code language="none"}}FLASH.LASER/MOD24.BEAMPOS/UV.VF_BP/CENTER.Y{{/code}}
--
--{{code language="none"}}FLASH.LASER/MOD24.CAM/UV.14.VF/ROI_SPECTRUM.X.SIG{{/code}}
--
--\\
--
--{{expand title="Parameters used until 2021"}}
--
--{{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/attenuator position{{/code}}//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
--DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
--desc: attenuation of the PPLaser in the FL24 hutch (rotation of a waveplate)
--units : deg.
--
--\\
--
--
--{{code language="none"}}/FL2/Experiment/Pump probe laser/FL24/polarization position{{/code}}//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR2.FL24/FPOS{{/code}}
--DAQ channel: {{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR2.FL24/FPOS{{/code}}
--desc: attenuation of the PPLaser in the FL24 hutch (rotation of a waveplate)
--units : deg.
--
--\\
--
--{{code language="none"}}/FL1/Experiment/Pump probe laser/laser delay readback{{/code}}
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION.RD{{/code}}
--DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/FMC0.MD22.0.POSITION.RD{{/code}}
--desc: delay of the Pump probe laser - measured by the read back position of the motor. There is also the set value available ( upto now these values are only updating every 1-2 seconds. There is no fast encoder property as on FLASH1 available)
--units : ps )
--
--\\
--
--{{code language="none"}}/FL1/Experiment/Pump probe laser/Synchronization/timing jitter RMS{{/code}}
--//always saved (PBD)//
--DOOCS prop : {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}}
--DAQ channel: {{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/FLASH2.PPL1.OSC1/CURRENT_INPUT_JITTER.RD{{/code}}
--desc: rms jitter of the fs-Oscillator
--units: fs
--{{/expand}}
--
  [[Contents>>doc:||anchor="Contents"]]
--\\
--
--=== "/uncategorized/" ===
--
-- 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 their DOOCS names
--
--\\
--
  === HDF5 structure revisions ===
  Starting with Beamblock 4, August 2018, the hierarchy of the HDF group names have been adapted to reflect the new situation at FLASH. FLASH2 is operating for users quite some time now. Therefore, both accelerators appear equally in their respective HDF groups, namely "/FL1" and "/FL2". The root group of proper, by run organised HDF files have an attribute called "version". This version attribute has changed from "0.2.x" to "0.3.x". The changes in detail:
@@ -1505,6 +1505,72 @@
  [[Contents>>doc:||anchor="Contents"]]
  \\
--{{/layout-cell}}
--{{/layout-section}}
--{{/layout}}
++
++== Example code showing how to access HDF5 files ==
++
++\\
++
++=== Samples how to read HDF5 with Matlab ===
++
++The examples apply to HDF files with HDF tree version before vers. 0.3.0.
++
++(% 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
++
++(% 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
++
++(% style="color: rgb(0,128,0);" %)% read a Number per 10 Hz pulse train:
++
++(% class="code" %)
++(((
++FEL_Wavelength_energy_server=h5read(hdf5file,'/Photon Diagnostic/Wavelength/Calculated by energy/wavelength' );
++)))
++
++(% 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');
++
++(% 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)
++
++\\
++
++(% class="code" %)
++(((
++Start_event= 500 ;   % define the first 10 Hz event
++ Number_of_events = 20; % how many 10 Hz events to load
++)))
++
++(% style="color: rgb(0,128,0);" %)% read only part of the data:
++
++(% class="code" %)
++(((
++Gotthard_data=h5read(hdf5file,'/Experiment/Gotthard1/BL.0',[2   650 Start_event],[50 85 Number_of_events]);
++)))
++
++(% 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 ]
++
++(% class="code" %)
++(((
++VLS_Spectrum=h5read(hdf5file,'/Photon Diagnostic/Wavelength/VLS online spectrometer/PCO.ROI.X',[400 Start_event],[200 Number_of_events] );
++
++)))
++
++(% 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 ]
++
++(% style="color: rgb(0,128,0);" %)%GMD data
++
++(% class="code" %)
++(((
++GMD_Spectrum=h5read(hdf5file,'/Photon Diagnostic/GMD/Pulse resolved energy/energy BDA',[1 Start_event],[40 Number_of_events] );
++)))
++
++[[Contents>>doc:||anchor="Contents"]]
++
++=== How to read HDF5 with Python via FLASHH5 ===
++
++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.
++
++\\
++
++== HDF5 and DOOCS ==
++
++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
++
++[[Contents>>doc:||anchor="Contents"]]

Changes for page The FLASH HDF5 structure

Summary

Details

Applications

Navigation