Skip to Content
Last modified by robert on 2026/08/12 13:08
From version 119.1
edited by robert
on 2026/08/12 13:08
Change comment: There is no comment for this version
To version 115.1
edited by robert
on 2026/06/29 08:23
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -106,17 +106,7 @@
106 106  
107 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 108  
109 -== 2. Burial ==
110 -
111 -**ALL nodes should be buried flush with the ground, no exceptions**. If the node is sticking up the data data quality will be significantly reduced (especially the horizontal channels, see [[below>>https://auspass.edu.au/xwiki/bin/view/Instrumentation/SmartSolo%20Nodes/#HIGU-16Horizontalnoise26howtoavoid]]). It also catches wind, makes them more visible, etc. But mostly it makes the data bad.
112 -
113 -//Don't be lazy. Do it right. //
114 -
115 -[[An example of what not to do.>>image:1786503344572-296.jpg||data-xwiki-image-style-alignment="center" height="341" width="404"]]
116 -
117 -[[North channel PSD of the sensor in the picture above (it is not good)>>image:1786503812585-338.02.28 PM.png||data-xwiki-image-style-alignment="center" height="244" width="451"]]
118 -
119 -== 3. Node Placement ==
109 +== 2. Node Placement ==
120 120  )))
121 121  
122 122  **Site Analysis**:
... ... @@ -125,12 +125,12 @@
125 125  * Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it.
126 126  * Include a detailed site description in your notes.
127 127  
128 -== 4. GPS Considerations ==
118 +== 3. GPS Considerations ==
129 129  
130 130  (% class="wikigeneratedid" %)
131 131  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.
132 132  
133 -== 5. Visibility and Location Marking ==
123 +== 4. Visibility and Location Marking ==
134 134  
135 135  **Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
136 136  
... ... @@ -139,11 +139,12 @@
139 139  * 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.
140 140  * Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]).
141 141  
142 -== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)6. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
132 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)5. Charge Time, Pre-Deployment & Post-Deployment(%%) ==
143 143  
144 144  * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
145 145  * **Pre-Deployment Charging**:
146 146  ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
137 +
147 147  * **Operational Duration**:
148 148  ** 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.
149 149  
... ... @@ -158,7 +158,7 @@
158 158  ** Charge levels for transport will be advised by the freighter. The required SoC will depend on volume and transport method (air, land, sea).
159 159  
160 160  (((
161 -== 7. Data Sharing and Metadata Creation ==
152 +== 6. Data Sharing and Metadata Creation ==
162 162  )))
163 163  
164 164  **GPS Data**:
... ... @@ -173,7 +173,7 @@
173 173  
174 174  * 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.
175 175  
176 -== 8. Additional Best Practices ==
167 +== 7. Additional Best Practices ==
177 177  
178 178  * **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.
179 179  
... ... @@ -443,6 +443,9 @@
443 443  
444 444  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]]
445 445  
437 +(% class="wikigeneratedid" %)
438 +//A small note on the y-axis scale of the following plots: We are aware that raw velocity is typically scaled ~~1e-6. This data has been filtered and selected for especially quiet regions so has lower amplitude. The key point is showing the match with the known CMG-6TD and Centaur data.//
439 +
446 446  == IGU 16HR-3C ==
447 447  
448 448   '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
... ... @@ -450,15 +450,15 @@
450 450   'gain':1,
451 451   'sensitivity': 257019225.55108312}
452 452  
453 -[[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"]]
447 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
454 454  
455 -[[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"]]
449 +[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]]
456 456  
457 457  == IGU 16-1C ==
458 458  
459 459  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.
460 460  
461 -[[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"]]
455 +[[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:IGU16_1C_Z_huddle.png]]
462 462  
463 463  == BD3C-5 ==
464 464  
... ... @@ -474,7 +474,7 @@
474 474  [[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]]
475 475  
476 476  (% class="wikigeneratedid" %)
477 -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:
471 +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). In the next two figures the filter is **0.1** to 5 Hz:
478 478  
479 479  
480 480  [[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
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
1786503344572-296.jpg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -1.4 MB
Content
1786503808210-822.02.28 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -437.8 KB
Content
1786503812585-338.02.28 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -437.8 KB
Content
BD3C_N_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -65.9 KB
1 +72.1 KB
Content
BD3C_N_huddle.0.5.png
Size
... ... @@ -1,1 +1,1 @@
1 -68.4 KB
1 +73.3 KB
Content
BD3C_Z_huddle.0.1.png
Size
... ... @@ -1,1 +1,1 @@
1 -64.3 KB
1 +52.1 KB
Content
BD3C_Z_huddle.0.5.png
Size
... ... @@ -1,1 +1,1 @@
1 -52.5 KB
1 +64.6 KB
Content
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.