Changes for page The FLASH HDF5 structure

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

From 44.1 to 43.1 From 79.1 to 78.1

From version 78.1

edited by sndueste
on 2023/11/01 16:51

Change comment: There is no comment for this version

To version 44.1

edited by cpassow
on 2021/02/10 09:30

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)
Attachments (0 modified, 0 added, 11 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.sndueste
++XWiki.cpassow

Tags

...	...	@@ -1,1 +1,0 @@
1		-favourite\|data\|hdf5\|analysis\|offline

Content

@@ -19,18 +19,14 @@
  {{code language="none"}}> module load xray{{/code}}
  {{code language="none"}}> hdfview{{/code}}
--or you can use
++[[Contents>>doc:||anchor="Contents"]]
--{{code language="none"}}> silx view{{/code}}
++== The new (starting 2021) HDF5 format ==
  \\
--[[Contents>>doc:||anchor="Contents"]]
++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 FLASH HDF5 format ==
--
--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 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.
  Reference implementation, which follows the concept of Python libraries like Pandas, Xarray, or Dask, is given below.
@@ -38,7 +38,7 @@
  \\
  {{expand title="Discontinued HDF formats"}}
--=== Comparison to FLASH's deprecated 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.
@@ -47,25 +47,9 @@
  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)**
--
--Here we have a few HDF5 samples (User data combined with Photon diagnostics data) from a few beamtimes showing the different kind options.
--
--[[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: ===
++=== HDF excerpt: ===
  {{/layout-cell}}
  {{/layout-section}}
@@ -79,10 +79,12 @@
  {{/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}})
++* The //average// FEL pulse energy as example for the **slow** **data** (different e.g. 1 Hz):
--           ( as example only every 10th train ID is listed in the HDF group "index")
++           ( every 10th train ID is listed in the HDF group "index")
++\\
++
  [[image:attach:image2020-11-16_15-31-45.png||height="250"]]
  {{/layout-cell}}
@@ -101,13 +101,12 @@
  {{layout-section ac:type="single"}}
  {{layout-cell}}
--{{info}}
--===  There are different options that help you to work with the FLASH HDF5 data in Python ===
++{{info title="Sample scripts in python"}}
++=== Reference implementation (Python) ===
--* The currently developed option for large data sets: [[the FAB package>>url:https://hasfcpkg.desy.de/fab/fab.html||shape="rect"]] ... see below
--* and for smaller projects:   (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]]
++[[~[~[image:attach:binder_badge.png~|~|thumbnail="true" width="120"~]~]>>url:https://mybinder.org/v2/git/https%3A%2F%2Fgitlab.desy.de%2Fchristopher.passow%2Fflash-daq-hdf/master||shape="rect"]]
--(% class="Object" %)See also the collection of Demo data and sample scripts : [[doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).Collection of HDF5 sample data from different beamlines.WebHome]] and [[doc:FLASHUSER.Data Acquisition and controls.Data Access at FLASH (DAQ, gpfs,\.\.\.).Offline data analysis (DAQ).DEMO - Working with FLASH data.WebHome]]
++(% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]]
  {{/info}}
  {{/layout-cell}}
  {{/layout-section}}
@@ -114,17 +114,49 @@
  {{layout-section ac:type="single"}}
  {{layout-cell}}
--
++== The discontinued (till 2021) FLASH HDF5 structure ==
--== Complete list of recordable parameters ==
++The photon diagnostic, electron diagnostic and beamline information as well as the information about the pump-probe laser and the infrastructure offered for users (GHz/MHz ADCs) can be included in one HDF5 file which is organized according to train IDs. The general structure is:
--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"]].
++* Electron Diagnostic
++* Photon Diagnostics
++* Beamlines
++* Experiment
++* Timing
++[[image:attach:HDF5_structure.jpg||height="400"]]
++
++A detailed description of (most) channels can be found in the lower part of the hdf5 viewer:
++[[image:attach:HDF5_structure_desc.jpg||thumbnail="true" height="250"]]
++
++[[Contents>>doc:||anchor="Contents"]]
++
  \\
++=== HDF5 example files (old format) ===
++
++Here we have a few HDF5 samples (User data combined with Photon diagnostics data) from a few beamtimes showing the different kind options.
++
++[[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"]]
++
++\\
++
++\\
++
++[[Contents>>doc:||anchor="Contents"]]
++
++\\
++
  == Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ  ==
  {{id name="DOOCSparameters"/}}
++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:
++
  Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
  \\
@@ -131,6 +131,8 @@
  === FLASH1 ===
++\\
++
  ==== Beamline info (FLASH1) ====
  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
@@ -207,7 +207,8 @@
  ==== Photon Diagnostics SASE ([[GMD>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/gmd_intensity_and_position/index_eng.html||shape="rect"]]) ====
--{{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}}
@@ -255,11 +255,10 @@
  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}}
  \\
--(% style="letter-spacing: 0px; color: rgb(0, 0, 0)" %)**NEW (since 2021) GMD data recording / evaluation  (same format as FLASH2 and XFEL)**
++(% style="color: rgb(0,0,0);" %)**NEW (2021) GMD data recording / evaluation  (MTCA, analog to FLASH2 and XFEL)**
  {{code language="none"}}/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel{{/code}}
  //always saved (PBD)//
@@ -417,27 +417,8 @@
  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}}
