Changes for page The FLASH HDF5 structure

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

Summary

Details

Page properties
Content
... ... @@ -485,10 +485,9 @@
485 485  
486 486  in addition there are also additional parameters saved like:
487 487  
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.
488 +* sample frequency (in MHz)
489 +* error (state)
490 +* offset
492 492  
493 493  ~|
494 494  
... ... @@ -728,7 +728,7 @@
728 728  
729 729  \\
730 730  
731 -==== Timing information, rep rate etc.  (FLASH2) ====
730 +==== Timing information, rep rate etc.  (FLASH1) ====
732 732  
733 733  ===== start time of FLASH2 =====
734 734  
... ... @@ -736,7 +736,7 @@
736 736  //always saved (PBD2)//
737 737  DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
738 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 ...)
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) ...
740 740  units: µs
741 741  
742 742  ===== bunch repetition rate =====
... ... @@ -780,16 +780,13 @@
780 780  
781 781  ===== Train time =====
782 782  
783 -//always saved (PBD2)
784 -//{{code language="none"}}/Timing/train time{{/code}}
782 +{{code language="none"}}/Timing/train time{{/code}}
785 785  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
786 786  units: d h min s cs
787 787  \\
788 788  
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
787 +{{code language="none"}}/Timing/time stamp{{/code}}
788 +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
793 793  second column: microseconds
794 794  third column: Train ID of FLASH
795 795  \\