Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/02/06 10:55
From version 14.1
edited by sndueste
on 2019/09/17 17:52
Change comment: There is no comment for this version
To version 17.1
edited by sndueste
on 2019/09/18 09:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -485,9 +485,10 @@
485 485  
486 486  in addition there are also additional parameters saved like:
487 487  
488 -* sample frequency (in MHz)
489 -* error (state)
490 -* offset
488 +* {{code language="none"}}sample frequency{{/code}}: it shows the sample frequency in MHz (number of samples per µs). NOTE: the clock of the ADC is NOT synchronized to the FLASH timing system. Thus the number of samples between bunches in the bunch train may be not integer numbers which will be show up for long bunch trains.
489 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
490 +* {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error
491 +* {{code language="none"}}offset{{/code}}: To use the full dynamic range of the ADC one can shift the base line . This offset is saved here.
491 491  
492 492  ~|
493 493  
... ... @@ -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) ====
635 +==== 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,7 +670,7 @@
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 ...
674 +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  
... ... @@ -684,7 +684,7 @@
684 684  //always saved (PBD2)//
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)
688 +desc: electron bunch charge FLASH2 (average value for each bunchtrain).
688 688  units: nC
689 689  
690 690  \\
... ... @@ -702,10 +702,10 @@
702 702  //always saved (PBD2)//
703 703  DOOCS prop : {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
704 704  DAQ channel:  {{code language="none"}}FLASH.UTIL/FL2.UND.MOTOR/FL2SASE14/GAP{{/code}}
705 -desc: Sgap value of the Undulators. this can be used to follow up how many undulators were closed and if there was a taper
706 +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 706  units: mm
707 707  
708 -The gap values are saved for all 12 undulators (Nr 3 to 14)
709 +The gap values are saved for all 12 undulators (Nr 3 to 14). Undulator 14 is the one closest to the experimental hall.
709 709  
710 710  =====
711 711  arrival time =====
... ... @@ -717,59 +717,43 @@
717 717  desc: Electron bunch arrival time measured with the BAM (more or less) before the undulator (pulse resolved data)
718 718  units: ps (bigger numbers indicate later arrivaltime of the electrons)
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 +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.
722 +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 721  
722 -\\
724 +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 723  
724 -first bunch of FLASH2 ... how to calculate ..
725 725  
726 -\\
727 +[[Contents>>doc:||anchor="Contents"]]
727 727  
728 728  \\
729 729  
730 -Docu:  [[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"]]
731 +==== Timing information, rep rate etc.  (FLASH2) ====
731 731  
732 -\\
733 +===== start time of FLASH2 =====
733 733  
734 -\\
735 +{{code language="none"}}/FL2/Timing/start time flash2{{/code}}
736 +//always saved (PBD2)//
737 +DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
738 +DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
739 +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 ...)
740 +units: µs
735 735  
736 -\\
737 -
738 -
739 -\\
740 -
741 -[[Contents>>doc:||anchor="Contents"]]
742 -
743 -\\
744 -
745 -==== Timing information, rep rate etc.  (FLASH1) ====
746 -
747 747  ===== bunch repetition rate =====
748 748  
749 -{{code language="none"}}/FL1/Timing/repetition rate{{/code}}
750 -//always saved (PBD)//
751 -DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.1{{/code}}
752 -DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_FREQ{{/code}}
753 -desc: repetition rate of the bunches / pulses within the burst (FLASH1)
744 +{{code language="none"}}/FL2/Timing/repetition rate{{/code}}
745 +//always saved (PBD2)//
746 +DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
747 +DAQ channel: {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/REP_RATE_KHZ.2{{/code}}
748 +desc: repetition rate of the bunches / pulses within the burst (FLASH2)
754 754  units: kHz
755 -\\
756 756  
757 -===== set number of pulses =====
758 -
759 -{{code language="none"}}/FL1/Timing/set number of bunches{{/code}}
760 -//always saved (PBD)//
761 -DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH1{{/code}}
762 -DAQ channel: {{code language="none"}}TTF2.UTIL/LASER.CONTROL/GUN/PULSE_NUM{{/code}}
763 -desc: Number of pulses set at the gun (FLASH1)
764 -units:
765 -
766 766  ===== actual number of pulses =====
767 767  
768 768  {{code language="none"}}/FL1/Timing/actual number of bunches{{/code}}
769 -//always saved (PBD)//
770 -DOOCS prop : {{code language="none"}}FLASH.DIAG/TOROID.ML/12EXP/NUMBEROFBUNCHES.FLASH1{{/code}}
771 -DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
772 -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)
754 +//always saved (PBD2)//
755 +DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
756 +DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/3GUN/NUMBEROFBUNCHES.FLASH2{{/code}}
757 +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)
773 773  units:
774 774  \\
775 775  
... ... @@ -776,10 +776,10 @@
776 776  ===== actual pulse pattern recorded after the undulator =====
777 777  
778 778  {{code language="none"}}/FL1/Timing/Bunch pattern/pattern after undulator{{/code}}
779 -//always saved (PBD)//
780 -DOOCS prop : {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP/CHARGE.TD{{/code}}
781 -DAQ channel: {{code language="none"}}TTF2.DIAG/PBD.TOROID.ML/12EXP{{/code}}
782 -desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH1)
764 +//always saved (PBD2)//
765 +DOOCS prop : {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
766 +DAQ channel: {{code language="none"}}FLASH.DIAG/PBD2.TOROID.ML/9FL2BURN.PULSEPATTERN{{/code}}
767 +desc: The bunch pattern as function of time in a burst recorded by toroide diagnostic BEHIND the undulator. (FLASH2)
783 783  units:
784 784  \\
785 785  
... ... @@ -786,7 +786,7 @@
786 786  ===== Train ID =====
787 787  
788 788  {{code language="none"}}/Timing/train ID{{/code}}
789 -//always saved (PBD)//
774 +//always saved (PBD2)//
790 790  DOOCS prop : {{code language="none"}}none{{/code}}
791 791  DAQ channel: {{code language="none"}}none{{/code}}
792 792  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 !)
... ... @@ -795,13 +795,16 @@
795 795  
796 796  ===== Train time =====
797 797  
798 -{{code language="none"}}/Timing/train time{{/code}}
783 +//always saved (PBD2)
784 +//{{code language="none"}}/Timing/train time{{/code}}
799 799  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
800 800  units: d h min s cs
801 801  \\
802 802  
803 -{{code language="none"}}/Timing/time stamp{{/code}}
804 -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
789 +{{code language="none"}}/Timing/time stamp{{/code}}
790 +
791 +//always saved (PBD2)//
792 +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
805 805  second column: microseconds
806 806  third column: Train ID of FLASH
807 807  \\