@@ -445,94 +445,22 @@
  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)
--\\
--
  {{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}}
++units: ps (bigger numbers indicate later arrivaltime of the electrons)
--====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
++{{info title="BAM hints"}}
++* besides the arrivaltime from FLASH1 there is also the FLASH2/3 electron arrival time saved.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}}
--(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time   (HDF5 name not yet implemented - see zraw)(%%)
--//always saved (PBD)//
--{{code language="none"}}/FL1/Electron Diagnostic/BAM/ {{/code}}DOOCS prop : FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
--DAQ (% style="color: rgb(0,0,0);" %)channel: FLASH.SDIAG/BAM/**FL0.DBC2**/ARRIVAL_TIME.ABSOLUTE.SA1.COMP (%%)
--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  still may have arbitrary numbers looking like a signal which they are not ). 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"}}/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 still may have arbitrary numbers looking like a signal which they are not). 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}}
@@ -603,11 +603,11 @@
  ===== set number of pulses =====
--(% style="color: rgb(255, 0, 0); color: rgb(255, 102, 0)" %)(HDF5 name not yet implemented - see zraw)(% style="color: rgb(255,0,0);" %){{code language="none"}}/FL1/Timing/set number of bunches {{/code}}(%%)
++{{code language="none"}}/FL1/Timing/set number of bunches{{/code}}
  //always saved (PBD)//
--DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
--DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]{{/code}}
--desc: Number of bunches set in the control (timing) system.  The property contains 4 numbers. the last one is the number of pulses (see also [[doc:FLASH.Timing properties]] (internal link)).    If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated and thus the actual number of pulses may be smaller than the set one
++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:
  ===== actual number of pulses =====
@@ -626,7 +626,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:
  \\
@@ -659,43 +659,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)//
@@ -736,8 +736,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
  \\
@@ -747,7 +747,7 @@
  ==== 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.
