Skip to Content

Changes for page The FLASH HDF5 structure

Last modified by sndueste on 2025/09/10 11:43
From version 89.12
edited by sndueste
on 2025/04/24 13:22
Change comment: There is no comment for this version
To version 93.1
edited by sndueste
on 2025/04/24 13:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -604,13 +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
607 +currently it is saved as Unix time in : /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
608 608  
609 -|/zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time
609 +{{expand expanded="false" title="Timestamp help for python"}}
610 + import time
610 610  
611 -[[Contents>>doc:||anchor="Contents"]]
612 +# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
613 +# 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
614 +epoch_time = 1709051499.17 # Replace with your epoch time
612 612  
616 +formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
617 +print(formatted_time)
618 +{{/expand}}
613 613  
620 +
621 +[[Contents>>doc:||anchor="Contents"]]
622 +
614 614  ==== Pump Probe Laser (FLASH1) ====
615 615  
616 616  **PIGLET (PG laser)**
... ... @@ -1107,9 +1107,9 @@
1107 1107  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 !)
1108 1108  units:
1109 1109  
1110 -===== Train time =====
1119 +===== (% style="color:#e67e22" %)Train time(%%) =====
1111 1111  
1112 -//always saved (PBD2)//
1121 +(% style="color:#e67e22" %)//always saved (PBD2)//
1113 1113  {{code language="none"}}/Timing/train time{{/code}}
1114 1114  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
1115 1115  units: d h min s cs
... ... @@ -1118,11 +1118,28 @@
1118 1118  /Timing/time stamp
1119 1119  {{/code}}
1120 1120  
1121 -//always saved (PBD2)//
1130 +(% style="color:#e67e22" %)//always saved (PBD2)//
1122 1122  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
1123 1123  second column: microseconds
1124 1124  third column: Train ID of FLASH
1125 1125  
1135 +
1136 +(% 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
1137 +
1138 +{{expand expanded="false" title="Timestamp help for python"}}
1139 + import time
1140 +
1141 +# epoch time is found in /zraw/FLASH.DIAG/TIMINGINFO/TIME1.BUNCH_FIRST_INDEX.1/dGroup/time #!!! a leading 1 has to be added !!!
1142 +# 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
1143 +epoch_time = 1709051499.17 # Replace with your epoch time
1144 +
1145 +formatted_time = time.strftime('%Y-%m-%d %H:%M:%S', time.gmtime(epoch_time))
1146 +print(formatted_time)
1147 +{{/expand}}
1148 +
1149 +
1150 +
1151 +
1126 1126  [[Contents>>doc:||anchor="Contents"]]
1127 1127  
1128 1128