Changes for page The FLASH HDF5 structure
Last modified by sndueste on 2025/09/10 11:43
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -116,11 +116,12 @@ 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. 120 120 121 - 122 122 === FLASH1 === 123 123 122 + 123 +IN teh 124 + 124 124 ==== Beamline info (FLASH1) ==== 125 125 126 126 {{code language="none"}}/FL1/Beamlines/Attenuator/pressure{{/code}} ... ... @@ -604,17 +604,22 @@ 604 604 second column: microseconds 605 605 third column: Train ID of FLASH 606 606 607 -currently it is saved as Unix time in 608 +currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time 608 608 609 - |(((610 - /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time610 +{{expand expanded="false" title="Timestamp help for python"}} 611 + import time 611 611 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 !!! 614 +# 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 615 +epoch_time = 1709051499.17 # Replace with your epoch time 614 614 615 -[[Contents>>doc:||anchor="Contents"]] 617 +formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time)) 618 +print(formatted_time) 619 +{{/expand}} 616 616 617 617 622 +[[Contents>>doc:||anchor="Contents"]] 623 + 618 618 ==== Pump Probe Laser (FLASH1) ==== 619 619 620 620 **PIGLET (PG laser)** ... ... @@ -1111,10 +1111,10 @@ 1111 1111 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 !) 1112 1112 units: 1113 1113 1114 -===== Train time ===== 1120 +===== (% style="color:#e67e22" %)Train time(%%) ===== 1115 1115 1116 -//always saved (PBD2)// 1117 -{{code language="none"}}/Timing/train time{{/code}} 1122 +(% style="color:#e67e22" %)//always saved (PBD2)//(%%) 1123 +(% style="color:#e67e22" %){{code language="none"}}/Timing/train time{{/code}} 1118 1118 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 1119 1119 units: d h min s cs 1120 1120 ... ... @@ -1122,11 +1122,28 @@ 1122 1122 /Timing/time stamp 1123 1123 {{/code}} 1124 1124 1125 -//always saved (PBD2)// 1126 -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 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 1127 1127 second column: microseconds 1128 1128 third column: Train ID of FLASH 1129 1129 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 + 1130 1130 [[Contents>>doc:||anchor="Contents"]] 1131 1131 1132 1132