Changes for page The FLASH HDF5 structure

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

From 56.1 to 57.1 From 78.1 to 79.1

From version 57.1

edited by sndueste
on 2022/09/07 09:50

Change comment: There is no comment for this version

To version 78.1

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Tags

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

Content

@@ -79,12 +79,10 @@
  {{/layout-cell}}
  {{layout-cell}}
--* The //average// FEL pulse energy as example for the **slow** **data** (different e.g. 1 Hz):
++* 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}})
--           ( every 10th train ID is listed in the HDF group "index")
++           ( as example only every 10th train ID is listed in the HDF group "index")
--\\
--
  [[image:attach:image2020-11-16_15-31-45.png||height="250"]]
  {{/layout-cell}}
@@ -104,11 +104,12 @@
  {{layout-section ac:type="single"}}
  {{layout-cell}}
  {{info}}
--=== Reference implementation (Python) ===
++===  There are different options that help you to work with the FLASH HDF5 data in Python ===
--(imperative)  (% class="Object" %)[[https:~~/~~/gitlab.desy.de/christopher.passow/flash-daq-hdf>>url:https://gitlab.desy.de/christopher.passow/flash-daq-hdf||shape="rect"]]
++* 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"]]
--(% class="Object" %)(object oriented) [[https:~~/~~/gitlab.desy.de/christopher.passow/fdh-builder>>url:https://gitlab.desy.de/christopher.passow/fdh-builder.git||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]]
  {{/info}}
  {{/layout-cell}}
  {{/layout-section}}
@@ -115,6 +115,8 @@
  {{layout-section ac:type="single"}}
  {{layout-cell}}
++
++
  == Complete list of recordable parameters ==
  The complete list for the relation between DOOCS names and HDF5 names for the recordable parameters can be found in [[DESY's Repository~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:https://stash.desy.de/projects/CS/repos/pah/browse/src/camp/data/channel2HdfName.dat||shape="rect"]].
@@ -419,9 +419,10 @@
  arrival time (BAM) =====
  {{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 for pulses that go to FL1 and to FL2 (in detail: first time slot of the accelerator and second)
++* 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
@@ -443,41 +443,94 @@
  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 arrivaltime of the electrons)
++units: ps (bigger numbers indicate later arrival time of the electrons)
  {{/expand}}
++====== **BAM FL0.DBC2**{{code language="none"}}{{/code}} ======
++
++(% style="color: rgb(255,102,0);" %)**DBC2**/electron bunch arrival time   (HDF5 name not yet implemented - see zraw)(%%)
++//always saved (PBD)//
++{{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).
++
  \\
--{{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
++(% style="color: rgb(255,102,0);" %)DBC2/electron bunch arrival time (raw)  (HDF5 name not yet implemented - see zraw){{code language="none"}}/FL1/Electron Diagnostic/BAM/{{/code}}(%%)
  //always saved (PBD)//
--DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
--DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
--desc: Electron bunch arrival time measured with the BAM inside the accelerator - however shows a very good correlation to the arrivaltime  of the XUV pulses in the experiment (pulse resolved data).
--units: ps (bigger numbers indicate later arrivaltime of the electrons)
++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).
--{{code language="none"}}/FL1/Electron Diagnostic/BAM/1SFELC/electron bunch arrival time (low charge){{/code}}
++\\
++
++(% 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 : {{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 arrivaltime of the electrons)
++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 !!
  \\
--{{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>>url:https://confluence.desy.de/display/SDiagPublic/BAM+Data+Structure||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/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}}
@@ -548,11 +548,11 @@
  ===== set number of pulses =====
--{{code language="none"}}/FL1/Timing/set number of bunches{{/code}}
++(% 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}}(%%)
  //always saved (PBD)//
--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)
++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
  units:
  ===== actual number of pulses =====
@@ -604,6 +604,43 @@
  ==== 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)//
@@ -645,6 +645,7 @@
  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}}
  \\
@@ -931,8 +931,27 @@
  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 =====
++arrival time (BAM) =====
++{{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}}
@@ -957,8 +957,94 @@
  * [[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"]]
  \\
@@ -983,6 +983,17 @@
  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}}
@@ -1081,11 +1081,129 @@
  \\
--==== Pump Probe Laser (FLASH2) ====
++==== FL 24 Pump Probe Laser (FLASH2) ====
--There may be more information available from the "Laser DAQ". laese contact your Laser Local Contact.
++These are the parameters that can be saved in the FL2 User DAQ for the FL2 PP laser//** FOR BEAMLINE FL24**//
++\\
++**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}}
@@ -1118,7 +1118,172 @@
  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"]]
  \\

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

Author

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

Size

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

Content

FLASH1__DaqChannel2HdfNamePbd.xlsx

Author

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

Size

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

Content

HDF5_structure.jpg

Author

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

Size

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

Content

HDF5_structure_desc.jpg

Author

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

Size

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

Content

binder_badge.png

Author

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

Size

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

Content

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

Author

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

Size

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

Content

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

Author

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

Size

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

Content

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

Author

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

Size

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

Content

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

Author

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

Size

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

Content

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

Author

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

Size

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

Content

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

Author

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

Size

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

Content

Changes for page The FLASH HDF5 structure

Summary

Details

Applications

Navigation