Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 89.2
edited by robert
on 2025/10/28 18:02
Change comment: There is no comment for this version
To version 89.1
edited by robert
on 2025/10/28 18:01
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -322,7 +322,7 @@
322 322  
323 323  == 18 Leap Second bug ==
324 324  
325 -Not so much a bug as much as "a thing that can happen if your SoloLite installation is corrupted". If you notice your data has large time offsets, you should suspect that the number of leap seconds has not been accounted properly. There is a file "smartsoloconfig.xml" that needs to be present in "C:\SmartSoloApps SoloLite" (e.g. the main program directory) that dictates the leap second offset for the last two data ranges. Since 2017-01-01, this is 18 seconds. At some point in the next few years it will be 19 seconds.
325 +Not so much a bug as much as "a thing that can happen if your SoloLite installation is corrupted". If you notice your data has large time offsets, you should suspect that the number of leap seconds has not been accounted properly. There is a file "smartsoloconfig.xml" that needs to be present in "C:\SmartSoloApps SoloLite" (e.g. the main program directory) that dictates the leap second offset for the last two data ranges. Since 2017-01-01, this is 18 seconds.
326 326  
327 327  If this file is missing, just create a new one structured like so, name it "smartsoloconfig.xml" and put it in your main program directory. Then, Reanalyze your data (tools > Reanalyze seismic data) and your data should have the correct time. You can also do this manually, if you want. The offset is 18 seconds precisely.
328 328