Skip to Content
Last modified by robert on 2026/07/09 10:45
From version 116.2
edited by robert
on 2026/07/09 10:45
Change comment: Added comment
To version 19.2
edited by Sima Mousavi
on 2024/01/18 13:49
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -SmartSolo Node Seismometers
1 +SmartSolo Nodes
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.robert
1 +XWiki.sima
Content
... ... @@ -2,508 +2,272 @@
2 2  (((
3 3  (% class="col-xs-12 col-sm-8" %)
4 4  (((
5 -= **Node Types** =
5 += **Node Setup** =
6 6  
7 -ANSIR supply two types of three-channel nodes, and one type of one-channel node:
7 +Short term (~~30 day) battery powered nodes
8 8  
9 -* **SmartSolo IGU-16HR 3C (5 Hz, 'very' short period)**
10 -* **SmartSolo BD3C-5 (5 second, short period)**
11 -* **SmartSolo IGU-16 1C (5 Hz, 'very' short period, single channel. Not 'HR')**
9 +== **Pre-Fieldwork Preparation** ==
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
14 -
15 -The three-channel nodes have a theoretical battery capacity of ~~30 days, whereas the single-channel type has a capacity of ~~50 days. The programming, operation and downloading procedures for all types of SmartSolo nodes are also similar.
16 -
17 17  (% class="box infomessage" %)
18 18  (((
19 -**Freight update, 2026: **Freight options for lithium-ion batteries are changing in 2025/2026 to comply with updated transport safety regulations. This will impact supply of IGU 16 (<100Wh) and BD3C (168Wh) nodes. Advice will be sought from freighters on a case-by-case basis while they implement new guidelines.
20 -)))
21 -
22 -----
23 -
24 -= **Programming Defaults** =
25 -
26 -The nodes must be programmed in the SoloLite software prior to use. The screenshots below show our recommended parameters for the 5 Hz (16HR-3C) and 5 second (BDC3-5) nodes.
27 -
28 -[[IGU16HR-3C programming screen set at 250 Hz. Ensure circled areas are set!>>image:5Hz_node_programming.labels.png||alt="IGU-16 3C programming screen"]]
29 -
30 -[[BD3C-5 programming screen set at 250 Hz. Ensure circled areas are set!>>image:5S_node_programming.labels.png||alt="BD3C-5 programming screen set at 250 hz. Ensure that the circled areas are set!"]]
31 -
32 -
33 -FIFO (first in, first out) data mode is safest as this will overwrite old data in case you forgot to clear the storage. At <= 250 hz you can fit 4++ months of data on these, shouldn't be an issue.
34 -
35 -Note that the samplerate is instead given in sample spacing, in milliseconds. 4 ms = 250 Hz, 1 ms = 1000 Hz, 10 ms = 100 Hz, ad nauseam.
36 -
37 -Be sure to set the channel types to Seismic and the gain appropriately. For active source (i.e. explosions) you can leave the gain at 0, but for passive experiments some gain is purported to be helpful (although we have found this to be somewhat negligible). We can confirm that 6db for the broadband nodes and 24db for the short period works well.
38 -
39 -If you want recording to begin immediately, ensure that begin date is in the past by at least a few days. If you prefer to have a timed turn-on, then set the times as needed. **Be warned that recording will not begin until a GPS lock is achieved, so if you set it to a future turn-on but bury it too deeply, it may not record!**
40 -
41 -In newer versions of the software there is a "power consumption" setting.. we are no sure what this does exactly, but the manual says it gives life a "boost" at the expense of about 3 db of resolution. Until this can be quantified a bit better it is not recommended.
42 -
43 -Storage type can be DLD (proprietary) or Miniseed. We assume the software works best with their proprietary format so prefer not to risk any issues. You can export to miniseed later.
44 -
45 -GPS is best set to cycle mode (e.g. once per hour) instead of constant "always on". The clock drift on these are almost nil even if there is no sync at all, so it's best to conserve power.
46 -
47 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
48 -
49 -We recommend that the 16HR-3C be set to a gain of 24db for passive experiments and no higher than 250 Hz sampling rate unless there is an explicit reason to do so. The BD3C-5 should be set to a gain of 6db (which is the maximum allowed) for passive experiments (or 0 db if active).
50 -
51 -{{info}}
52 -**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!
53 -{{/info}}
54 -
55 -= **Fieldwork Preparation** =
56 -
57 57  (% class="box warningmessage" %)
58 58  (((
59 -**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
60 -
61 -**Assume ~~1 Tb of storage for both raw and exported data per 50 nodes @ 250 Hz & 30 days. One node recording at 250 Hz for 30 days tends to create about 3 Gb of miniseed data.**
62 -
63 -**We have had good experience with the 4Tb Samsung T7 Shield drives.**
15 +**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING **
64 64  )))
17 +)))
65 65  
66 -== Magnets ==
67 -
68 -If you are short on magnets, you may find it easier and a lot cheaper to buy magnets in Australia. AMF Magnetics is a good retailer, and [[this item>>https://magnet.com.au/collections/shop?q=23012B]] seems to work well. It is also advantageous to use smaller magnets and store/carry them individually in your back pocket (as well as stick them to various places in your field vehicle, etc).
69 -
70 -== Animal-Proofing ==
71 -
72 -We have experienced interference from animals (foxes, dogs, goats) digging up and carrying nodes off for tens or hundreds of metres. It is helpful to minimise human and food smells (particularly on the rope handles) when working in areas where this is a risk. Or, wipe down affected nodes with 50-80% methylated spirits if extensive handling can not be avoided.
73 -
74 -If you come to collect your node and it is missing~-~- LOOK FOR IT! It may not have gotten far. We have found dozens of nodes by spending 15 minutes looking for them.
75 -
76 -= External Power =
77 -
78 -Both the 5Hz IGU-16HR and 5s BD3C-5 can be optionally powered via external battery via either a replacement bottom half (the 5Hz nodes) or a battery cable accessory (BD3C-5) using standard lead acid batteries from 9-36v. We have done preliminary testing at 250 Hz with a 12v battery:
79 -
80 -- BD3C-5: ~~2 days of recording per 1 Ah
81 -
82 -- IGU16-HR 3C:  ~~3.5 days of recording per 1 Ah
83 -
84 -- IGU16-HR 1C: ~~7 days of recording per 1 Ah
85 -
86 -Of course, these can also be fit with a solar panel & charge controller which would then theoretically keep them going indefinitely (limited only by the disk storage, which at 250 Hz could be on the order of 12 months).
87 -
88 88  = **Installation** =
89 89  
90 -(% class="box infomessage" %)
91 -(((
92 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
93 -)))
21 +=== **1- Logbook documentation** ===
94 94  
95 -== 1. Logbook documentation ==
96 -
97 97  (((
98 -**Essential Details** for field logs:
24 +**Essential Details**: Record the following in a logbook:
99 99  
26 +
100 100  * Station name
101 -* Latitude, longitude, elevation
28 +* Latitude and longitude
102 102  * Names of team members present
103 -* Date and both local & UTC time of installation/removal
104 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
105 -* Detailed notes on the site conditions and setup, anything else that will be helpful to find it again ("by the fence", "south of rock", etc)
30 +* Date and local time of installation
31 +* Serial number (SN) of the sensor
32 +* Detailed notes on the site conditions and setup
106 106  
107 -[[HERE>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]] is an example logsheet that works well for nodes, feel free to print and use!
108 -
109 -== 2. Node Placement ==
34 +=== **2- Node Placement** ===
110 110  )))
111 111  
37 +**Protection**: Place nodes inside thick, landfill biodegradable plastic bags for environmental protection.
38 +
112 112  **Site Analysis**:
113 113  
114 -* **Take compass measurements away from the sensor as it will affect your measurement. Use a stick or shovel to help align.**
115 -* Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
116 -* Include a detailed site description in your notes.
41 +* Conduct compass measurements away from the node and metallic structures, adjusting for inclination angle.
42 +* Take multiple photographs from various angles to document the site setup thoroughly.
43 +* Include a detailed site description in your notes, specifying distances and orientations from nearby landmarks (e.g. Richards garden, Te Mini steam field eastern side)
117 117  
118 -== 3. GPS Considerations ==
45 +=== **3- Visibility and Location Marking** ===
119 119  
120 -(% class="wikigeneratedid" %)
121 -The GPS antenna is at the top and center of the unit, and will (usually) only receive signal with a clear sky view directly above. The signal is able to penetrate plastic and terracotta planters and a thin (2 cm?) layer of soil, but may struggle if the soil layer is too thick. **These nodes will not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.
122 -
123 -== 4. Visibility and Location Marking ==
124 -
125 125  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
126 126  
127 127  **GPS Marking**:
128 128  
129 -* Use a GPS device to mark the instrument's exact location. Most modern cell phones can get to about a 3m error with their internal GPS also; you can probably also get away with investing a few dollars in a good app that shows error and lets you log markers.
130 -* Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
51 +* Use a GPS device to mark the instrument's exact location.
52 +* Record this location in both your paper notes and the GPS device.
131 131  
132 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
54 +=== **4- Data Sharing and Metadata Creation** ===
133 133  
134 -* **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
135 -* **Pre-Deployment Charging**:
136 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
137 -
138 -* **Operational Duration**:
139 -** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle. If they are set to run only overnight, this can be extended to 60 days.
140 -
141 -* **Post-Retrieval Charging**:
142 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
143 -* **State of Charge (SoC) for Storage**:
144 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
145 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
146 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
147 -** Storage at 0-charge damages lithium batteries**.**
148 -* **SoC for Transport:**
149 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
150 -
151 -(((
152 -== 6. Data Sharing and Metadata Creation ==
153 -)))
154 -
155 155  **GPS Data**:
156 156  
157 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
58 +* Download the GPS file to a laptop.
59 +* Share this file on a drive accessible to all team members for uniform understanding of node locations.
158 158  
159 159  **Photo Sharing**:
160 160  
161 -* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
63 +* Upload site photos to a shared platform (OneDrive, Dropbox, etc.).
64 +* Integrating photos into Google Maps or Google Earth can be particularly beneficial for easy location referencing.
162 162  
163 163  **Metadata File**:
164 164  
165 -* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]]. This is going to be particularly important if you are reusing nodes at different sites... not documenting the serial numbers (of the **top half** of the node) and the times they were deployed can lead to station mix-ups.
68 +* Create a metadata XML file for each node, which is essential for data organisation and future reference.
166 166  
167 -== 7. Additional Best Practices ==
70 +=== **5- Additional Best Practices** ===
168 168  
169 -* **Training and Familiarisation**: Make sure all team members are adequately trained in using the GPS devices, compass use, and other equipment to ensure consistent and accurate data collection.
72 +* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations.
73 +* **Training and Familiarisation**: Make sure all team members are adequately trained in using the GPS devices, compass, and other equipment to ensure consistent and accurate data collection.
170 170  
171 -----
75 += =
172 172  
173 -= **Seismic Station Demobilization and Documentation** =
174 -
175 -1. (((
176 -**Preparation for Demobilization**:
177 -
178 -* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag.
77 +* (((
78 +==== **Keeping the Instruments Clean** ====
179 179  )))
180 -1. (((
181 -**Locating the instrument**:
182 -
183 -* Use the downloaded GPS file to accurately locate the node for demobilization.
184 -* Import this KMZ file onto your phone for easy reference and location tracking.
185 -* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location.
80 +* (((
81 +Use a (**landfill**, not //compost//) degradable bag when installing to keep the instrument clean. This will save you many hours of time cleaning them in preparation for their return. [[Here is a video>>url:http://auspass.edu.au/field/bd3c_removal.mp4]] demonstrating its effectiveness.
186 186  )))
187 -1. (((
188 -**Labeling Instruments for Demobilization**:
189 189  
190 -* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.
191 -* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
192 -* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
193 -)))
194 -1. (((
195 -**Photographing the Setup Node**:
84 += =
196 196  
197 -* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__.
198 -* This photo serves as a final record of the instrument’s condition and orientation at the time of removal.
199 -)))
200 -1. (((
201 -**Logging Demobilization Details**:
86 += SmartSolo IGU 16HR 3C (5 Hz) Short Period Node =
202 202  
203 -* Use the field logbook to note the time of demobilization, serial numbers, and station name.
204 -* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors.
205 -)))
206 -1. (((
207 -**Final Checks and Equipment Removal**:
88 +blahblah
208 208  
209 -* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.
210 -* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.
90 +== Sub-paragraph ==
211 211  
212 -
213 -)))
214 214  
215 -[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]]
93 +== ==
216 216  
217 -----
218 218  
219 -= **Charging Procedure for Seismic Nodes** =
96 += Smart Solo BD3C-5 (5 second) Broad-Band Node =
220 220  
221 -(((
222 -== 1. Preparation for Charging: ==
98 +Lorem
223 223  
224 -* Before charging, ensure each node is clean. This involves removing any dirt or debris to maintain the integrity of the equipment and ensure effective charging.
225 -)))
100 +[[image:1705196270090-364.png]]
226 226  
227 -(((
228 -== 2. Disassembling the Node: ==
229 229  
230 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
231 -)))
103 +== GPS Considerations ==
232 232  
233 -(((
234 -== 3. Setting Nodes in the Charging Box: ==
105 +The GPS antenna is at the top and center of the unit, and will (usually) only receive signal with a clear sky view directly above. The signal is able to penetrate plastic and terracotta planters and a thin layer of soil, but may struggle if the soil layer is too thick. The BD3C will not start recording without first attaining a GPS lock.
235 235  
236 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
237 -* Charging will begin automatically when nodes are inserted in the charging rack.
238 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
239 -)))
107 += Keeping the Instruments Clean =
240 240  
241 -(((
242 -== 4. Monitoring the Charging Process: ==
109 +Use a (**landfill**, not //compost//) degradable bag when installing to keep the instrument clean. This will save you many hours of time cleaning them in preparation for their return. [[Here is a video>>url:http://auspass.edu.au/field/bd3c_removal.mp4]] demonstrating its effectiveness.
243 243  
244 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
245 -* Observe the transition of the lights from steady RED to ORANGE, then GREEN, and finally to FLASHING GREEN. A flashing green light indicates the batteries are fully charged.
246 -)))
247 247  
248 -(((
249 -== 5. Updating Charge Status: ==
112 += Charge Time, Instrument Life, and Charge During Storage & Shipping =
250 250  
251 -* During the charging period, take this opportunity to update the status of each unit. Check the //"C"// box on your temporary labels to indicate that the unit has been successfully charged.
252 -* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
253 -)))
114 +Both nodes take about 6-8 hours to charge from flat and hold their charge reasonably well, however you may benefit from a "top up" charge immediately prior to deploy. The instruments should last around 30 days per cycle (recording at 250hz) with GPS on cycle on and bluetooth disabled.
254 254  
255 -[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]]
116 +Upon retrieval, the instruments should not be stored flat as this will damage the batteries. It is recommended to charge them back up "to orange" such that they are charged around ~~50-60%. This is also acceptable for shipping.
256 256  
257 257  
119 += Best Practices and Guide =
258 258  
121 +== Install ==
259 259  
260 -{{{
261 - }}}
123 +Logbook is required (used again for pick up & metadata creation)
262 262  
263 -----
125 +- station name
264 264  
265 -= **Downloading and Converting Seismic Data to MiniSeed Format** =
127 +- lat / long
266 266  
267 -(% class="wikigeneratedid" %)
268 -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]]
129 +- team members
269 269  
270 -== Connection tips: ==
131 +- date and local time
271 271  
272 -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:
133 +- SN of sensor
273 273  
274 -* Place the node on the harvester gently, then firmly press it down onto the pins.
275 -* 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.
276 -* 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.
277 -* 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!
135 +- notes on site
278 278  
137 +Place nodes in thick (“landfill biodegradable”) plastic bags in the hole
279 279  
139 +Take compass measurement away from node and fences [make sure to adjust inclination angle]
280 280  
281 -== Node Registration and Software Setup ==
141 +Take many photos from the site from different angles 
282 282  
283 -1. (((
284 -**Registering Nodes in the System**:
143 +Add a precise site description to the notes such as distances and orientations from landmarks 
285 285  
286 -* To begin, register the nodes in the system so the software can recognize them.
287 -* Navigate to the installation folder of “SmartSoloApps SoloLite”.
288 -* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below).
289 -* To avoid double registration, replace the file each time you register a new node.
290 -)))
291 -1. (((
292 -**Creating a New Project in SoloLite**:
145 +It will be very helpful in locating the instrument if you place a flag next to it, preferably in a color other than green or yellow.
293 293  
294 -* Open the “SoloLite” software.
295 -* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing.
296 -* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
297 -)))
147 +Make a mark (digital) of the instrument's location using a GPS device. Record the location both in your paper notes and on the GPS device.
298 298  
299 -== File structure ==
149 +Download the GPS (Garmin) file to a laptop and share drive to share with other GPS devices
300 300  
301 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
151 +Share photos in a shared location (Google photos, OneDrive, Dropbox, etc), but most useful are those added to a Google Maps/Earth location
302 302  
303 -=== SOLOLITE ===
153 +Create metadata .xml file
304 304  
305 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
306 306  
307 -=== DCCDATA ===
156 +== Removing/Demob ==
308 308  
309 -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.
158 +Download and then use the GPS file to locate the node 
310 310  
311 -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)//
160 +Use Google Maps / Google Earth to create a kmz file that can then be imported onto your phone.  
312 312  
313 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
314 314  
315 -=== SOLODATA ===
163 +Upload photos of the site  
316 316  
317 -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.
165 +- station name
318 318  
167 +- latitude
319 319  
320 -== Data Downloading Process ==
169 +- longitude
321 321  
322 -1. (((
323 -**Initiating Data Download**:
171 +- elevation
324 324  
325 -* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
326 -* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
327 -* Select all nodes and right-click to “force download”. This starts the download process.[[image:Smartsolo harvesting #4 copy.png]]
328 -* Completed downloads will appear as new folders in the Downloaded Data panel.
329 -)))
330 -1. (((
331 -**Exporting Data in Readable Format**:
173 +* SN of sensor – SN of battery (optional)
174 +* Site notes and name of location (e.g. Richards garden, Te Mini steam field eastern side) 
332 332  
333 -* Go to the “Tool” menu and select “export seismic data”.
334 -* Tailor other parameters to project preference and ensure "Sample Interval" matches the setting used during node reset (note: the standard used by ANU is 4ms, or 250hz)
335 -* (% class="box warningmessage" %)
336 -(((
337 -**Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!**
338 -)))
339 -* Set "Remove Gain" to the same decibel gain as during programming. By default ANU sets this to 24db for short period nodes (a scaling factor of 15.848932), and 6db (a factor of 2.0) for broadband nodes.
340 -* Set "Remove DC" to "Yes" to centre the data around the zero value
341 -* Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
342 -* [[image:Smartsolo harvesting #9 copy.png]]
343 -* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
344 -* The data will be exported to the SOLODATA folder. For a windows system, the following file explorer page is where you must navigate to to locate your project folder[[image:Smartsolo harvesting #8 copy.png]]
345 -)))
176 +Upload photos into Google Earth and on a shared drive
346 346  
347 -== Smart Solo IGU-16HR Polarity Notice ==
178 +Before removing the instrument have your compass, tape, marker, pen, clipboard, logbook and compass ready (in tote bag!). 
348 348  
349 -See [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]] for discussion. If data is headed to AusPass, we prefer to invert the IGU-16HR channel data manually rather than in the SoloLite software or inverting the response metadata.
180 +Write the station name and the instrument’s serial number, along with 'D' and 'C' and ‘R’, each next to a box to indicate 'download' and 'charge'. Stick this label to the top of the instrument. When dealing with dozens or hundreds of these you WILL start to mix them up after a while! Having an easy visual cue keep them sorted will save you a great deal of confusion later on.
350 350  
351 -**The BD3C-5 data does not require any sort of polarity inversion.**
182 +Take a photo of the entire setup node with the label on it + compass 
352 352  
353 -== 18 Leap Second bug ==
184 +Use existing field logbook to note time, SN and station name plus any notes – including any issues with orientation or level or anything else
354 354  
355 -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 constant 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.
356 356  
357 -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.
187 +== Charging ==
358 358  
359 -{{code language="none"}}
360 -<?xml version="1.0" encoding="UTF-8"?>
361 -<config>
362 - <leapsecond>
363 - <interval>
364 - <start_time>2017-01-01#00:00:00</start_time>
365 - <end_time>2999-12-31#23:59:59</end_time>
366 - <second>18</second>
367 - </interval>
368 - <interval>
369 - <start_time>1970-01-01#00:00:00</start_time>
370 - <end_time>2017-01-01#00:00:00</end_time>
371 - <second>17</second>
372 - </interval>
373 - </leapsecond>
374 - <GPS_distance_threshold_degree>
375 - 4e-5
376 - </GPS_distance_threshold_degree>
377 -</config>
378 -{{/code}}
189 +Clean node prior to charging and harvesting the data
379 379  
191 +Remove battery (and spike) from the sensor by twisting the spike part of the instrument
380 380  
381 -== Handling Nodes During Download ==
193 +Set 16 nodes into the charging box (spikes up)
382 382  
383 -1. (((
384 -**Monitoring Download Indicators**:
195 +Red lights on the box next to the batteries will come on and remain a steady red light while charging. This will change to orange, then to green, then to flashing green when fully charged.
385 385  
386 -* During download, green lights on nodes will blink, and associated red lights on the rack will flash.
387 -* Disconnect nodes properly before unplugging anything.
388 -* Be cautious: if the laptop enters sleep mode, the download will pause.
389 -)))
390 -1. (((
391 -//**Investment in Storage Hardware**~://
197 +This is a good time to check the "C" box on your temporary labels to mark that the unit has been charged
392 392  
393 -* (% class="box warningmessage" %)
394 -(((
395 -* **Use fast external hard drives to avoid limitations in data harvesting.**
199 +[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center"]]
396 396  
397 -* **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
398 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
399 -)))
400 -)))
401 -1. (((
402 -**Metadata and Time Settings**:
403 403  
404 -* Ensure all metadata is saved with the file.
405 -* System auto-determines the earliest data time as the start time. You can set it a day earlier at 00:00:00 for 24-hour data segments starting from midnight.
406 -)))
407 -1. (((
408 -**Finalizing the Download**:
409 409  
410 -* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
411 -)))
203 +== Downloading and Converting Data to MiniSeed ==
412 412  
413 413  
206 +The first thing to do is to register the nodes in the system, so the software can recognize them. To do this, go to the folder where the “SmartSoloApps SoloLite” was installed. Then right-click the deviceconfig.exe program to “run as an administrator” and save the file to the directory of “deviceconfig” (snapshot below). Note that to avoid registering the same node twice, you can simply replace the file each time you do the registration.
414 414  
208 +[[image:1705195543887-977.png]]
415 415  
416 -[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]]
417 417  
211 +Then open the “SoloLite” software, and just go to “File” to make a new project. In this case, you do not need to find the exact 16 nodes that were grouped for script writing. Do not worry about the settings for the seismic recordings for the next window to pop up, as the only way to reset the instruments (e.g., sampling rate, gain etc) is to write script to re-program them.
418 418  
213 +[[image:1705195543890-537.png||data-xwiki-image-style-alignment="center"]]
419 419  
420 420  
421 -[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]]
216 +Once you create the new project, your Data Transfer View panel on the bottom right of the window will show these nodes that have properly connected to the data harvest, including series number, data size etc. It is okay if the “Prospect not matched”, which simply means the project you just created does not match the one you made to program them. Simply select all these nodes, and right click to “force download”, which will initiate the downloading process. Once they are done, you will see new folders created for each slot at your Downloaded Data panel on the top left of the window.
422 422  
218 +[[image:1705195543891-334.png||data-xwiki-image-style-alignment="center"]]
423 423  
220 +At this stage, it means that the raw DLL data of the recording has been downloaded successfully to your local machine. To output data in readable format, such as SAC or miniSEED, click the “Tool” menu and select “export seismic data”. The parameters here should be straightforward to set and tailored to personal reference.
424 424  
425 -[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]]
222 +(% class="box warningmessage" %)
223 +(((
224 +**Please make sure that data is exported as "COUNTS" and NOT "mV"!**
225 +)))
426 426  
227 +(% class="box warningmessage" %)
228 +(((
229 +**Furthermore you must also set "Remove Gain" to the same decibel gain setting that was set during programming! ANU always set this to 18 db (double check) for all types of nodes.**
230 +)))
427 427  
232 +A list of ANU group preferred parameters can be found at the end of this session. One thing to note is that the “Sample Interval” must be set exactly to this used to reset the nodes. Once you are done with the setting, click “prepare” before “run”. If everything works correctly, you should see the reformatting process from the small panel on the bottom left of this popped up window.
428 428  
429 -[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]]
234 +Now the data should be ready. Then you can select these data and right click to output the GPS information associated with them.
430 430  
431 -----
236 +[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center"]]
432 432  
433 -= Instrument Response =
238 +When downloading, all the green lights on the nodes will blink. The associated red lights on the rack will flash when it is downloading, and make sure to disconnect the nodes before you unplug anything. Be careful: if the laptop goes to sleep, the download process will pause.
434 434  
435 -We are aware that there are various different published responses for these instruments and trust very few of them. One has to be careful with how polarity is handled between groups as well, and if one is working in integer counts (the ANSIR default) or mV (unclear why anyone would use this as it makes file sizes enormous). The response information published below is in **counts** and seems to fit well in huddle tests. Note that the response is the same for all channels and all units (e.g. there are no bespoke calibrations!), all appear to be sample rate insensitive, and the IGU data has been inverted (multiplied by -1) as described here: [[5Hz Node Polarity Issues>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodePolarityIssues]]
240 +(% class="box infomessage" %)
241 +(((
242 +**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**. USB-C, USB 3.0, and 4+ Tb of space are highly recommended!
243 +)))
436 436  
437 -== IGU 16HR-3C ==
245 +When downloading, ensure that all metadata is saved along with the file.
438 438  
439 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
440 - 'zeros':[0j, 0j],
441 - 'gain':1,
442 - 'sensitivity': 257019225.55108312}
247 +Start and endtime: the system will automatically find the earliest time of the data and set that as the starting time. However, you can set the time a day earlier with a sharp start of 00:00:00. In this case, all the outputted data segments will be 24 hours long starting from midnight.
443 443  
444 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:16HR_Z_huddle.png||alt="IGU16_Z_huddle.png"]]
249 +//Once downloaded, mark the "D" box on your temporary labels!//
445 445  
446 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:16HR_N_huddle.png||alt="IGU16_N_huddle.png"]]
251 +== Converting data ==
447 447  
448 -== IGU 16-1C ==
253 +Check the data all have been converted to miniseed correctly 
449 449  
450 -The 1C nodes seem to have the same response as the 3-channel IGU-16HR-3C (above), however the response posted at IRIS-NRL seems to imply that there is no poles and zeros information (e.g. a flat/linear response). This is 100% not so.
255 +– 3 files per station per day 
451 451  
452 -[[IGU-16 1C, X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter. Seems to be same response as IGU-16HR-3C.>>image:16HR1C_Z_huddle.png||alt="IGU16_1C_Z_huddle.png"]]
257 +* Files are the same size (NOTE if having memory issues one or more of the components may have 0-1 kb)
258 +* ~~ 5 Gb / node / month
453 453  
454 -== BD3C-5 ==
260 +//Tick ‘R’ box on the node label//
455 455  
456 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
457 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
458 - 'gain':1.69726e-05,
459 - 'sensitivity': 702651512.6046528}
460 460  
461 -Above 0.5 Hz, the BD3C-5 response fits well:
263 +== Cleaning ==
462 462  
463 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
265 +If the nodes are placed in a thick plastic bag at the time of installation, the cleaning procedure should be straightforward. If not you have a lot of work to do before they are returned to us!
464 464  
465 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:BD3C_N_huddle.0.5.png]]
466 -
467 -(% class="wikigeneratedid" %)
468 -Below the corner frequency (0.2 Hz) the phase response still fares well, but amplitude response may need to be dialed in a bit (it seems a bit high). We are working to try to calibrate this a bit better. In the next two figures the filter is **0.1** to 5 Hz:
469 -
470 -
471 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
472 -
473 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
474 -
475 -== IGU-16 Horizontal noise & how to avoid ==
476 -
477 -The** 5 Hz nodes** are susceptible to horizontal noise due to the placement of geophones in the units, **but this can be mitigated by completely burying the units flush with the ground.** In the below example, the node was set on the floor of our basement set on its plastic carrying case support. As such the amount of horizontal noise noticeably increases above ~~ 10Hz.
478 -
479 -[[IGU-16HR-3C Power spectrum huddle test vs a CMG-6TD (S1) and TC120/Centaur combo. The N and E channels have excess noise above 10Hz due to "sticking up" out of the ground.>>image:IGU16_spectrum.png]]
480 -
481 -(% class="wikigeneratedid" %)
482 -The BD3C-5 nodes do not have this issue:
483 -
484 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
485 -
486 -= **Cleaning** =
487 -
488 -When assembled, the nodes are water resistant but not submersible. They can handle a good spray and wipe-down. A stiff plastic brush is helpful to reach areas between the metal spikes on the bottom.
489 -
490 -= **Weights (for shipping)** =
491 -
492 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
493 -
494 -1 bag + 6*IGU-16HR nodes: 18 kg
495 -
496 -1*IGU-16HR data harvester: 21.5 kg
497 -
498 -1*IGU-16HR charger: 26.3 kg
499 -
500 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
501 -
502 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
503 -
504 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
267 +
505 505  )))
506 506  
270 +
507 507  (% class="col-xs-12 col-sm-4" %)
508 508  (((
509 509  (% class="box" %)
... ... @@ -510,11 +510,24 @@
510 510  (((
511 511  **Contents**
512 512  
513 -{{toc/}}
514 -
515 -
277 +(% class="wikitoc" %)
278 +* [[SmartSolo IGU 16HR 3C (5 Hz) Short Period Node>>path:#HSmartSoloIGU16HR3C285Hz29ShortPeriodNode]]
279 +** [[Sub-paragraph>>path:#HSub-paragraph]]
280 +** [[ >>path:#H]]
281 +* [[Smart Solo BD3C-5 (5 second) Broad-Band Node>>path:#HSmartSoloBD3C-5285second29Broad-BandNode]]
282 +** [[GPS Considerations>>path:#HGPSConsiderations]]
283 +* [[Keeping the Instruments Clean>>path:#HKeepingtheInstrumentsClean]]
284 +* [[Charge Time, Instrument Life, and Charge During Storage & Shipping>>path:#HChargeTime2CInstrumentLife2CandChargeDuringStorage26Shipping]]
285 +* [[Best Practices and Guide>>path:#HBestPracticesandGuide]]
286 +** [[Install>>path:#HInstall]]
287 +** [[Removing/Demob>>path:#HRemoving2FDemob]]
288 +** [[Charging>>path:#HCharging]]
289 +** [[Downloading and Converting Data to MiniSeed>>path:#HDownloadingandConvertingDatatoMiniSeed]]
290 +** [[Converting data>>path:#HConvertingdata]]
291 +** [[Cleaning>>path:#HCleaning]]
516 516  )))
517 517  
294 +
518 518  (% class="box" %)
519 519  (((
520 520  = SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
... ... @@ -525,19 +525,15 @@
525 525  
526 526  |(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
527 527  |(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
528 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
305 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
529 529  |(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
530 530  |(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
531 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
532 -Lithium-ion battery contained in equipment (168.84 Wh)
533 -
534 -UN3481 PI967 S1
308 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh
535 535  )))
536 -)))
537 537  
538 538  (% class="box" %)
539 539  (((
540 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
313 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
541 541  
542 542  [[image:smartsolo node.jpg]]
543 543  
... ... @@ -544,114 +544,13 @@
544 544  [[image:smartsolo node 2.jpg]]
545 545  
546 546  |(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
547 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
548 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
549 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
320 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
321 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
322 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.3 kg
550 550  |(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
551 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
552 -Lithium-ion battery contained in equipment (96.48 Wh)
553 -
554 -UN3481 PI967 S2
324 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Li_etc XXAh
555 555  )))
556 -)))
557 557  
558 -(% class="box" %)
559 -(((
560 560  
561 -
562 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
563 -
564 -
565 -[[image:Screenshot 2025-08-01 161027.png]]
566 -
567 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
568 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
569 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
570 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
571 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
572 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
573 -Lithium-ion battery contained in equipment (38.48 Wh)
574 -
575 -UN3481 PI967 S2
576 576  )))
577 577  )))
578 -
579 -(% class="box" %)
580 -(((
581 -= SmartSolo BD3C-16 Portable Battery Charger =
582 -
583 -[[image:20250729_125049.jpg]]
584 -
585 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
586 -|**Input rating**|100-210V - 50/60Hz
587 -|**Power**|1000W
588 -|**Weight**|14.5 kg
589 -|**Weight with cables**|21 kg
590 -)))
591 -
592 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
593 -(((
594 -= SmartSolo IGU-16 Portable Data Harvester =
595 -
596 -[[image:20250729_124747.jpg]]
597 -
598 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
599 -|**Input rating**|100-210V - 50/60Hz
600 -|**Power**|100W
601 -|**Weight**|21.5 - 24 kg
602 -|**Capacity**|16 nodes
603 -|**Download Speed**|20MB/sec/slot
604 -)))
605 -
606 -(% class="box" %)
607 -(((
608 -= SmartSolo IGU-16 Portable Battery Charger =
609 -
610 -[[image:20250729_124644.jpg]]
611 -
612 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
613 -|**Input rating**|100-210V - 50/60 Hz
614 -|**Power**|640 W
615 -|**Weight**|26.3 kg
616 -|**Capacity**|16 nodes
617 -)))
618 -
619 -(% class="box" %)
620 -(((
621 -= SmartSolo BD3C-5 Carry Case =
622 -
623 -[[image:20250729_124957.jpg]]
624 -
625 -
626 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
627 -|**Weight**|8.2 kg
628 -|**Capacity**|6 nodes
629 -)))
630 -
631 -(% class="box" %)
632 -(((
633 -= SmartSolo IGU-16 3C Carry Bag =
634 -
635 -[[image:20250729_124502.jpg]]
636 -
637 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
638 -|**Weight**|(((
639 -3.6kg (empty)
640 -
641 -18.0kg (full)
642 -)))
643 -|**Capacity**|6 nodes
644 -)))
645 -
646 -(% class="box" %)
647 -(((
648 -= SmartSolo IGU-16 1C Carry Bag =
649 -
650 -[[image:20250729_124558.jpg]]
651 -
652 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
653 -|**Weight**|
654 -|**Capacity**|8 nodes
655 -)))
656 -)))
657 -)))
16HR1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -92.1 KB
Content
16HR_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -88.4 KB
Content
16HR_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -80.8 KB
Content
1706153266647-145.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sima
Size
... ... @@ -1,1 +1,0 @@
1 -1.7 MB
Content
1706153354750-415.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sima
Size
... ... @@ -1,1 +1,0 @@
1 -2.1 MB
Content
1706153556166-231.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.sima
Size
... ... @@ -1,1 +1,0 @@
1 -839.4 KB
Content
20250729_124502.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -318.3 KB
Content
20250729_124558.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -376.8 KB
Content
20250729_124644.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -528.0 KB
Content
20250729_124747.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -488.5 KB
Content
20250729_124957.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -532.5 KB
Content
20250729_125049.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -457.6 KB
Content
5Hz_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -109.8 KB
Content
5S_node_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.KB
Size
... ... @@ -1,1 +1,0 @@
1 -114.2 KB
Content
BB_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -111.5 KB
Content
BD3C_N_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.9 KB
Content
BD3C_N_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -68.4 KB
Content
BD3C_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.1 KB
Content
BD3C_Z_huddle.0.1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -64.3 KB
Content
BD3C_Z_huddle.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.5 KB
Content
BD3C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -52.1 KB
Content
BD3C_psd.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -73.7 KB
Content
IGU16_1C_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -72.3 KB
Content
IGU16_N_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.7 KB
Content
IGU16_Z_huddle.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -67.4 KB
Content
IGU16_spectrum.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -65.0 KB
Content
SP_programming.labels.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -106.7 KB
Content
Screenshot 2025-08-01 161027.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -82.8 KB
Content
Smartsolo harvesting #4 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.8 KB
Content
Smartsolo harvesting #4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.8 KB
Content
Smartsolo harvesting #6 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -33.6 KB
Content
Smartsolo harvesting #8 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -38.3 KB
Content
Smartsolo harvesting #8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -60.0 KB
Content
Smartsolo harvesting #9 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content
example_metadata.txt
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -2.7 KB
Content
... ... @@ -1,46 +1,0 @@
1 -# AKL-HR Node Array (AHNA) code X5
2 -CITE: Name, Name, and Name. (2023). A Node Array [Data set]. International Federation of Digital Seismograph Networks. https://doi.org/10.7914/8jxr-7029
3 -
4 -#SITE START END LAT LONG ELEV SPS RECORDER S/N SENSOR S/N PROPERTY,LOCALITY,COUNTRY COMMENTS
5 -
6 -# INSTALL
7 -AKL01 20-05-2023T00:00 30-06-2023T00:00 -37.0471 175.5245 75 250 SSNODE_C 590001950 SSNODE_5S 590001950 "Te Puru,Hauraki,NZ"
8 -AKL02 20-05-2023T00:00 30-06-2023T00:00 -36.7476 175.5026 70 250 SSNODE_C 590001943 SSNODE_5S 590001943 "Coromandel Town,Hauraki,NZ"
9 -AKL03 20-05-2023T00:00 30-06-2023T00:00 -36.9694 175.5020 98 250 SSNODE_C 590002068 SSNODE_5S 590002068 "Te Mata,Hauraki,NZ"
10 -AKL05 19-05-2023T19:00 22-02-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001957 SSNODE_5S 590001957 "South Head South,Auckland,NZ" "site was disturbed"
11 -AKL06 19-05-2023T19:00 30-06-2023T00:00 -37.2459 175.3426 34 250 SSNODE_C 590001930 SSNODE_5S 590001930 "Back Miranda,Auckland,NZ"
12 -AKB05 02-05-2023T00:37 30-06-2023T00:00 -36.6651 175.4800 63 250 TSAWR TS085A TRILL120 4875 "Colville,Hauraki,NZ"
13 -
14 -# SERVICE 1
15 -AKL05 22-02-2023T00:00 30-06-2023T00:00 -36.5996 174.3312 102 250 SSNODE_C 590001999 SSNODE_.2S 590001999 "South Head South,Auckland,NZ" "swapped node to shortperiod"
16 -
17 -
18 -
19 -
20 -################### ANY LINE BEGINNING WITH # will be commented! Comments are good!
21 -
22 -
23 -# NOTES
24 -# the start/end time is not critical, but good to have. what IS critical are the times of instrument changes as this potentially affects response information
25 -# to mark equipment changes, add a new line with an updated start date (e.g. AKL05 above)
26 -# can use tabs or spaces, but spaces tend to look nicer. formatting ultimately doesn't matter too much so long as there is any sort of "white space" between the fields
27 -# if you don't know a serial number, put 999. if you don't know the elevation, put 0
28 -# for Nodes, put the same serial number for both Recoder and Sensor (since they are the same!)
29 -
30 -
31 -# EXAMPLE INSTRUMENT LABELS
32 -#LPR200 = ANU LPR-200 logger (beige box)
33 -#TSAWR = ANU TerraSAWR logger (yellow box)
34 -
35 -#TRILL120 = Trillium Compact 120s
36 -#TRILL20 = Trillium Compact 20s
37 -#TRILL120PH = Trillium Compact 120s PostHole
38 -#CMG6TD = Guralp 6TD
39 -#CMG3ESP = Guralp 3ESP
40 -#3DLITE = Lenarrtz 3D-LITE
41 -
42 -#SSNODE_C = output was in COUNTS (there is also SSNODE_MV, if you (accidentally!) output to millivolts etc)
43 -#SSNODE_5S = broadband (can also use SSNODE_BB)
44 -#SSNODE_.2S = shortperiod (can also use SSNODE_SP)
45 -
46 -#it doesn't matter too much what you use for equipment labels, so long as they are consistent and otherwise defined somewhere in the comments!
XWiki.XWikiComments[0]
Date
... ... @@ -1,1 +1,0 @@
1 -2026-07-09 10:45:51.967
Author
... ... @@ -1,1 +1,0 @@
1 -Mark Goldman
Comment
... ... @@ -1,1 +1,0 @@
1 -I can verify that the default orientation for the SmartSolo 3C nodes is positive values for case motion to the South, West, and downwards. We have co-located nodes with permanent stations and noticed this correlation when comparing waveforms.
XWiki.XWikiRights[0]
Allow/Deny
... ... @@ -1,1 +1,0 @@
1 -Allow
Groups
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiAllGroup
Levels
... ... @@ -1,1 +1,0 @@
1 -comment
XWiki.XWikiRights[1]
Allow/Deny
... ... @@ -1,1 +1,0 @@
1 -Allow
Levels
... ... @@ -1,1 +1,0 @@
1 -comment
Users
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest