Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 89.3
edited by robert
on 2025/10/29 10:39
Change comment: There is no comment for this version
To version 88.1
edited by robert
on 2025/10/27 16:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -233,8 +233,9 @@
233 233  
234 234  
235 235  {{{
236 - }}}
237 237  
237 +}}}
238 +
238 238  ----
239 239  
240 240  = **Downloading and Converting Seismic Data to MiniSeed Format** =
... ... @@ -320,34 +320,6 @@
320 320  
321 321  See [[https:~~/~~/auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodeZPolaritybug>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodeZPolaritybug]] for discussion. If data is headed to AusPass, we prefer to invert the IGU-16HR 3 Z channel data manually rather than in the SoloLite software or inverting the response metadata. **The BD3C-5 data does not require a polarity inversion.**
322 322  
323 -== 18 Leap Second bug ==
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.
326 -
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 -
329 -{{code language="none"}}
330 -<?xml version="1.0" encoding="UTF-8"?>
331 -<config>
332 - <leapsecond>
333 - <interval>
334 - <start_time>2017-01-01#00:00:00</start_time>
335 - <end_time>2999-12-31#23:59:59</end_time>
336 - <second>18</second>
337 - </interval>
338 - <interval>
339 - <start_time>1970-01-01#00:00:00</start_time>
340 - <end_time>2017-01-01#00:00:00</end_time>
341 - <second>17</second>
342 - </interval>
343 - </leapsecond>
344 - <GPS_distance_threshold_degree>
345 - 4e-5
346 - </GPS_distance_threshold_degree>
347 -</config>
348 -{{/code}}
349 -
350 -
351 351  == Handling Nodes During Download ==
352 352  
353 353  1. (((