Skip to Content

Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/09/10 11:43
From version 93.2
edited by sndueste
on 2025/05/19 16:44
Change comment: There is no comment for this version
To version 91.1
edited by sndueste
on 2025/04/24 13:29
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -116,12 +116,11 @@
116 116  
117 117  {{id name="DOOCSparameters"/}}
118 118  
119 +Note, the HDF group and data set names apply to our HDF tree version since vers. 0.3.0.
119 119  
121 +
120 120  === FLASH1 ===
121 121  
122 -
123 -IN teh
124 -
125 125  ==== Beamline info (FLASH1) ====
126 126  
127 127  {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}}
... ... @@ -607,7 +607,7 @@
607 607  
608 608  currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
609 609  
610 -{{expand expanded="false" title="Timestamp help for python"}}
609 +{{expand title="Timestamp help for python" expanded="false"}}
611 611   import time
612 612  
613 613  # epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
... ... @@ -618,6 +618,9 @@
618 618  print(formatted_time)
619 619  {{/expand}}
620 620  
620 +|(((
621 +
622 +)))
621 621  
622 622  [[Contents>>doc:||anchor="Contents"]]
623 623  
... ... @@ -1117,10 +1117,10 @@
1117 1117  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 !)
1118 1118  units:
1119 1119  
1120 -===== (% style="color:#e67e22" %)Train time(%%) =====
1122 +===== Train time =====
1121 1121  
1122 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1123 -(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}}
1124 +//always saved (PBD2)//
1125 +{{code language="none"}}/Timing/train time{{/code}}
1124 1124  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
1125 1125  units: d h min s cs
1126 1126  
... ... @@ -1128,28 +1128,11 @@
1128 1128  /Timing/time stamp
1129 1129  {{/code}}
1130 1130  
1131 -(% style="color:#e67e22" %)//always saved (PBD2)//(%%)
1132 -(% style="color:#e67e22" %)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
1133 +//always saved (PBD2)//
1134 +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
1133 1133  second column: microseconds
1134 1134  third column: Train ID of FLASH
1135 1135  
1136 -
1137 -(% id="cke_bm_2455529S" style="display:none" %) (%%)currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
1138 -
1139 -{{expand expanded="false" title="Timestamp help for python"}}
1140 - import time
1141 -
1142 -# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
1143 -# The time and date of the start of the data taking in the HDF file is encoded in the filename - to roughly check the time
1144 -epoch_time = 1709051499.17 # Replace with your epoch time
1145 -
1146 -formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
1147 -print(formatted_time)
1148 -{{/expand}}
1149 -
1150 -
1151 -
1152 -
1153 1153  [[Contents>>doc:||anchor="Contents"]]
1154 1154  
1155 1155