Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 85.1
edited by Jack Dent
on 2025/09/29 12:55
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.JackD
1 +XWiki.robert
Content
... ... @@ -16,8 +16,6 @@
16 16  
17 17  = **Programming Defaults** =
18 18  
19 -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>>https://nappe.wustl.edu/smartsolo/files/smartsolo_online_training.pdf]]
20 -
21 21  The nodes must be programmed in the SoloLite software prior to use. Screenshots for the short period 16HR-3C and broadband BDC3-5 are shown with our recommended parameters.
22 22  
23 23  [[IGU-16 3C (short period node) programming screen set at 250 Hz. Ensure that the highlighted areas are set!>>image:SP_programming.labels.png||alt="IGU-16 3C programming screen"]]
... ... @@ -46,18 +46,6 @@
46 46  **Note that any applied instrument gain must be removed when exporting (e.g. to miniseed) after your deploy, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high!
47 47  {{/info}}
48 48  
49 -=== **Programming tips**: ===
50 -
51 -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:
52 -
53 - - Place the node on the harvester gently, then firmly press it down onto the pins
54 -
55 - - 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.
56 -
57 - - 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 eachother
58 -
59 - - Nodes will likely not show up in the order that they should, though this is not an issue. Eg, a node in slot 6 on the harvester may show up in port 13 in the SoloLite software
60 -
61 61  = **Fieldwork Preparation** =
62 62  
63 63  (% class="box warningmessage" %)
... ... @@ -246,12 +246,27 @@
246 246  
247 247  
248 248  
249 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
235 +{{{
236 + }}}
250 250  
251 251  ----
252 252  
253 253  = **Downloading and Converting Seismic Data to MiniSeed Format** =
254 254  
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 +
255 255  == Node Registration and Software Setup ==
256 256  
257 257  1. (((
... ... @@ -270,6 +270,27 @@
270 270  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
271 271  )))
272 272  
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 +
273 273  == Data Downloading Process ==
274 274  
275 275  1. (((
... ... @@ -294,10 +294,38 @@
294 294  )))
295 295  )))
296 296  
297 -== Smart Solo Z Polarity bug ==
319 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
298 298  
299 -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 invert the response metadata. The BD3C-5 data does not require a polarity inversion.
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.**
300 300  
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.
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 +
301 301  == Handling Nodes During Download ==
302 302  
303 303  1. (((