Skip to Content
Last modified by robert on 2026/02/27 19:58
From version 105.5
edited by robert
on 2026/02/17 15:49
Change comment: There is no comment for this version
To version 38.1
edited by Sima Mousavi
on 2024/01/25 14:31
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,113 +2,56 @@
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. The default gain should be 24 db for the 16HR-3C and 6 db for the BD3C-5
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')**
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
10 +~*~**this needs to be reformatted
14 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.
12 +== **Pre-Fieldwork Preparation** ==
16 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 59  **INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
60 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.**
20 +**Plan on 1 Tb to store ALL data for 50 nodes @ 250 Hz and a single ~~30 day occupation**
64 64  )))
22 +)))
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 76  = **Installation** =
77 77  
78 -(% class="box infomessage" %)
79 -(((
80 -**Field logs are a critical component of fieldwork and this is especially the case for large N nodal deploys. Take notes!**
81 -)))
26 +=== **1- Logbook documentation** ===
82 82  
83 -== 1. Logbook documentation ==
84 -
85 85  (((
86 -**Essential Details** for field logs:
29 +**Essential Details**: Record the following in a logbook:
87 87  
88 88  * Station name
89 -* Latitude, longitude, elevation
32 +* Latitude and longitude
90 90  * Names of team members present
91 -* Date and both local & UTC time of installation/removal
92 -* Serial number (SN) of the TOP HALF of the sensor (if a BD3C-5, there is only one serial number)
93 -* 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)
34 +* Date and local time of installation
35 +* Serial number (SN) of the sensor
36 +* Detailed notes on the site conditions and setup
94 94  
95 -[[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!
96 -
97 -== 2. Node Placement ==
38 +=== **2- Node Placement** ===
98 98  )))
99 99  
41 +**Protection**: Place nodes inside thick, landfill biodegradable plastic bags for environmental protection.
42 +
100 100  **Site Analysis**:
101 101  
102 -* **Take compass measurements away from the sensor as it will affect your measurement.**
103 -* Take photographs from various angles to document the site setup thoroughly.
104 -* Include a detailed site description in your notes
45 +* Conduct compass measurements away from the node and metallic structures, adjusting for inclination angle.
46 +* Take multiple photographs from various angles to document the site setup thoroughly.
47 +* 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)
105 105  
106 -== 3. GPS Considerations ==
49 +=== **3- GPS Considerations** ===
107 107  
108 108  (% class="wikigeneratedid" %)
109 -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. **These nodes will not start recording without attaining a GPS lock** and repeated attempts will excessively drain the battery.
52 +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.
110 110  
111 -== 4. Visibility and Location Marking ==
54 +=== **4- Visibility and Location Marking** ===
112 112  
113 113  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
114 114  
... ... @@ -117,53 +117,63 @@
117 117  * Use a GPS device to mark the instrument's exact location.
118 118  * Record this location in both your paper notes and the GPS device.
119 119  
120 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
63 +=== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5- Charge Time, Pre-Deployment & Post-Deployment**(%%) ===
121 121  
122 122  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
123 123  * **Pre-Deployment Charging**:
124 -** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
67 +** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge right before deployment.
125 125  
126 126  * **Operational Duration**:
127 -** 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.
70 +** When recording at 250 Hz, with GPS on and Bluetooth disabled, the instruments are expected to last about 30 days per charge cycle.
128 128  
129 129  * **Post-Retrieval Charging**:
130 -** After retrieval, charge the instruments to about 50-60% (indicated by ORANGE LED) unless they are to be immediately re-deployed or transported.
131 -* **State of Charge (SoC) for Storage**:
132 -** Maintain a battery charge level of around 50-60% (i.e., ORANGE) for storage.
133 -** This charge level is recommended to prevent battery damage, and should be checked every six months.
134 -** Nodes should //__not be stored at full-charge (GREEN), or 0-charge (RED).__//
135 -** Storage at 0-charge damages lithium batteries**.**
136 -* **SoC for Transport:**
137 -** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
73 +** Do not store the instruments with completely drained batteries.
74 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) for optimal battery health.
138 138  
139 -(((
140 -== 6. Data Sharing and Metadata Creation ==
76 +* **Storage and Shipping Charge Level**:
77 +** Maintain a battery charge level of around 50-60% for both storage and shipping purposes.
78 +** This charge level is recommended to prevent battery damage and is safe for transportation.
79 +
80 +=== ===
81 +
82 +* (((
83 +=== **6- Data Sharing and Metadata Creation** ===
141 141  )))
142 142  
143 143  **GPS Data**:
144 144  
145 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
88 +* Download the GPS file to a laptop.
89 +* Share this file on a drive accessible to all team members for uniform understanding of node locations.
146 146  
147 147  **Photo Sharing**:
148 148  
149 -* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
93 +* Upload site photos to a shared platform (OneDrive, Dropbox, etc.).
94 +* Integrating photos into Google Maps or Google Earth can be particularly beneficial for easy location referencing.
150 150  
151 151  **Metadata File**:
152 152  
153 -* 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.
98 +* Create a metadata XML file for each node, which is essential for data organisation and future reference.
154 154  
155 -== 7. Additional Best Practices ==
100 +=== **7- Additional Best Practices** ===
156 156  
157 -* **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.
102 +* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations.
103 +* **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.
158 158  
105 +* (((
106 +==== **Keeping the Instruments Clean** ====
107 +)))
108 +* (((
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.
110 +)))
111 +
159 159  ----
160 160  
161 -= **Seismic Station Demobilization and Documentation** =
114 +=== **Seismic Station Demobilization and Documentation** ===
162 162  
163 163  1. (((
164 164  **Preparation for Demobilization**:
165 165  
166 -* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag.
119 +* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, clipboard, logbook, and compass ready in your tote bag.
167 167  )))
168 168  1. (((
169 169  **Locating the instrument**:
... ... @@ -175,7 +175,7 @@
175 175  1. (((
176 176  **Labeling Instruments for Demobilization**:
177 177  
178 -* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.
131 +* Write the station name and the instrument’s serial number on a label.
179 179  * Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
180 180  * Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
181 181  )))
... ... @@ -196,78 +196,55 @@
196 196  
197 197  * Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.
198 198  * Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.
199 -
200 -
201 201  )))
202 202  
203 -[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]]
154 +[[image:blob:https://anu365-my.sharepoint.com/aba1fadc-c966-4177-9f2c-7cbd734bff46]] [[image:blob:https://anu365-my.sharepoint.com/aba1fadc-c966-4177-9f2c-7cbd734bff46]]
204 204  
205 205  ----
206 206  
207 -= **Charging Procedure for Seismic Nodes** =
158 +=== **Charging Procedure for Seismic Nodes** ===
208 208  
209 -(((
210 -== 1. Preparation for Charging: ==
160 +1. (((
161 +**Preparation for Charging**:
211 211  
212 212  * 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.
213 213  )))
165 +1. (((
166 +**Disassembling the Node**:
214 214  
215 -(((
216 -== 2. Disassembling the Node: ==
217 -
218 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
168 +* Carefully remove the battery and the spike from the sensor. This is typically done by twisting the spike part of the instrument to release these components.
219 219  )))
170 +1. (((
171 +**Setting Nodes in the Charging Box**:
220 220  
221 -(((
222 -== 3. Setting Nodes in the Charging Box: ==
223 -
224 -* Connect to a safe indoor power supply, and turn on (red rocker switch).
225 -* Charging will begin automatically when nodes are inserted in the charging rack.
226 -* Place IGU-16HR battery sections upside-down in the rack, oriented with the terminal connectors.
173 +* Place up to 16 nodes into the charging box, arranging them with the spikes pointing upwards. This configuration is essential for proper connection and efficient charging.
227 227  )))
175 +1. (((
176 +**Monitoring the Charging Process**:
228 228  
229 -(((
230 -== 4. Monitoring the Charging Process: ==
231 -
232 -* Lights adjacent to the batteries will illuminate, indicating that charging is underway.
233 -* 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.
178 +* Once the nodes are set in the charging box and the charging process begins, red lights adjacent to the batteries will illuminate. These lights indicate that charging is underway.
179 +* Observe the transition of the lights from steady red to orange, then to green, and finally to flashing green. A flashing green light signifies that the batteries are fully charged.
234 234  )))
181 +1. (((
182 +**Updating Charge Status**:
235 235  
236 -(((
237 -== 5. Updating Charge Status: ==
238 -
239 239  * 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.
240 240  * This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
241 241  )))
242 242  
243 -[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]]
188 +[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center"]]
244 244  
245 245  
246 246  
247 247  
248 -{{{
249 - }}}
193 +[[image:1706153354750-415.png]]
250 250  
251 251  ----
252 252  
253 -= **Downloading and Converting Seismic Data to MiniSeed Format** =
197 +=== **Downloading and Converting Seismic Data to MiniSeed Format** ===
254 254  
255 -(% class="wikigeneratedid" %)
256 -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]]
199 +==== **Node Registration and Software Setup** ====
257 257  
258 -== Connection tips: ==
259 -
260 -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:
261 -
262 -* Place the node on the harvester gently, then firmly press it down onto the pins.
263 -* 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.
264 -* 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.
265 -* 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!
266 -
267 -
268 -
269 -== Node Registration and Software Setup ==
270 -
271 271  1. (((
272 272  **Registering Nodes in the System**:
273 273  
... ... @@ -284,29 +284,8 @@
284 284  * Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
285 285  )))
286 286  
287 -== File structure ==
217 +==== **Data Downloading Process** ====
288 288  
289 -There are essentially three main folders where relevant PROSPECT and PROJECT DATA is stored. Individual projects will be found as subfolders in these.
290 -
291 -=== SOLOLITE ===
292 -
293 -This folder stores SoloLite config files and parameters. Nothing too important stored here, you can always start over and re-create this.
294 -
295 -=== DCCDATA ===
296 -
297 -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.
298 -
299 -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)//
300 -
301 -Then in the SoloLite software, go to tools > Reanalyze Seismic Data
302 -
303 -=== SOLODATA ===
304 -
305 -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.
306 -
307 -
308 -== Data Downloading Process ==
309 -
310 310  1. (((
311 311  **Initiating Data Download**:
312 312  
... ... @@ -323,48 +323,14 @@
323 323  * Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
324 324  * (% class="box warningmessage" %)
325 325  (((
326 -* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
235 +* **Ensure to export data as "COUNTS", not "mV".**
327 327  
328 -* **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.**
237 +* **Set "Remove Gain" to the same decibel gain as during programming (ANU usually sets this to 18 db, but double-check).**
329 329  )))
330 330  )))
331 331  
332 -== Smart Solo IGU-16HR Polarity Notice ==
241 +==== **Handling Nodes During Download** ====
333 333  
334 -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.
335 -
336 -**The BD3C-5 data does not require any sort of polarity inversion.**
337 -
338 -== 18 Leap Second bug ==
339 -
340 -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.
341 -
342 -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.
343 -
344 -{{code language="none"}}
345 -<?xml version="1.0" encoding="UTF-8"?>
346 -<config>
347 - <leapsecond>
348 - <interval>
349 - <start_time>2017-01-01#00:00:00</start_time>
350 - <end_time>2999-12-31#23:59:59</end_time>
351 - <second>18</second>
352 - </interval>
353 - <interval>
354 - <start_time>1970-01-01#00:00:00</start_time>
355 - <end_time>2017-01-01#00:00:00</end_time>
356 - <second>17</second>
357 - </interval>
358 - </leapsecond>
359 - <GPS_distance_threshold_degree>
360 - 4e-5
361 - </GPS_distance_threshold_degree>
362 -</config>
363 -{{/code}}
364 -
365 -
366 -== Handling Nodes During Download ==
367 -
368 368  1. (((
369 369  **Monitoring Download Indicators**:
370 370  
... ... @@ -380,7 +380,6 @@
380 380  * **Use fast external hard drives to avoid limitations in data harvesting.**
381 381  
382 382  * **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
383 -* **The USB type for the harvester is TYPE-A, the typical normal rectangular shape.**
384 384  )))
385 385  )))
386 386  1. (((
... ... @@ -397,247 +397,270 @@
397 397  
398 398  )))
399 399  
400 -[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
274 +[[image:1706153266647-145.png]]
401 401  
276 +[[Caption>>image:1705195543887-977.png]]
402 402  
403 403  
404 -[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]]
279 +[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center"]]
405 405  
406 406  
407 407  
283 +[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center"]]
408 408  
409 -[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]]
410 410  
411 411  
287 +[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center"]]
412 412  
413 -[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]]
289 +----
414 414  
291 +=== **Cleaning** ===
415 415  
293 +**Procedure for Seismic Nodes:**
416 416  
417 -[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]]
295 +* 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!
418 418  
419 -----
297 += =
420 420  
421 -= Instrument Response =
299 += SmartSolo IGU 16HR 3C (5 Hz) Short Period Node =
422 422  
423 -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]]
301 +blahblah
424 424  
425 -== IGU 16HR-3C ==
303 +== Sub-paragraph ==
426 426  
427 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
428 - 'zeros':[0j, 0j],
429 - 'gain':1,
430 - 'sensitivity': 257019225.55108312}
431 431  
432 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
306 +== [[image:1705196270090-364.png]] ==
433 433  
434 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_N_huddle.png]]
435 435  
436 -== IGU 16-1C ==
309 += Smart Solo BD3C-5 (5 second) Broad-Band Node =
437 437  
438 -The 1C nodes seem to have a slightly different response to the 3C (TBA)
311 +Lorem
439 439  
440 -== BD3C-5 ==
441 441  
442 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
443 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
444 - 'gain':1.69726e-05,
445 - 'sensitivity': 702651512.6046528}
314 +== GPS Considerations ==
446 446  
447 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.png]]
316 +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.
448 448  
449 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_N_huddle.png]]
318 += Keeping the Instruments Clean =
450 450  
451 -(% class="wikigeneratedid" %)
452 -Below the corner frequency 0.2 Hz (i.e. 5 seconds) the response still does a good job, but may need to be dialed in a bit. We are looking into this.
320 +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.
453 453  
454 -(% class="wikigeneratedid" %)
455 -
456 456  
457 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_Z_huddle.0.1.png]]
323 += Charge Time, Instrument Life, and Charge During Storage & Shipping =
458 458  
459 -[[BD3C 0.1 to 5 Hz bandpass>>image:BD3C_N_huddle.0.1.png]]
325 +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.
460 460  
461 -== IGU-16 Horizontal noise & how to avoid ==
327 +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.
462 462  
463 -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.
464 464  
465 -[[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]]
330 += Best Practices and Guide =
466 466  
467 -(% class="wikigeneratedid" %)
468 -The BD3C-5 nodes do not have this issue:
332 +== Install ==
469 469  
470 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
334 +Logbook is required (used again for pick up & metadata creation)
471 471  
472 -= **Cleaning** =
336 +- station name
473 473  
474 -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.
338 +- lat / long
475 475  
476 -= **Weights (for shipping)** =
340 +- team members
477 477  
478 -The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
342 +- date and local time
479 479  
480 -1 bag + 6*IGU-16HR nodes: 18 kg
344 +- SN of sensor
481 481  
482 -1*IGU-16HR data harvester: 21.5 kg
346 +- notes on site
483 483  
484 -1*IGU-16HR charger: 26.3 kg
348 +Place nodes in thick (“landfill biodegradable”) plastic bags in the hole
485 485  
486 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
350 +Take compass measurement away from node and fences [make sure to adjust inclination angle]
487 487  
488 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
352 +Take many photos from the site from different angles 
489 489  
490 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
491 -)))
354 +Add a precise site description to the notes such as distances and orientations from landmarks 
492 492  
493 -(% class="col-xs-12 col-sm-4" %)
494 -(((
495 -(% class="box" %)
496 -(((
497 -**Contents**
356 +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.
498 498  
499 -{{toc/}}
358 +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.
500 500  
501 -
502 -)))
360 +Download the GPS (Garmin) file to a laptop and share drive to share with other GPS devices
503 503  
504 -(% class="box" %)
505 -(((
506 -= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
362 +Share photos in a shared location (Google photos, OneDrive, Dropbox, etc), but most useful are those added to a Google Maps/Earth location
507 507  
508 -[[image:Smartsolo IGU BD3C 5 (2).jpg]]
364 +Create metadata .xml file
509 509  
510 -[[image:smartsolo.jpg]]
511 511  
512 -|(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
513 -|(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
514 -|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)Φ158 x160mm(H)
515 -|(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
516 -|(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
517 -|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
518 -Lithium-ion battery contained in equipment (168.84 Wh)
367 +== Removing/Demob ==
519 519  
520 -UN3481 PI967 S1
521 -)))
522 -)))
369 +Download and then use the GPS file to locate the node 
523 523  
524 -(% class="box" %)
525 -(((
526 -= SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]]3C =
371 +Use Google Maps / Google Earth to create a kmz file that can then be imported onto your phone.  
527 527  
528 -[[image:smartsolo node.jpg]]
529 529  
530 -[[image:smartsolo node 2.jpg]]
374 +Upload photos of the site  
531 531  
532 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
533 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)76.7 V/m/s
534 -|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm(H)
535 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
536 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
537 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
538 -Lithium-ion battery contained in equipment (96.48 Wh)
376 +- station name
539 539  
540 -UN3481 PI967 S2
541 -)))
542 -)))
378 +- latitude
543 543  
544 -(% class="box" %)
545 -(((
546 -
380 +- longitude
547 547  
548 -= SmartSolo [[IGU-16>>url:https://smartsolo.com/cp-3.html]]1C =
382 +- elevation
549 549  
384 +* SN of sensor – SN of battery (optional)
385 +* Site notes and name of location (e.g. Richards garden, Te Mini steam field eastern side) 
550 550  
551 -[[image:Screenshot 2025-08-01 161027.png]]
387 +Upload photos into Google Earth and on a shared drive
552 552  
553 -|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 413Hz
554 -|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)80 V/m/s
555 -|(% style="width:187px" %)**Size (without spike)**|(% style="width:224px" %)95mm(L) × 103mm(W) × 118mm(H)
556 -|(% style="width:187px" %)**Weight**|(% style="width:224px" %)1.1 kg
557 -|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)8 Gb
558 -|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
559 -Lithium-ion battery contained in equipment (38.48 Wh)
389 +Before removing the instrument have your compass, tape, marker, pen, clipboard, logbook and compass ready (in tote bag!). 
560 560  
561 -UN3481 PI967 S2
562 -)))
563 -)))
391 +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.
564 564  
565 -(% class="box" %)
566 -(((
567 -= SmartSolo BD3C-16 Portable Battery Charger =
393 +Take a photo of the entire setup node with the label on it + compass 
568 568  
569 -[[image:20250729_125049.jpg]]
395 +Use existing field logbook to note time, SN and station name plus any notes – including any issues with orientation or level or anything else
570 570  
571 -|**Dimensions (LxHxW)**|558 x 357 x 300mm
572 -|**Input rating**|100-210V - 50/60Hz
573 -|**Power**|1000W
574 -|**Weight**|14.5 kg
575 -|**Weight with cables**|21 kg
397 +[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center"]]
398 +
399 +
400 +== Charging ==
401 +
402 +Clean node prior to charging and harvesting the data
403 +
404 +Remove battery (and spike) from the sensor by twisting the spike part of the instrument
405 +
406 +Set 16 nodes into the charging box (spikes up)
407 +
408 +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.
409 +
410 +This is a good time to check the "C" box on your temporary labels to mark that the unit has been charged
411 +
412 +
413 +
414 +== Downloading and Converting Data to MiniSeed ==
415 +
416 +
417 +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.
418 +
419 +[[image:1705195543887-977.png]]
420 +
421 +
422 +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.
423 +
424 +[[image:1705195543890-537.png||data-xwiki-image-style-alignment="center"]]
425 +
426 +
427 +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.
428 +
429 +[[image:1705195543891-334.png||data-xwiki-image-style-alignment="center"]]
430 +
431 +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.
432 +
433 +(% class="box warningmessage" %)
434 +(((
435 +**Please make sure that data is exported as "COUNTS" and NOT "mV"!**
576 576  )))
577 577  
578 -(% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
438 +(% class="box warningmessage" %)
579 579  (((
580 -= SmartSolo IGU-16 Portable Data Harvester =
440 +**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.**
441 +)))
581 581  
582 -[[image:20250729_124747.jpg]]
443 +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.
583 583  
584 -|**Dimensions (LxHxW)**|625 x 500 x 366mm
585 -|**Input rating**|100-210V - 50/60Hz
586 -|**Power**|100W
587 -|**Weight**|21.5 - 24 kg
588 -|**Capacity**|16 nodes
589 -|**Download Speed**|20MB/sec/slot
590 -)))
445 +Now the data should be ready. Then you can select these data and right click to output the GPS information associated with them.
591 591  
592 -(% class="box" %)
447 +[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center"]]
448 +
449 +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.
450 +
451 +(% class="box infomessage" %)
593 593  (((
594 -= SmartSolo IGU-16 Portable Battery Charger =
453 +**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!
454 +)))
595 595  
596 -[[image:20250729_124644.jpg]]
456 +When downloading, ensure that all metadata is saved along with the file.
597 597  
598 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
599 -|**Input rating**|100-210V - 50/60 Hz
600 -|**Power**|640 W
601 -|**Weight**|26.3 kg
602 -|**Capacity**|16 nodes
458 +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.
459 +
460 +//Once downloaded, mark the "D" box on your temporary labels!//
461 +
462 +== Converting data ==
463 +
464 +Check the data all have been converted to miniseed correctly 
465 +
466 +– 3 files per station per day 
467 +
468 +* Files are the same size (NOTE if having memory issues one or more of the components may have 0-1 kb)
469 +* ~~ 5 Gb / node / month
470 +
471 +//Tick ‘R’ box on the node label//
472 +
473 +
474 +== Cleaning ==
475 +
476 +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!
477 +
478 +
603 603  )))
604 604  
481 +
482 +(% class="col-xs-12 col-sm-4" %)
483 +(((
605 605  (% class="box" %)
606 606  (((
607 -= SmartSolo BD3C-5 Carry Case =
486 +**Contents**
608 608  
609 -[[image:20250729_124957.jpg]]
610 -
611 -
612 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
613 -|**Weight**|8.2 kg
614 -|**Capacity**|6 nodes
488 +(% class="wikitoc" %)
489 +* [[SmartSolo IGU 16HR 3C (5 Hz) Short Period Node>>path:#HSmartSoloIGU16HR3C285Hz29ShortPeriodNode]]
490 +** [[Sub-paragraph>>path:#HSub-paragraph]]
491 +** [[ >>path:#H]]
492 +* [[Smart Solo BD3C-5 (5 second) Broad-Band Node>>path:#HSmartSoloBD3C-5285second29Broad-BandNode]]
493 +** [[GPS Considerations>>path:#HGPSConsiderations]]
494 +* [[Keeping the Instruments Clean>>path:#HKeepingtheInstrumentsClean]]
495 +* [[Charge Time, Instrument Life, and Charge During Storage & Shipping>>path:#HChargeTime2CInstrumentLife2CandChargeDuringStorage26Shipping]]
496 +* [[Best Practices and Guide>>path:#HBestPracticesandGuide]]
497 +** [[Install>>path:#HInstall]]
498 +** [[Removing/Demob>>path:#HRemoving2FDemob]]
499 +** [[Charging>>path:#HCharging]]
500 +** [[Downloading and Converting Data to MiniSeed>>path:#HDownloadingandConvertingDatatoMiniSeed]]
501 +** [[Converting data>>path:#HConvertingdata]]
502 +** [[Cleaning>>path:#HCleaning]]
615 615  )))
616 616  
505 +
617 617  (% class="box" %)
618 618  (((
619 -= SmartSolo IGU-16 3C Carry Bag =
508 += SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
620 620  
621 -[[image:20250729_124502.jpg]]
510 +[[image:Smartsolo IGU BD3C 5 (2).jpg]]
622 622  
623 -|**Dimensions (LxHxW)**|230 x 340 x 310mm
624 -|**Weight**|(((
625 -3.6kg (empty)
512 +[[image:smartsolo.jpg]]
626 626  
627 -18.0kg (full)
514 +|(% style="width:189px" %)**Frequency Band**|(% style="width:221px" %)5 Seconds to 150Hz
515 +|(% style="width:189px" %)**Sensitivity**|(% style="width:221px" %)200 V/m/s
516 +|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
517 +|(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
518 +|(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
519 +|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh
628 628  )))
629 -|**Capacity**|6 nodes
630 -)))
631 631  
632 632  (% class="box" %)
633 633  (((
634 -= SmartSolo IGU-16 1C Carry Bag =
524 += SmartSolo [[IGU-16HR>>url:https://smartsolo.com/cp-3.html]] =
635 635  
636 -[[image:20250729_124558.jpg]]
526 +[[image:smartsolo node.jpg]]
637 637  
638 -|**Dimensions (LxHxW)**|225 x 200 x 550mm
639 -|**Weight**|
640 -|**Capacity**|8 nodes
528 +[[image:smartsolo node 2.jpg]]
529 +
530 +|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
531 +|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
532 +|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
533 +|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.3 kg
534 +|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
535 +|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Li_etc XXAh
641 641  )))
537 +
538 +
642 642  )))
643 643  )))
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 -72.1 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 -52.1 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_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
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.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