++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
@@ -775,13 +775,13 @@
  {{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:
  * {{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"}}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
  ===== MHz ADCs =====
@@ -794,7 +794,7 @@
  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"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
  [[Contents>>doc:||anchor="Contents"]]
@@ -955,7 +955,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
  \\
@@ -969,11 +969,11 @@
  \\
--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 ...
  \\
@@ -992,21 +992,8 @@
  \\
--===== electron bunch energy =====
++===== undulator settings =====
--{{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
--
  {{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}}
@@ -1024,27 +1024,8 @@
  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}}
@@ -1069,94 +1069,8 @@
  * [[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){{code language="none"}}/FL2/Electron Diagnostic/BAM/{{/code}}
--
--{{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.DBC2.ARRIVAL_TIME.ABSOLUTE.SA2.COMP/dGroup/{{/code}}
--
--//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"}} 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 still may have arbitrary numbers looking like a signal which they are not0). 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}}
--
--{{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.DBC2.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/{{/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).
--
--\\
--
--(% 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 !!
--
--\\
--
--(% 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
--
--\\
--
--====== **BAM FL2.SEED5**{{code language="none"}}{{/code}} ======
--
--/FL2/Electron Diagnostic/BAM/**SEED5**(% style="color: rgb(255,102,0);" %)/electron bunch arrival time   (HDF5 name not yet implemented - see zraw)
--
--(% style="color: rgb(0,0,0);" %){{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2.COMP/dGroup/{{/code}}
--
--//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 still may have arbitrary numbers looking like a signal which they are not). 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);" %)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}}
--
--(% style="color: rgb(0,0,0);" %){{code language="none"}}/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/{{/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).
--
--\\
--
--(% 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}}(%%)
--//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 !!
--
--\\
--
--(% 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}}(%%)
--//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
--
--\\
--
  [[Contents>>doc:||anchor="Contents"]]
  \\
@@ -1181,17 +1181,6 @@
  desc: repetition rate of the bunches / pulses within the burst (FLASH2)
  units: kHz
--\\
--
--===== set number of pulses =====
--
--(% style="color: rgb(255, 0, 0); color: rgb(255, 102, 0)" %)(HDF5 name not yet implemented - see zraw)(% style="color: rgb(255,0,0);" %){{code language="none"}}/FL2/Timing/set number of bunches {{/code}}(%%)
--//always saved (PBD2)//
--DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]{{/code}}
--DAQ channel: {{code language="none"}}FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]{{/code}}
--desc: Number of bunches set in the control (timing) system.  The property contains 4 numbers. the last one is the number of pulses (see also [[doc:FLASH.Timing properties]] (internal link)).    If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated and thus the actual number of pulses may be smaller than the set one
--units:
--
  ===== actual number of pulses =====
  {{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
@@ -1290,129 +1290,11 @@
  \\
--==== FL 24 Pump Probe Laser (FLASH2) ====
++==== Pump Probe Laser (FLASH2) ====
--These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**//
++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 (readback):
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD{{/code}}
--
--(% style="letter-spacing: 0.0px;" %)Delay (encoder readback):
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.ENCODER_POSITION.RD{{/code}}
--
--OXC. jitter:
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD{{/code}}
--
--\\
--
--\\
--
--**FL24 Pulse resolved energy:**
--
--OPCPA output (photodiode signal raw ADC trace 16000 samples):
--
--{{code language="none"}}/zraw/FLASH.LASER/FLASH2CPUULGAN1.ADCSCOPE/CH23.TD/dGroup{{/code}}
--
--(% style="letter-spacing: 0.0px;" %)Upper breadboard Photodiode (THG) burst (photodiode signal raw ADC trace 16000 samples)::
--
--{{code language="none"}}/zraw/FLASH.LASER/FLASH2CPUULGAN1.ADCSCOPE/CH26.TD/dGroup{{/code}}
--
--Upper breadboard Photodiode (THG) energy (analyzed signal. integration over pulses in the ADC trace. contains for each laser pulse the pulse energy in a.u.)
--
--{{code language="none"}}/zraw/FLASH.LASER/MOD24.PES/FL24_userPD/dGroup{{/code}}
--
--\\
--
--**FL24 LAM (Laser Arrivaltime Monitor)  pulse resolved data:**
--
--Signal of Photodiode1  - for experts only... (analyzed signal. integration over pulses in the ADC trace. )
--
--{{code language="none"}}/zraw/FLASH.LASER/MOD24.PES/LAM.PD1/dGroup{{/code}}
--
--Signal of Photodiode2  - for experts only...  (analyzed signal. integration over pulses in the ADC trace.)
--
--{{code language="none"}}/zraw/FLASH.LASER/MOD24.PES/LAM.PD2/dGroup{{/code}}
--
--"Actual" LAM Signal - to be calibrated ......  (analyzed signal. integration over pulses in the ADC trace.)
--
--{{code language="none"}}/zraw/FLASH.LASER/MOD24.PES/LAM.PDBAL/dGroup{{/code}}
--
--The delay feedback(% style="letter-spacing: 0.0px;" %)
--
--{{code language="none"}}FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26 {{/code}}
--
--The LAM delay feedback(% style="letter-spacing: 0.0px;" %) (the pulse energy signal, which is saved in the above but maybe it’s good to have this also as slow, in the case these two numbers are not the same the sysdc was active instead of the LAM):
--
--{{code language="none"}}FLASH.LASER/MOD24.PES/LAM.PDBAL/PULSEENERGY.MEAN{{/code}}
--
--LAM Delay line act:
--
--{{code language="none"}}FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.POSITION.RD{{/code}}
--LAM Delay line set:
--
--{{code language="none"}}FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.POSITION_SET.WR{{/code}}
--
--LAM Delay line encoder:
--
--{{code language="none"}}FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.1.ENCODER_POSITION.RD{{/code}}
--
--Temperature feedback:
--
--{{code language="none"}}FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE24{{/code}}
--
--**Feedback mode** (if this is not =1 the delay FB is not active, then it’s either temp feedback controlled or failsave, maybe it’s good to have):
--
--{{code language="none"}}FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.INTS/INTEGER30{{/code}}
--
--\\
--
--**FL24 Attenuator angle:**
--
--{{code language="none"}}FLASH.FEL/FLAPP2BEAMLINES/MOTOR1.FL24/FPOS{{/code}}
--
--**FL24 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:**
--
--\\
--
--**FL24 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}}
@@ -1445,172 +1445,7 @@
  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}}
--\\
--
--==== FL 26 Pump Probe Laser (FLASH2) ====
--
--These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL26**//
--
--\\
--
--**User delay**
--
--Delay (set value):
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION_SET.WR{{/code}}
--
--Delay (readback):
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD{{/code}}
--
--Delay (encoder readback):
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.ENCODER_POSITION.RD{{/code}}
--
--OXC. jitter:
--
--{{code language="none"}}FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD{{/code}}
--
--\\
--
--**Parameters for FL26**
--
--(% class="wrapped" %)
--|(((
--FL2PPL FL26 REMI Attenuation: HWP motor current position
--)))|(((
--FLASH.FEL/FLAPP2BEAMLINES/MOTOR11.FL26B/FPOS
--)))
--|(((
--FL2PPL FL26 REMI Polarization: linear polarization angle
--)))|(((
--FLASH.FEL/FLAPP2BEAMLINES/MOTOR12.FL26B/FPOS
--)))
--|(((
--FL2PPL FL26 REMI Diagnostics: NIR spectrum
--)))|(((
--FLASH.LASER/MOD26.SPECT/REMI/DAQ_CHANNEL
--)))
--|(((
--FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - pulse energy mean
--)))|(((
--FLASH.LASER/MOD26.PES/RE_OUT/PULSEENERGY.MEAN
--)))
--|(((
--FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - intra burst pulse energy
--)))|(((
--FLASH.LASER/MOD26.PES/RE_OUT/DAQ_CHANNEL
--)))
--|(((
--FL2PPL FL26 REMI Diagnostics: photo diode input MOD2.6 - raw adc
--)))|(((
--FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH04.TD
--)))
--|(((
--FL2PPL FL26 REMI Diagnostics: photo diode input REMI - pulse energy mean
--)))|(((
--FLASH.LASER/MOD26.PES/INC_BOX/PULSEENERGY.MEAN
--)))
--|(((
--FL2PPL FL26 REMI Diagnostics: photo diode input REMI - intra burst pulse energy
--)))|(((
--FLASH.LASER/MOD26.PES/INC_BOX/DAQ_CHANNEL
--)))
--|(((
--FL2PPL FL26 REMI Diagnostics: photo diode input REMI - raw adc
--)))|(((
--FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH05.TD
--)))
--|(((
--FL2PPL FL26 REMI In coupling: filter wheel 1 position
--)))|(((
--FLASH/MOD26.FW1/FLASH2MOD26/pos
--)))
--|(((
--FL2PPL FL26 REMI In coupling: filter wheel 2 position
--)))|(((
--FLASH/MOD26.FW2/FLASH2MOD26/pos
--)))
--|(((
--FL2PPL FL26 REMI: Energy meter REMI incoupling breadboard
--)))|(((
--FLASH.LASER/MOD26.OPHIRE/REINC.54/DAQ_CHANNEL
--)))
--|(((
--FL2PPL FL26 REMI Incoupling: focusing lens position
--)))|(((
--FLASH.FEL/FLAPP2BEAMLINES/MOTOR3.FL26B/FPOS
--)))
--|(((
--FL2PPL FL26 REMI Incoupling: nearfield
--)))|(((
--FLASH.LASER/MOD26.CAM/REINC.21.NF/DAQ_CHANNEL
--)))
--|(((
--FL2PPL FL26 REMI Incoupling: focus
--)))|(((
--FLASH.LASER/MOD26.CAM/REINC.22.FF/DAQ_CHANNEL
--)))
--|(((
--FL2PPL FL26 REMI Drift: relative arrival time intra burst LAM balanced - calb. in the PES
--)))|(((
--FLASH.LASER/MOD26.PES/LAM_DIFF/DAQ_CHANNEL
--)))
--|(((
--FL2PPL FL26 REMI Drift: forward signal (PD1)  raw
--)))|(((
--FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH00.TD
--)))
--|(((
--FL2PPL FL26 REMI Drift: backward signal (PD2) raw
--)))|(((
--FLASH.LASER/TAMC532DMA/ULGAN1_S5/CH01.TD
--)))
--|(((
--FL2PPL FL26 REMI Drift: mean relative burst arrival time - avarage of the calib value
--)))|(((
--FLASH.LASER/MOD26.PES/LAM_DIFF/PULSEENERGY.MEAN
--)))
--|(((
--FL2PPL FL26 REMI Drift: delay line position (ODL of the LAM REMI)
--)))|(((
--FLASH.FEL/FLAPP2BEAMLINES/MOTOR14.FL26B/FPOS
--)))
--|(((
--FL2PPL FL26 Laser Hutch: delay line position (ODL of the osc. Sync / user delay)
--)))|(((
--FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/FMC0.MD22.0.POSITION.RD
--)))
--|(((
--FL2PPL FL26 REMI Drift: delay line encoder position (ODL REMI raw value)
--)))|(((
--FLASH.SYNC/LAM.EXP.ODL/F2.MOD.AMC12/FMC0.MD22.0.ENCODER_POSITION.RD
--)))
--|(((
--Jiiter between oscillator and MLO (inloop jitter osc. Sync)
--)))|(((
--FLASH.SYNC/LASER.LOCK.EXP/F2.PPL.OSC/CURRENT_INPUT_JITTER.RD
--)))
--|(((
--Temperature controlled fiber (PWM signal to the temperature controlled fiber delay sysdc)
--)))|(((
--FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE23
--)))
--|(((
--Temperature controlled fiber (Temp of the fiber delay sysdc)
--)))|(((
--FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE24
--)))
--|(((
--Sydc feedback data if LAM is not activated (sysdc delay)
--)))|(((
--FLASH.LASER/ULGAN1.DYNPROP/TCFIBER.DOUBLES/DOUBLE26
--)))
--
--\\
--
  [[Contents>>doc:||anchor="Contents"]]
  \\
@@ -1633,7 +1633,6 @@
  \\
--(% class="wrapped" %)
  |=(((
  earlier HDF path (vers. 0.2)
  )))|=(((
@@ -1735,6 +1735,14 @@
  [[Contents>>doc:||anchor="Contents"]]
  \\
++
++== 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"]]
++
++\\
  {{/layout-cell}}
  {{/layout-section}}
  {{/layout}}

BAM-basics and outlook-2018_DESY-template_16-9Format.pdf

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-3.7 MB

Content

FLASH1__DaqChannel2HdfNamePbd.xlsx

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-22.1 KB

Content

HDF5_structure.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-194.1 KB

Content

HDF5_structure_desc.jpg

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-28.3 KB

Content

binder_badge.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-6.6 KB

Content

image2019-10-21_17-2-50.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-977.2 KB

Content

image2019-10-22_10-52-27.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-642.4 KB

Content

image2020-11-16_15-26-28.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-1.1 MB

Content

image2020-11-16_15-31-45.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-890.0 KB

Content

image2020-11-16_16-26-3.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-134.5 KB

Content

image2021-2-9_10-51-6.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.XWikiGuest

Size

...	...	@@ -1,1 +1,0 @@
1		-1.1 MB

Content

Changes for page The FLASH HDF5 structure

Summary

Details

Applications

Navigation