Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/02/06 10:55
From version 10.1
edited by sndueste
on 2019/09/17 16:45
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
... ... @@ -1,25 +1,8 @@
1 1  == Contents ==
2 2  
3 -\\
4 4  
5 -* [[General information about HDF5>>doc:||anchor="General information about HDF5"]]
6 -* [[FLASH HDF5 structure>>doc:||anchor="FLASH HDF5 structure"]]
7 -* [[Most popular FLASH parameters and their names in HDF5>>doc:||anchor="Most popular FLASH parameters and their names in HDF5"]]
8 -** [[FLASH1>>doc:||anchor="FLASH1"]]
9 -*** [[Beamline info (FLASH1)>>doc:||anchor="Beamline info (FLASH1)"]]
10 -*** [[Photon Diagnostics SASE / Spectrometer (FLASH1)>>doc:||anchor="Photon Diagnostics SASE / Spectrometer (FLASH1)"]]
11 -*** [[Electron Beam properties (FLASH1)>>doc:||anchor="Electron Beam properties (FLASH1)"]]
12 -*** [[Timing information, rep rate etc.(FLASH1)>>doc:||anchor="Timing information, rep rate etc.(FLASH1)"]]
13 -*** [[Pump Probe Laser (FLASH1)>>doc:||anchor="Pump Probe Laser (FLASH1)"]]
14 -*** [[User Data (FLASH1)>>doc:||anchor="User Data (FLASH1)"]]
15 -** [[FLASH2>>doc:||anchor="FLASH2"]]
16 -** [[HDF5 structure revisions>>doc:||anchor="HDF5 structure revisions"]]
17 -* [[Example code showing how to access HDF5 files>>doc:||anchor="Example code showing how to access HDF5 files"]]
18 -** [[Samples how to read HDF5 with Matlab>>doc:||anchor="Samples how to read HDF5 with Matlab"]]
19 -** [[How to read HDF5 with Python via FLASHH5>>doc:||anchor="How to read HDF5 with Python via FLASHH5"]]
20 -* [[HDF5 and DOOCS>>doc:||anchor="HDF5 and DOOCS"]]
21 21  
22 -\\
5 +{{toc/}}
23 23  
24 24  \\
25 25  
... ... @@ -680,12 +680,17 @@
680 680  // saved opon request (PBD2)//
681 681  DOOCS prop : {{code language="none"}}FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
682 682  DAQ channel:{{code language="none"}} FLASH.UTIL/STORE/FL2.TUNNEL.OPIS/VAL060{{/code}}
683 -desc : The bunch number of the bunch used for the wavelength calculationiunits :
666 +desc : The bunch number of the bunch used for the wavelength calculation
667 +units :
684 684  
685 685  \\
686 686  
671 +If Opis is running typically on the the averaged data is saved. For several experiments it may make sense to save the information for each single bunch. This is up to now done by savng the compleate ADC trace of the TOF setup. This is a huge amount of data and needs processing. This has to be performed after the beamtime in close contact to [[Markus Braune>>mailto:markus.braune@desy.de||shape="rect"]] ( respobsible for [[OPIS>>url:http://photon-science.desy.de/facilities/flash/photon_diagnostics/opis_spectrometer/index_eng.html||shape="rect"]])
672 +
687 687  \\
688 688  
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 ...
676 +
689 689  \\
690 690  
691 691  \\
... ... @@ -692,12 +692,161 @@
692 692  
693 693  \\
694 694  
683 +==== Electron Beam properties (FLASH2) ====
684 +
685 +===== bunch charge =====
686 +
687 +{{code language="none"}}/FL2/Electron Diagnostic/Bunch charge/after undulator{{/code}}
688 +//always saved (PBD)//
689 +DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
690 +DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN/CHARGE.FLASH2{{/code}}
691 +desc: electron bunch charge (FLASH2)
692 +units: nC
693 +
695 695  \\
696 696  
697 697  \\
698 698  
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 +)))
709 +
710 +=====
711 +arrival time =====
712 +
713 +{{code language="none"}}/FL1/Electron Diagnostic/BAM/4DBC3/electron bunch arrival time (low charge){{/code}}
714 +//always saved (PBD)//
715 +DOOCS prop : {{code language="none"}}FLASH.SDIAG/BAM/4DBC3/LOW_CHARGE_ARRIVAL_TIME{{/code}}
716 +DAQ channel: {{code language="none"}}FLASH.SDIAG/BAM.DAQ/4DBC3.LOW_CHARGE_ARRIVAL_TIME{{/code}}
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)
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"]]
720 +
699 699  \\
700 700  
723 +\\
724 +
725 +\\
726 +
727 +===== electron bunch energy =====
728 +
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(%%)
735 +\\
736 +
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
743 +
744 +\\
745 +
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 +\\
753 +
754 +[[Contents>>doc:||anchor="Contents"]]
755 +
756 +\\
757 +
758 +==== Timing information, rep rate etc.  (FLASH1) ====
759 +
760 +===== bunch repetition rate =====
761 +
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)
767 +units: kHz
768 +\\
769 +
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 +
779 +===== actual number of pulses =====
780 +
781 +{{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
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)
786 +units:
787 +\\
788 +
789 +===== actual pulse pattern recorded after the undulator =====
790 +
791 +{{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
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)
796 +units:
797 +\\
798 +
799 +===== Train ID =====
800 +
801 +{{code language="none"}}/Timing/train ID{{/code}}
802 +//always saved (PBD)//
803 +DOOCS prop : {{code language="none"}}none{{/code}}
804 +DAQ channel: {{code language="none"}}none{{/code}}
805 +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 !)
806 +units:
807 +\\
808 +
809 +===== Train time =====
810 +
811 +{{code language="none"}}/Timing/train time{{/code}}
812 +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
813 +units: d h min s cs
814 +\\
815 +
816 +{{code language="none"}}/Timing/time stamp{{/code}}
817 +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
818 +second column: microseconds
819 +third column: Train ID of FLASH
820 +\\
821 +
822 +[[Contents>>doc:||anchor="Contents"]]
823 +
824 +\\
825 +
826 +\\
827 +
828 +\\
829 +
830 +\\
831 +
832 +\\
833 +
834 +\\
835 +
836 +\\
837 +
701 701  (% class="wrapped" %)
702 702  |=(((
703 703  DAQ name