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 80.1
edited by Jack Dent
on 2025/08/01 16:17
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.JackD
Content
... ... @@ -232,27 +232,12 @@
232 232  
233 233  
234 234  
235 -{{{
236 - }}}
235 +[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
237 237  
238 238  ----
239 239  
240 240  = **Downloading and Converting Seismic Data to MiniSeed Format** =
241 241  
242 -(% class="wikigeneratedid" %)
243 -SmartSolo provides the following powerpoint for SmartSolo node programming and operation. Note that ANSIR only uses a portion of their process for our own uses: [[https:~~/~~/nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf>>url:https://nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf]]
244 -
245 -== Connection tips: ==
246 -
247 -Connecting SmartSolo nodes to their harvesters and having SoloLite recognise them can be a bit tricky, here are some tricks to help register and program them easier:
248 -
249 -* Place the node on the harvester gently, then firmly press it down onto the pins.
250 -* Place all nodes onto the harvester before trying any troubleshooting, as they may not show up while the SoloLite software is running. Once all are connected, try restarting the software for them to be recognised.
251 -* If a node is refusing to connect, try it with another slot. It is easiest if you place all 16 nodes on the harvester, and swap any nodes that refuse to connect with each other.
252 -* Nodes will likely not show up in the order that they should, though this is not an issue. E.g, a node in slot 6 on the harvester may show up in port 13 in the SoloLite software. Annoying, but it doesn't matter so long as you keep track of what's been harvested!
253 -
254 -
255 -
256 256  == Node Registration and Software Setup ==
257 257  
258 258  1. (((
... ... @@ -271,27 +271,6 @@
271 271  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
272 272  )))
273 273  
274 -== File structure ==
275 -
276 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
277 -
278 -=== SOLOLITE ===
279 -
280 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
281 -
282 -=== DCCDATA ===
283 -
284 -This folder stores the RAW data you have harvested from the nodes. The data will still be on the nodes (unless you erased it) in case of emergency, but regardless, this is the folder you want to back up and save somewhere.
285 -
286 -If you had a weird time harvesting a node, you can always manually copy it as if it were a USB stick and place it into this folder manually. The structure is: //C:/DCCDATA/prospect_name/project_name/SERIALNUMBER/label(usually a timestamp but can be anything)//
287 -
288 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
289 -
290 -=== SOLODATA ===
291 -
292 -This folder stores **exported** (e.g. miniseed) data. It is structured similarly. If your DCCDATA is intact, this can always be re-created if need be.
293 -
294 -
295 295  == Data Downloading Process ==
296 296  
297 297  1. (((
... ... @@ -316,38 +316,6 @@
316 316  )))
317 317  )))
318 318  
319 -== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
320 -
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 -
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. (((
... ... @@ -443,7 +443,7 @@
443 443  
444 444  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
445 445  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
446 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
378 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
447 447  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
448 448  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
449 449  |(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
... ... @@ -463,7 +463,7 @@
463 463  
464 464  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
465 465  |(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
466 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
398 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
467 467  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
468 468  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
469 469  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
... ... @@ -484,7 +484,7 @@
484 484  
485 485  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
486 486  |(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
487 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
419 +|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm
488 488  |(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
489 489  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
490 490  |(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((