The FLASH HDF5 structure
Unknown macro: layout. Click on this message for details.
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.
Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ
FLASH1
In the Shutdown 2024 / 2025 the complete photon diagnostic and experiment control was renewed and thus the Doocs names and also some HDF5 names had to be changed. The new naming will be documented here as soon as the systems are online again.
The previously used naming scheme (2024 and before) can be found here:
FLASH1 Naming scheme used until 2024
Beamline info (FLASH1)
/FL1/Beamlines/Attenuator/pressure
always saved (PBD)
DOOCS prop : FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE
DAQ channel: FLASH.FEL/GAS_DOSING/FL1.ATTENUATOR/PRESSURE
desc: set pressure in the gas attenuator
units: mbar
/FL1/Beamlines/BL/Fast shutter/open
always saved (PBD)
DOOCS prop : FLASH.FEL/ADC.SIS.FL1FS/BL.SHUTTER/CH00.TD
DAQ channel: FLASH.FEL/ADC.SIS.FL1FS/BL.SHUTTER
desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
units: none
/FL1/Beamlines/PG/Fast shutter/open
always saved (PBD)
DOOCS prop : FLASH.FEL/ADC.SIS.FL1FS/PG.SHUTTER/CH00.TD
DAQ channel: FLASH.FEL/ADC.SIS.FL1FS/PG.SHUTTER
desc: PG Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
units: none
/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 1
always saved (PBD)
DOOCS prop : TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS
DAQ channel: TTF2.FEL/BLFILTERS1/FILTER1/FW.MOTOR.POS
desc: Position of the BL filter wheel 1 - to correlate with the filter material please look here
units: degree
/FL1/Beamlines/BL/Filters/BL filter wheel/position filter 2
always saved (PBD)
DOOCS prop : TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS
DAQ channel: TTF2.FEL/BLFILTERS2/FILTER2/FW.MOTOR.POS
desc: Position of the BL filter wheel 2 - to correlate with the filter material please look here
units: degree
/FL1/Beamlines/PG/Filters/position filter 1
always saved (PBD)
DOOCS prop : = TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS=
DAQ channel: TTF2.FEL/BDAF1/BDA.F1/FW.MOTOR.POS
desc: Position of the PG filter wheel 1
units: degree
/FL1/Beamlines/PG/Filters/position filter 2
always saved (PBD)
DOOCS prop : TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS
DAQ channel: TTF2.FEL/BDAF2/BDA.F2/FW.MOTOR.POS
desc: Position of the PG filter wheel 2
units: degree
/FL1/Beamlines/PG/Filters/position filter 3
always saved (PBD)
DOOCS prop : TTF2.FEL/PGFILTERS/PGFILTERS/FW.MOTOR.POS
DAQ channel: TTF2.FEL/PGFILTERS/PGFILTERS/FW.MOTOR.POS
desc: Position of the PG filter wheel 3
units: degree
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
Photon Diagnostics SASE (GMD)
NEW (since 2021) GMD data recording / evaluation (same format as FLASH2 and XFEL)
/FL1/Photon Diagnostic/GMD/Average energy/energy tunnel
always saved (PBD)
DOOCS prop : FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ
DAQ channel: FLASH.FEL/XGM.PHOTONFLUX/FL1.TUNNEL/PHOTONFLUX.UJ
desc : calibrated average SASE Energy/pulse measured in the TUNNEL upstream the gas attenuator
units : microJ
/FL1/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel
always saved (PBD)
DOOCS prop :
FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TDDAQ channel: FLASH.FEL/XGM.INTENSITY/FL1.TUNNEL/INTENSITY.TD
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
For every pulse in the pulse train the information is saved:
- Intensity per pulse (a.u. (more or less µJ ))
- Intensity per pulse (auxillary GMD) - not used
- Position horizontal (mm, for a single pulse the position information may be very noisy - talk to your local contact)
- Position vertical (mm, for a single pulse the position information may be very noisy - talk to your local contact)
- Intensity per pulse sigma (a.u. (more or less µJ ), 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))
- Position horizontal sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
- Position vertical sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
- 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
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
/FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal
always saved (PBD)
DOOCS prop : FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS
DAQ channel: FLASH.FEL/XGM.POSMON/FL1.BDA/IX.POS
desc :Beam position of the photon Beam determined by the GMD (BDA, x=horizontal)
units : mm
/FL1/Photon Diagnostic/GMD/Beam position/position BDA vertical
always saved (PBD)
DOOCS prop : FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS
DAQ channel: FLASH.FEL/XGM.POSMON/FL1.BDA/IY.POS
desc :Beam position of the photon Beam determined by the GMD (BDA, y=vertical)
units : mm
/FL1/Photon Diagnostic/GMD/Beam position/position tunnel horizontal
always saved (PBD)
DOOCS prop : FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS
DAQ channel: FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IX.POS
desc :Beam position of the photon Beam determined by the GMD (TUNNEL, x=horizontal)
units : mm
/FL1/Photon Diagnostic/GMD/Beam position/position tunnel vertical
always saved (PBD)
DOOCS prop : FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS
DAQ channel: FLASH.FEL/XGM.POSMON/FL1.TUNNEL/IY.POS
desc :Beam position of the photon Beam determined by the GMD (TUNNEL, y=vertical)
units : mm
Spectrometer (FLASH1)
/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength
_always saved (when Spectrum is measured !!) (PBD) _
DOOCS prop : TTF2.EXP/PHOTONWL.ML/WAVE_LENGTH/VAL.TD
DAQ channel: PBD.PHOTONWL.ML/WAVE_LENGTH
desc : XUV Spectrum measured with the "tunnel spectrometer"
units :
/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength start value
_always saved (when Spectrum is measured !!) (PBD) _
DOOCS prop : TTF2.EXP/PBD.PHOTONWL.ML/BSTART/VAL
DAQ channel: TTF2.EXP/PBD.PHOTONWL.ML/BSTART/VAL
desc : start value (in nm) for the wavelength axis of the XUV Spectrum measured with the "tunnel spectrometer"
units : nm
/FL1/Photon Diagnostic/Wavelength/Tunnelspectrometer/wavelength increment
_always saved (when Spectrum is measured !!) (PBD) _
DOOCS prop : ==
DAQ channel: ==
desc : increment value (in nm) for each pixel for the wavelength axis of the XUV Spectrum measured with the "tunnel spectrometer"
units : nm
/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy
saved on DEMAND (PBD spectrometer stream)
DOOCS prop : ==
DAQ channel: PBD.PHOTONEN.ML/PHOTON_ENERGY
desc : XUV Spectrum in eV measured with the "PG2 spectrometer"
units :
/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy start value
saved on DEMAND (PBD spectrometer stream)
DOOCS prop : ==
DAQ channel: ==
desc : start value (in eV) for the wavelength axis of the XUV Spectrum measured with the "PG2 spectrometer"
units : eV
/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon energy increment
saved on DEMAND (PBD spectrometer stream)
DOOCS prop : ==
DAQ channel: ==
desc : increment value (in eV) for each pixel for the wavelength axis of the XUV Spectrum measured with the "PG spectrometer"
units : eV
/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength
saved on DEMAND (PBD spectrometer stream)
DOOCS prop : ==
DAQ channel: PHOTONEN.ML/PHOTON_WAVE_LEN
desc : XUV Spectrum in nm measured with the "PG2 spectrometer"
units :
/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength increment
saved on DEMAND (PBD spectrometer stream)
DOOCS prop : ==
DAQ channel: ==
desc : start value (in nm) for the wavelength axis of the XUV Spectrum measured with the "PG2 spectrometer"
units : nm
/FL1/Photon Diagnostic/Wavelength/PG2 spectrometer/photon wavelength start value
saved on DEMAND (PBD spectrometer stream)
DOOCS prop : ==
DAQ channel: ==
desc : increment value (in nm) for each pixel for the wavelength axis of the XUV Spectrum measured with the "PG spectrometer"
units : nm
Electron Beam properties (FLASH1)
bunch charge
/FL1/Electron Diagnostic/Bunch charge/after undulator
always saved (PBD)
DOOCS prop : FLASH.DIAG/TOROID.ML/12EXP/CHARGE.FLASH1
DAQ channel: FLASH.DIAG/TOROID/12EXP
desc: electron bunch charge (FLASH1)
units: nC
arrival time (BAM)
BAM FL0.DBC2
DBC2/electron bunch arrival time (HDF5 name not yet implemented - see zraw)
always saved (PBD)
/FL1/Electron Diagnostic/BAM/ DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
DAQ 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).
DBC2/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw)/FL1/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE
DAQ channel: 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).
DBC2/error (HDF5 name not yet implemented - see zraw)/FL1/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamError.1
DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.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
DBC2/status (HDF5 name not yet implemented - see zraw)/FL1/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME..bamStatus.1
DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/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
BAM FL1.SFELC
/FL1/Electron Diagnostic/BAM/SFELC/electron bunch arrival time (HDF5 name not yet implemented - see zraw)
always saved (PBD)
FL1.SFELC
channel: FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ 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).
SFELC/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw)/FL1/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.ABSOLUTE
DAQ channel: 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).
SFELC/error (HDF5 name not yet implemented - see zraw)/FL1/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME.bamError
DAQ channel: 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 !!
SFELC/status (HDF5 name not yet implemented - see zraw)/FL1/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL1.SFELC/ARRIVAL_TIME..bamStatus.1
DAQ channel: 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
/FL1/Electron Diagnostic/Electron bunch profile/TDS profile
always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)
DOOCS prop : TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/OUT.PROF.CCCED
DAQ channel: PBD.BEAM.PROF.ML/DAQ.OUT.PROF.CCCED
desc: temporal profile of electron bunch, y axis in Ampers (FLASH1)
units: pixel
/FL1/Electron Diagnostic/Electron bunch profile/Expert stuff/TDS calibration constant
always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)
DOOCS prop : TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/CALIB.CONST.T
DAQ channel: = PBD.BEAM.PROF.ML/CCT=
desc: TDS calibration constant for the x-axis of the profiles: fs per pixel
units: fs per pixel
/FL1/Electron Diagnostic/Electron bunch profile/TDS profile width rms
always saved (PBD) - IF LOLA is ON and ACTIVATED in the PBD DAQ (talk to expert)
DOOCS prop : TTF2.DAQ/BEAM.PROF.ML/BEAM.PROF/SOWS.W.CCTED
DAQ channel: PBD.BEAM.PROF.ML/PROFWIDTHCCTED
desc: rms pulse width of the measures TDS electron bunch profile
units: fs
electron bunch energy
/FL1/Electron Diagnostic/Electron energy/average electron energy
always saved (PBD)
DOOCS prop : TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL
DAQ channel: PBD.ENERGY.DOGLEG/E_MEAN
desc: electron bunch energy (average over the bunch train)
units: MeV
/FL1/Electron Diagnostic/Electron energy/pulse resolved energy
always saved (PBD)
DOOCS prop : TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD
DAQ channel: PBD.ENERGY.DOGLEG/E_SPECT
desc: electron bunch energy bunch resolved
units: MeV
/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average
always saved (PBD)
DOOCS prop : TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL
DAQ channel: PBD.ENERGY.DOGLEG/LAMBDA_MEAN
desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
units: nm
Timing information, rep rate etc. (FLASH1)
bunch repetition rate
/Timing/repetition rate
always saved (PBD)
DOOCS prop : FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1
DAQ channel: FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1
desc: repetition rate of the bunches / pulses within the burst (FLASH1)
units: kHz
set number of pulses
(HDF5 name not yet implemented - see zraw)/Timing/set number of bunches
always saved (PBD)
DOOCS prop : FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]
DAQ channel: FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1 [4th number]
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 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
/FL1/Timing/actual number of bunches
always saved (PBD)
DOOCS prop : FLASH.DIAG/TOROID.ML/12EXP/NUMBEROFBUNCHES.FLASH1
DAQ channel: TTF2.DIAG/PBD.TOROID.ML/12EXP
desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH1)
units:
actual pulse pattern recorded after the undulator
/FL1/Timing/Bunch pattern/pattern after undulator
always saved (PBD)
DOOCS prop : TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD
DAQ channel: TTF2.DIAG/PBD.TOROID.ML/12EXP
desc: The bunch pattern as function of time in a burst recorded by toroid diagnostic BEHIND the undulator. (FLASH1)
units:
Train ID
/Timing/train ID
always saved (PBD)
DOOCS prop : none
DAQ channel: none
desc: Each 10 Hz burst has its unique train ID. For the HDF5 data set the ID is the same for all parameters with the same index (note camera images may be shifted by 1 ID - talk to the experts !)
units:
Train time
/Timing/train time
desc:Local time as array of day, hour, minute, second, and centisecond. This data set is meant for visualization purposes only. For correlations use the train ID or the Unix time of the time stamp
units: d h min s cs
/Timing/time stamp
desc:first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date --date='@1553617729' or matlab, python etc
second column: microseconds
third column: Train ID of FLASH
currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
Pump Probe Laser (FLASH1)
PIGLET (PG laser)
/FL1/Experiment/Pump probe laser
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
saved on DEMAND in the user DAQ
The HDF5 names for the ADC traces are depending on the beamline :
PG Beamline:
/FL1/Experiment/PG/ADQ412 GHz ADC/CH00/TD
/FL1/Experiment/PG/ADQ412 GHz ADC/CH01/TD
/FL1/Experiment/PG/ADQ412 GHz ADC/CH02/TD
/FL1/Experiment/PG/ADQ412 GHz ADC/CH03/TD
BL Beamlines:
/FL1/Experiment/BL1/ADQ412 GHz ADC/CH00/TD
/FL1/Experiment/BL1/ADQ412 GHz ADC/CH01/TD
/FL1/Experiment/BL1/ADQ412 GHz ADC/CH02/TD
/FL1/Experiment/BL1/ADQ412 GHz ADC/CH03/TD
/FL1/Experiment/BL2/ADQ412 GHz ADC/CH00/TD
/FL1/Experiment/BL2/ADQ412 GHz ADC/CH01/TD
/FL1/Experiment/BL3/ADQ412 GHz ADC/CH02/TD
/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD
DOOCS prop : FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD or CH00.DAQ.TD
here the CH00.TD is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the CH00.DAQ.TD trace only has the number of samples which are sent to the DAQ OR if grouping is activated the CH00.DAQ.TD contains only the grouped spectra. To read the ADC trace with an online analysis program the CH00.DAQ.TD is used preferably.
DAQ channel: FLASH.FEL/ADC.ADQ.PG/EXP1.CH00
In addition there are also additional parameters saved like:
- sample frequency: 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.
- number of samples: total number of samples recorded for each 10 Hz trigger
- error (ADC):0 indicates that there was no error
MHz ADCs
similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
/FL1/Experiment/BL1/SIS8300 100MHz ADC/CH2/TD
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:
- sample frequency: 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.
- number of samples: total number of samples recorded for each 10 Hz trigger
FLASH2
There is analog to FLASH1 a permanently running "PhotonDagnostic DAQ FLASH2" (PBD2) and 2 User DAQs
Beamline info (FLASH2)
/FL2/Beamlines/Attenuator/pressure
DOOCS prop : FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE
DAQ channel: FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE
desc: set pressure in the gas attenuator
units: mbar
/FL2/Beamlines/FL20/Shutter/open
DOOCS prop : FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER/CH00.TD
DAQ channel: FLASH.FEL/ADC.SIS.FL2FS/FL20.SHUTTER
desc: BL Beamline Fast shutter state: 1 is open, 0 is closed ( for technical reasons there are 100 vales of this state saved ...)
units: none
/FL2/Beamlines/Filter wheel/position wheel 1
DOOCS prop : FLASH.FEL/FL20H.PH.MOTOR/MOTOR1.MOT3/FPOS
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
units: degree
/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 here
units: degree
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
Photon Diagnostics SASE (XGMD - FLASH2)
/FL2/Photon Diagnostic/GMD/Average energy/energy tunnel
DOOCS prop : FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ
DAQ channel: FLASH.FEL/XGM.PHOTONFLUX/FL2.TUNNEL/PHOTONFLUX.UJ
desc : calibrated average ( ~ 20 sec averaging time ) SASE Energy/pulse measured in the TUNNEL before the attenuator (ion current)
units : microJ
/FL2/Photon Diagnostic/GMD/Pulse resolved energy/energy tunnel
DOOCS prop : FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD
DAQ channel: FLASH.FEL/XGM.INTENSITY/FL2.TUNNEL/INTENSITY.TD
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
For every pulse in the pulse train the information is saved:
- Intensity per pulse (a.u. (more or less µJ ))
- Intensity per pulse (auxillary GMD) - not used
- Position horizontal (mm, for a single pulse the position information may be very noisy - talk to your local contact)
- Position vertical (mm, for a single pulse the position information may be very noisy - talk to your local contact)
- Intensity per pulse sigma (a.u. (more or less µJ ), 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))
- Position horizontal sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
- Position vertical sigma (mm, indicates the error (RMS, sigma) of the measurement according to known uncertainties and signal to noise)
- 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
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 !
Besides pulse energy the GMD also provides information about the beam position
/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel horizontal
DOOCS prop : FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS
DAQ channel: FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IX.POS
desc : the Average ( ~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
units : mm
/FL2/Photon Diagnostic/GMD/Average Beam position/position tunnel vertical
DOOCS prop : FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS
DAQ channel: FLASH.FEL/XGM.POSMON/FL2.TUNNEL/IY.POS
desc : the Average ( ~ 20 sec averaging time ) Beam position of the photon Beam determined by the GMD (tunnel, x=horizontal)
units : mm
/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x
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)
again the same parameter set is available for the HALL GMD
Photon Diagnostics OPIS (FLASH2)
for more info see: OPIS
(The OPIS hall is not installed yet ...)
/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean photon energy
DOOCS prop : FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042
DAQ channel: FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL042
desc : mean photon energy ( ~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
units : eV
/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/mean wavelength
DOOCS prop : FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040
DAQ channel: FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL040
desc : mean wavelength ( ~ 1 sec averaging time ) measured in the TUNNEL for a specific bunch out of the bunch train (via photoelectron spectroscopy)
units : nm
/FL2/Photon Diagnostic/Wavelength/OPIS tunnel/Processed/number of analyzed bunch (in older version this can be found in OPIS tunnel/Expert stuff/General operation parameters/)
DOOCS prop : FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060
DAQ channel: FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060
desc : The bunch number of the bunch used for the wavelength calculation
units :
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 ( responsible for OPIS)
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 ...
Electron Beam properties (FLASH2)
bunch charge
/FL2/Electron Diagnostic/Bunch charge/after undulator
DOOCS prop : FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2
DAQ channel: FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2
desc: electron bunch charge FLASH2 (average value for each bunchtrain).
units: nC
electron bunch energy
/FL2/Electron Diagnostic/Electron energy/energy of first bunch/behind undulators
DOOCS prop : FLASH.DIAG/BEAM_ENERGY_MEASUREMENT/FL2XTDS/ENERGY.FLASH2
DAQ channel: TTF2.DAQ/PBD2.BEAM.ENERGY.MEAS.ML.COPY/FL2XTDS.ENERGY.FLASH2
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 extraction and septum in the beginning of FLASH2
units: MeV
undulator settings
/FL2/Electron Diagnostic/Undulator setting/set wavelength 1
DOOCS prop : FLASH.FEL/FL2.WAVELENGTHCONTROL/FLASH2.COLOR1/WAVELENGTH
DAQ channel: FLASH.FEL/FL2.WAVELENGTHCONTROL/FLASH2.COLOR1/WAVELENGTH
desc: Set value for the anticipated wavelength 1 . This parameter is used to set the undulator gap. It may however deviate from the actual wavelength by several % ... For 2 color operation there is also the same parameter for COLOR 2
units: nm
/FL2/Electron Diagnostic/Undulator setting/SASE13 gap
DOOCS prop : FLASH.UTIL/FL2.UND.MOTOR/FL2SASE13/GAP
DAQ channel: FLASH.UTIL/FL2.UND.MOTOR/FL2SASE13/GAP
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 2 to 13). Undulator 13 is the one closest to the experimental hall.
arrival time (BAM)
Discontinued BAM format (used until end 2021)
Discontinued BAM data recording
/FL2/Electron Diagnostic/BAM/8FL2XTDS/electron bunch arrival time (low charge)
always saved (PBD2)
DOOCS prop : FLASH.SDIAG/BAM/8FL2XTDS/LOW_CHARGE_ARRIVAL_TIME
DAQ channel: FLASH.SDIAG/BAM.DAQ/8FL2XTDS.LOW_CHARGE_ARRIVAL_TIME
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//Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge)
always saved (PBD2)
DOOCS prop : FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME
DAQ channel: FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME
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)
- 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
- LINK to detailed infos from MSK (may only work inside DESY network
- a recent
BAM FL0.DBC2
DBC2/electron bunch arrival time (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/
always saved (PBD)
FL0.DBC2
channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE.SA2.COMP
DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA2.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 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).
DBC2/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/
/zraw/FLASH.SDIAG/BAM.DAQ/FL0.DBC2.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE
FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.ABSOLUTE DAQ channel:
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).
DBC2/error (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamError.2
DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMERROR.2
desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
DBC2/status (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.bamStatus.2
DAQ channel: FLASH.SDIAG/BAM/FL0.DBC2/ARRIVAL_TIME.BAMSTATUS.2
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
/FL2/Electron Diagnostic/BAM/SEED5/electron bunch arrival time (HDF5 name not yet implemented - see zraw)
/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2.COMP/dGroup/
always saved (PBD)
FL2.SEED5
channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.ABSOLUTE.SA1.COMP
DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE.SA1.COMPDAQ 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).
SEED5/electron bunch arrival time (raw) (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/
/zraw/FLASH.SDIAG/BAM.DAQ/FL0.SEED5.ARRIVAL_TIME.ABSOLUTE.SA2/dGroup/
always saved (PBD)
FL2.SEED5DOOCS prop : FLASH.SDIAG/BAM//ARRIVAL_TIME.ABSOLUTE
FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.ABSOLUTE DAQ channel:
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).
FL2.SEED5/error (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamError.2
DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMERROR.2
desc: If the value is 0 , the BAM is working well. If it is non-zero there is a problem !!
FL2.SEED5/status (HDF5 name not yet implemented - see zraw)/FL2/Electron Diagnostic/BAM/
always saved (PBD)
DOOCS prop : FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.bamStatus.2
DAQ channel: FLASH.SDIAG/BAM/FL2.SEED5/ARRIVAL_TIME.BAMSTATUS.2
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
Timing information, rep rate etc. (FLASH2)
start time of FLASH2
/FL2/Timing/start time flash2
always saved (PBD2)
DOOCS prop : FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2
DAQ channel: FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2
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
/FL2/Timing/repetition rate
always saved (PBD2)
DOOCS prop : FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2
DAQ channel: FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2
desc: repetition rate of the bunches / pulses within the burst (FLASH2)
units: kHz
set number of pulses
(HDF5 name not yet implemented - see zraw)/FL2/Timing/set number of bunches
always saved (PBD2)
DOOCS prop : FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]
DAQ channel: FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.2 [4th number]
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 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
/FL1/Timing/actual number of bunches
always saved (PBD2)
DOOCS prop : FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2
DAQ channel: FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2
desc: Number of bunches measured BEHIND the undulator. If pulses are used for diagnostic of the protection system of the accelerator limits the number of bunches to be accelerated this is the actual number that created XUV radiation.The number is calculated by the DAQ middle layer server, (FLASH2)
units:
actual pulse pattern recorded after the undulator
/FL1/Timing/Bunch pattern/pattern after undulator
always saved (PBD2)
DOOCS prop : FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN
DAQ channel: FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN
desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
units:
Train ID
/Timing/train ID
always saved (PBD2)
DOOCS prop : none
DAQ channel: none
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:
Train time
always saved (PBD2)
/Timing/train time
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
always saved (PBD2)
desc: first column: Local time in unix time. To get day, hour, minute, second you can use unix: e.g. date --date='@1553617729' or matlab, python etc
second column: microseconds
third column: Train ID of FLASH
currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
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
saved on DEMAND in the user DAQ
Up to now there are 4 channels available at FL24
/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH00/TD
/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH01/TD
/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH02/TD/FL2/Experiment/MTCA-EXP1/ADQ412 GHz ADC/CH03/TD
DOOCS prop : FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00/CH00.TD or CH00.DAQ.TD
here the CH00.TD is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the CH00.DAQ.TD trace only has the number of samples which are sent to the DAQ OR if grouping is activated the CH00.DAQ.TD conatins only the grouped spectra. To read the ADC trace with an online analysis program the CH00.DAQ.TD is used preferablly.
DAQ channel: FLASH.FEL/ADC.ADQ.FL2EXP1/FL2EXP1.CH00
In addition there are also additional parameters saved like:
- sample frequency: 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.
- number of samples: total number of samoles recorded for each 10 Hz trigger
- error (ADC):0 indicates that there was no error
- /CH0-CH3/offset: 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:
/FL2/Experiment/MTCA-EXP1/SIS8300 100MHz ADC/CH2/TD
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:
- sample frequency: 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.
- number of samples: total number of samoles recorded for each 10 Hz trigger
Pump Probe Laser (FLASH2)
"/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:
- All FLASH1 related HDF groups moved to group "/FL1", i.e. a new prefix "/FL1" is added to their HDF path.
- The ambigious term "pulse" has been replaced by "train" to refer to "pulse train". Most notably, the dataset "/Timing/pulse ID" has changed to "/Timing/train ID".
- A number of inconsistent names have been streamlined. The relevant changes are listed in the following table.
earlier HDF path (vers. 0.2) | is now (vers. 0.3) |
|---|---|
/Photon Diagnostic/GMD/Beam position/position BDA x | /FL1/Photon Diagnostic/GMD/Beam position/position BDA horizontal |
/Photon Diagnostic/GMD/Beam position/position BDA y | /FL1/Photon Diagnostic/GMD/Beam position/position BDA vertical |
/Photon Diagnostic/GMD/Beam position/position tunnel x | /FL1/Photon Diagnostic/GMD/Beam position/position tunnel horizontal |
/Photon Diagnostic/GMD/Beam position/position tunnel y | /FL1/Photon Diagnostic/GMD/Beam position/position tunnel vertical |
/Experiment/Pump probe laser/BPM/position x | /FL1/Experiment/Pump probe laser/BPM/position horizontal |
/Experiment/Pump probe laser/BPM/position y | /FL1/Experiment/Pump probe laser/BPM/position vertical |
/FL2/Photon Diagnostic/GMD/Beam position/Average/position hall horizontal | /FL2/Photon Diagnostic/GMD/Average beam position/position hall horizontal |
/FL2/Photon Diagnostic/GMD/Beam position/Average/position hall vertical | /FL2/Photon Diagnostic/GMD/Average beam position/position hall vertical |
/FL2/Photon Diagnostic/GMD/Beam position/Average/position tunnel horizontal | /FL2/Photon Diagnostic/GMD/Average beam position/position tunnel horizontal |
/FL2/Photon Diagnostic/GMD/Beam position/Average/position tunnel vertical | /FL2/Photon Diagnostic/GMD/Average beam position/position tunnel vertical |
/FL2/Photon Diagnostic/GMD/Average energy/hall | /FL2/Photon Diagnostic/GMD/Average energy/energy hall |
/FL2/Photon Diagnostic/GMD/Average energy/hall (raw) | /FL2/Photon Diagnostic/GMD/Average energy/energy hall (raw) |
/FL2/Photon Diagnostic/GMD/Average energy/tunnel | /FL2/Photon Diagnostic/GMD/Average energy/energy tunnel |
/FL2/Photon Diagnostic/GMD/Average energy/tunnel (raw) | /FL2/Photon Diagnostic/GMD/Average energy/energy tunnel (raw) |
/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/hall x | /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall horizontal |
/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/hall y | /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position hall vertical |
/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/tunnel x | /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel horizontal |
/FL2/Photon Diagnostic/GMD/Beam position/Pulse resolved/tunnel y | /FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel vertical |