Skip to Content
Last modified by robert on 2025/10/29 10:39
From version 86.1
edited by Jack Dent
on 2025/09/29 13:00
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.JackD
1 +XWiki.robert
Content
... ... @@ -232,8 +232,10 @@
232 232  
233 233  
234 234  
235 -[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
235 +{{{
236 236  
237 +}}}
238 +
237 237  ----
238 238  
239 239  = **Downloading and Converting Seismic Data to MiniSeed Format** =
... ... @@ -241,19 +241,17 @@
241 241  (% class="wikigeneratedid" %)
242 242  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]]
243 243  
244 -=== **Connection tips**: ===
246 +== Connection tips: ==
245 245  
246 246  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:
247 247  
248 - - Place the node on the harvester gently, then firmly press it down onto the pins
250 +* Place the node on the harvester gently, then firmly press it down onto the pins.
251 +* 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.
252 +* 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.
253 +* 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!
249 249  
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 251  
252 - - 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
253 253  
254 - - 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
255 -
256 -
257 257  == Node Registration and Software Setup ==
258 258  
259 259  1. (((
... ... @@ -272,6 +272,27 @@
272 272  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
273 273  )))
274 274  
275 +== File structure ==
276 +
277 +There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
278 +
279 +=== SOLOLITE ===
280 +
281 +This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
282 +
283 +=== DCCDATA ===
284 +
285 +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.
286 +
287 +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)//
288 +
289 +Then in the SoloLite software, go to tools > Reanalyze Seismic Data
290 +
291 +=== SOLODATA ===
292 +
293 +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.
294 +
295 +
275 275  == Data Downloading Process ==
276 276  
277 277  1. (((
... ... @@ -296,9 +296,9 @@
296 296  )))
297 297  )))
298 298  
299 -== Smart Solo Z Polarity bug ==
320 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
300 300  
301 -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.
322 +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.**
302 302  
303 303  == Handling Nodes During Download ==
304 304