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 18.1
edited by sndueste
on 2019/09/18 10:09
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -385,7 +385,7 @@
385 385  //always saved (PBD)//
386 386  DOOCS prop : {{code language="none"}}none{{/code}}
387 387  DAQ channel: {{code language="none"}}none{{/code}}
388 -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 !)
388 +desc: Each 10 Hz burst has its unique train ID. For the HDF5 data set 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 !)
389 389  units:
390 390  \\
391 391  
... ... @@ -392,7 +392,7 @@
392 392  ===== Train time =====
393 393  
394 394  {{code language="none"}}/Timing/train time{{/code}}
395 -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
395 +desc:Local time as array of day, hour, minute, second, and centisecond. This data set is meant for visualization purposes only. For correlations use the train ID or the Unix time of the time stamp
396 396  units: d h min s cs
397 397  \\
398 398  
... ... @@ -458,9 +458,15 @@
458 458  
459 459  ==== User Data (FLASH1) ====
460 460  
461 +The data saved specifically for detectors at an experiment will show up in /Experiment/ there is a large number of options for cameras or monitoring pslow properties (motor positons etc) for user experiments. For details please ask your local contact.
462 +
463 +NOTE: If parameters for an experiment are included on short notice the correct naming in the HDF5 may not be in time and the data will show up in /uncategorized/ with the DOOCS names
464 +
465 +The most common and permanently installed device used by experiment are our ADCs:
466 +
461 461  ===== GHz ADCs =====
462 462  
463 -ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]
469 +ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found** [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]**
464 464  //saved on DEMAND in the user DAQ//
465 465  \\The HDF5 names for the ADC traces are depending on the beamline :
466 466  \\PG Beamline:
... ... @@ -483,14 +483,12 @@
483 483  here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} conatins only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferablly.
484 484  DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}}
485 485  
486 -in addition there are also additional parameters saved like:
492 +In addition there are also additional parameters saved like:
487 487  
488 -* sample frequency (in MHz)
489 -* error (state)
490 -* offset
494 +* {{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.
495 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
496 +* {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error
491 491  
492 -~|
493 -
494 494  ===== MHz ADCs =====
495 495  
496 496  similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
... ... @@ -498,10 +498,19 @@
498 498  DOOCS prop : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02/CH00.TD
499 499  DAQ channel: : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02
500 500  
501 -\\
505 +In addition there are also additional parameters saved like:
502 502  
507 +* {{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.
508 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
509 +
503 503  [[Contents>>doc:||anchor="Contents"]]
504 504  
512 +\\
513 +
514 +\\
515 +
516 +\\
517 +
505 505  === FLASH2 ===
506 506  
507 507  There is analog to FLASH1 a permanently running "PhotonDagnostic DAQ FLASH2" (PBD2) and 2 User DAQs
... ... @@ -509,11 +509,11 @@
509 509  ==== Beamline info (FLASH2) ====
510 510  
511 511  (% style="color: rgb(255,153,0);" %)(not yet available){{code language="none"}}/FL2/Beamlines/Attenuator/pressure  {{/code}}(%%)
512 -//always saved (PBD2)//
513 -DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}}
514 -DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}}
515 -desc: set pressure in the gas attenuator
516 -units: mbar
525 +(% style="color: rgb(193,199,208);" %)//always saved (PBD2)// (%%)
526 +(% style="color: rgb(193,199,208);" %)DOOCS prop : {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
527 +(% style="color: rgb(193,199,208);" %)DAQ channel:  {{code language="none"}}FLASH.FEL/ATT.GAS_DOSING/FL2.HALL/PRESSURE{{/code}} (%%)
528 +(% style="color: rgb(193,199,208);" %)desc: set pressure in the gas attenuator (%%)
529 +(% style="color: rgb(193,199,208);" %)units: mbar(%%)
517 517  \\
518 518  
519 519  {{code language="none"}}/FL2/Beamlines/FL20/Shutter/open{{/code}}
... ... @@ -727,7 +727,7 @@
727 727  
728 728  \\
729 729  
730 -==== Timing information, rep rate etc.  (FLASH1) ====
743 +==== Timing information, rep rate etc.  (FLASH2) ====
731 731  
732 732  ===== start time of FLASH2 =====
733 733  
... ... @@ -735,7 +735,7 @@
735 735  //always saved (PBD2)//
736 736  DOOCS prop : {{code language="none"}}FLASH.DIAG/TIMER/FLASHCPUTIME1.0/BUNCH_POSITION.2{{/code}}
737 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) ...
751 +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 ...)
739 739  units: µs
740 740  
741 741  ===== bunch repetition rate =====
... ... @@ -779,13 +779,16 @@
779 779  
780 780  ===== Train time =====
781 781  
782 -{{code language="none"}}/Timing/train time{{/code}}
795 +//always saved (PBD2)
796 +//{{code language="none"}}/Timing/train time{{/code}}
783 783  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
784 784  units: d h min s cs
785 785  \\
786 786  
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
801 +{{code language="none"}}/Timing/time stamp{{/code}}
802 +
803 +//always saved (PBD2)//
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 789  second column: microseconds
790 790  third column: Train ID of FLASH
791 791  \\
... ... @@ -794,6 +794,54 @@
794 794  
795 795  \\
796 796  
813 +==== User Data (FLASH1) ====
814 +
815 +===== GHz ADCs =====
816 +
817 +ADC traces of the (SPDevices 412) GHZ ADCs available for the users . More information about the ADCs can be found [[here>>doc:FLASHUSER.Data Acquisition and controls.Controls (DOOCS, jDDD,\.\.\.).MTCA ADCs.WebHome]]
818 +//saved on DEMAND in the user DAQ//
819 +\\The HDF5 names for the ADC traces are depending on the beamline :
820 +\\PG Beamline:
821 +{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH00/TD{{/code}}
822 +{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH01/TD{{/code}}
823 +{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH02/TD{{/code}}
824 +{{code language="none"}}/FL1/Experiment/PG/ADQ412 GHz ADC/CH03/TD{{/code}}
825 +
826 +BL Beamlines:
827 +{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH00/TD{{/code}}
828 +{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH01/TD{{/code}}
829 +{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH02/TD{{/code}}
830 +{{code language="none"}}/FL1/Experiment/BL1/ADQ412 GHz ADC/CH03/TD{{/code}}
831 +\\{{code language="none"}}/FL1/Experiment/BL2/ADQ412 GHz ADC/CH00/TD{{/code}}
832 +{{code language="none"}}/FL1/Experiment/BL2/ADQ412 GHz ADC/CH01/TD{{/code}}
833 +\\{{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH02/TD{{/code}}
834 +{{code language="none"}}/FL1/Experiment/BL3/ADQ412 GHz ADC/CH03/TD{{/code}}
835 +
836 +DOOCS prop : {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00/CH00.TD  or CH00.DAQ.TD{{/code}}
837 +here the {{code language="none"}}CH00.TD{{/code}} is the full ADC trace as it is sampled ( typically several 100.000 samples per pulse train) while the {{code language="none"}}CH00.DAQ.TD{{/code}} trace only has the number of samples which are sent to the DAQ OR if //grouping// is activated the {{code language="none"}}CH00.DAQ.TD{{/code}} conatins only the grouped spectra. To read the ADC trace with an online analysis program the {{code language="none"}}CH00.DAQ.TD{{/code}} is used preferablly.
838 +DAQ channel: {{code language="none"}}FLASH.FEL/ADC.ADQ.PG/EXP1.CH00{{/code}}
839 +
840 +In addition there are also additional parameters saved like:
841 +
842 +* {{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.
843 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
844 +* {{code language="none"}}error (ADC):{{/code}} 0 indicates that there was no error
845 +* {{code language="none"}}/CH0-CH3/offset{{/code}}: To use the full dynamic range of the ADC one can shift the base line . This offset is saved here.
846 +
847 +===== MHz ADCs =====
848 +
849 +similar to the GHz ADCs the MHz ADCs are saved with HDF5 names like:
850 +{{code language="none"}}/FL1/Experiment/BL1/SIS8300 100MHz ADC/CH2/TD{{/code}}
851 +DOOCS prop : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02/CH00.TD
852 +DAQ channel: : FLASH.FEL/ADC.SIS.BL1/EXP1.CH02
853 +
854 +In addition there are also additional parameters saved like:
855 +
856 +* {{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.
857 +* {{code language="none"}}number of samples{{/code}}: total number of samoles recorded for each 10 Hz trigger
858 +
859 +[[Contents>>doc:||anchor="Contents"]]
860 +
797 797  \\
798 798  
799 799  \\
... ... @@ -806,6 +806,8 @@
806 806  
807 807  \\
808 808  
873 +\\
874 +
809 809  (% class="wrapped" %)
810 810  |=(((
811 811  DAQ name