Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/02/06 10:55
From version 15.1
edited by sndueste
on 2019/09/18 09:12
Change comment: There is no comment for this version
To version 13.1
edited by sndueste
on 2019/09/17 16:58
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -36,7 +36,7 @@
36 36  
37 37  \\
38 38  
39 -== Most popular FLASH parameters and their names in HDF5, DOOCS and (raw) DAQ ==
39 +== Most popular FLASH parameters and their names in HDF5 ==
40 40  
41 41  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"]].
42 42  The most common and often used ones are summarized below:
... ... @@ -618,7 +618,9 @@
618 618  
619 619  \\
620 620  
621 +\\
621 621  
623 +
622 622  //always saved (PBD2)//
623 623  \\\\{{code language="none"}}/FL2/Photon Diagnostic/GMD/Pulse resolved beam position/position tunnel x DOOCS prop : FLASH.FEL/XGM.BPM/FL2.HALL/X.TDDAQ channel: FLASH.FEL/XGM.BPM/FL2.HALL:2 desc: {{/code}}Besides the well calibrated averaged beam position information there is also the option
624 624  {{code language="none"}}to measure the beam position on a single bunch level. HOWEVER this methide needs a perfectly adjusted signal level (talk to your local contact !!) and also then the signal to noise is rather small and one needs some averaging ... BUT with this option one can determine if there was a spatial slope on a burst (say forst bunches were lower than the last ones or so ...)units : mm    {{/code}}
... ... @@ -631,7 +631,7 @@
631 631  
632 632  \\
633 633  
634 -==== Photon Diagnostics OPIS[[ >>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]](FLASH2) ====
636 +==== Photon Diagnostics OPIS[[ >>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]](FLASH2) ====
635 635  
636 636  for more info see: [[ OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]]
637 637  
... ... @@ -670,90 +670,117 @@
670 670  
671 671  \\
672 672  
673 -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 ...
675 +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 ...
674 674  
675 675  \\
676 676  
677 677  \\
678 678  
681 +\\
682 +
679 679  ==== Electron Beam properties (FLASH2) ====
680 680  
681 681  ===== bunch charge =====
682 682  
683 683  {{code language="none"}}/FL2/Electron Diagnostic/Bunch charge/after undulator{{/code}}
684 -//always saved (PBD2)//
688 +//always saved (PBD)//
685 685  DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
686 686  DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
687 -desc: electron bunch charge FLASH2 (average value for each bunchtrain).
691 +desc: electron bunch charge (FLASH2)
688 688  units: nC
689 689  
690 690  \\
691 691  
692 -===== undulator settings =====
696 +\\
693 693  
694 -{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/set wavelength{{/code}}
695 -//always saved (PBD2)//
696 -DOOCS prop : {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
697 -DAQ channel:  {{code language="none"}}TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH{{/code}}
698 -desc: Set value for the anticipated wavelength . This parameter is used to set the undulator gap. It may however deviate from the actual wavelength by several % ...
699 -units: nm
698 +(% class="wrapped" %)
699 +|(((
700 +FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP
701 +)))|(((
702 +/FL2/Electron Diagnostic/Undulator setting/SASE14 gap
703 +)))
704 +|(((
705 +TTF2.FEEDBACK/FL2.WAVELENGTHCONTROL/FLASH2/WAVELENGTH
706 +)))|(((
707 +/FL2/Electron Diagnostic/Undulator setting/set wavelength
708 +)))
700 700  
701 -{{code language="none"}}/FL2/Electron Diagnostic/Undulator setting/SASE14 gap{{/code}}
702 -//always saved (PBD2)//
703 -DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
704 -DAQ channel:  {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
705 -desc: gap value of the undulators. This can be used to follow up how many undulators were closed and if there was a taper
706 -units: mm
707 -
708 -The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall.
709 -
710 710  =====
711 711  arrival time =====
712 712  
713 -**FL1**{{code language="none"}}//Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
714 -//always saved (PBD2)//
713 +{{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
714 +//always saved (PBD)//
715 715  DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
716 716  DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
717 717  desc: Electron bunch arrival time measured with the BAM (more or less) before the undulator (pulse resolved data)
718 -units: ps (bigger numbers indicate later arrivaltime of the electrons)
718 +units: ps (bigger numbers indicate later arrivaltime of the electrons)
719 +note: besides the arivaltime from FLASH1 there is also the FLASH2/3 electron arrival time saved. [[LINK to detailled infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]] and to a recent  [[talk about the working principle of the BAM>>url:https://confluence.desy.de/download/attachments/134216957/BAM-basics_and_outlook-2018_DESY-template_16-9Format.pdf?version=1&modificationDate=1565162143328&api=v2||shape="rect"]]
719 719  
720 -The BAM measures the arrivaltime of** FLASH 1 and FLASH2** in the same data set (thus also sorted in at /FL1/ !). The first values are for FLASH1 bunches.
721 -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) ...
721 +\\
722 722  
723 -Docu for BAM:  [[LINK to detailled infos from MSK (may only work inside DESY network~[~[image:url:http://hasfweb.desy.de/pub/TWiki/TWikiDocGraphics/external-link.gif~|~|width="13" height="12"~]~]>>url:http://www.desy.de/~~mbock/pages/BAM_daq_channel_descriptions.html||shape="rect"]] and to a recent  [[talk about the working principle of the BAM>>url:https://confluence.desy.de/download/attachments/134216957/BAM-basics_and_outlook-2018_DESY-template_16-9Format.pdf?version=1&modificationDate=1565162143328&api=v2||shape="rect"]]
723 +\\
724 724  
725 +\\
725 725  
726 -[[Contents>>doc:||anchor="Contents"]]
727 +===== electron bunch energy =====
727 727  
729 +{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/average electron energy{{/code}}
730 +_always saved (PBD)
731 +DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_INTRA_MEAN/VAL{{/code}}
732 +DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_MEAN{{/code}}
733 +desc: electron bunch energy (average over the bunch train)
734 +units: (% class="twikiNewLink" %)MeV(%%)
728 728  \\
729 729  
730 -==== Timing information, rep rate etc.  (FLASH1) ====
737 +{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/pulse resolved energy{{/code}}
738 +_always saved (PBD)
739 +DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/E_SPECT/VAL.TD{{/code}}
740 +DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/E_SPECT{{/code}}
741 +desc: electron bunch energy bunch resolved
742 +units: (% class="twikiNewLink" %)MeV
731 731  
732 -===== start time of FLASH2 =====
744 +\\
733 733  
734 -{{code language="none"}}/FL2/Timing/start time flash2{{/code}}
735 -//always saved (PBD2)//
736 -DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
737 -DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
738 -desc: The max 600 µs acceleration time of FLASH is devided between FLASH1 and FLASH2. FLASH1 is (up to now) first starting for historic reasons 700 µs. 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) ...
739 -units: µs
746 +{{code language="none"}}/FL1/Electron Diagnostic/Electron energy/wavelength bunch train average{{/code}}
747 +_always saved (PBD)
748 +DOOCS prop : {{code language="none"}}TTF2.DAQ/ENERGY.DOGLEG/LAMBDA_MEAN/VAL{{/code}}
749 +DAQ channel: {{code language="none"}}PBD.ENERGY.DOGLEG/LAMBDA_MEAN{{/code}}
750 +desc: Wavelength calculated by the electron bunch energy (average over the bunch train) (FLASH1)
751 +units: nm
752 +\\
740 740  
754 +[[Contents>>doc:||anchor="Contents"]]
755 +
756 +\\
757 +
758 +==== Timing information, rep rate etc.  (FLASH1) ====
759 +
741 741  ===== bunch repetition rate =====
742 742  
743 -{{code language="none"}}/FL2/Timing/repetition rate{{/code}}
744 -//always saved (PBD2)//
745 -DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
746 -DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
747 -desc: repetition rate of the bunches / pulses within the burst (FLASH2)
762 +{{code language="none"}}/FL1/Timing/repetition rate{{/code}}
763 +//always saved (PBD)//
764 +DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}}
765 +DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}
766 +desc: repetition rate of the bunches / pulses within the burst (FLASH1)
748 748  units: kHz
768 +\\
749 749  
770 +===== set number of pulses =====
771 +
772 +{{code language="none"}}/FL1/Timing/set number of bunches{{/code}}
773 +//always saved (PBD)//
774 +DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH1{{/code}}
775 +DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_NUM{{/code}}
776 +desc: Number of pulses set at the gun (FLASH1)
777 +units:
778 +
750 750  ===== actual number of pulses =====
751 751  
752 752  {{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
753 -//always saved (PBD2)//
754 -DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
755 -DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
756 -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)
782 +//always saved (PBD)//
783 +DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/12EXP/NUMBEROFBUNCHES.FLASH1{{/code}}
784 +DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
785 +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)
757 757  units:
758 758  \\
759 759  
... ... @@ -760,10 +760,10 @@
760 760  ===== actual pulse pattern recorded after the undulator =====
761 761  
762 762  {{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
763 -//always saved (PBD2)//
764 -DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
765 -DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
766 -desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
792 +//always saved (PBD)//
793 +DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
794 +DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
795 +desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH1)
767 767  units:
768 768  \\
769 769  
... ... @@ -770,7 +770,7 @@
770 770  ===== Train ID =====
771 771  
772 772  {{code language="none"}}/Timing/train ID{{/code}}
773 -//always saved (PBD2)//
802 +//always saved (PBD)//
774 774  DOOCS prop : {{code language="none"}}none{{/code}}
775 775  DAQ channel: {{code language="none"}}none{{/code}}
776 776  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 !)