Changes for page SmartSolo Node Seismometers
Last modified by robert on 2026/08/12 13:08
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (4 modified, 6 added, 0 removed)
-
Objects (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -106,7 +106,15 @@ 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. Node Placement == 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. //Don't be lazy. Do it right. // 112 + 113 +[[An example of what not to do.>>image:1786503344572-296.jpg||data-xwiki-image-style-alignment="center" height="341" width="404"]] 114 + 115 +[[North channel PSD of the sensor in the picture above (not good)>>image:1786503812585-338.02.28 PM.png||data-xwiki-image-style-alignment="center" height="244" width="451"]] 116 + 117 +== 3. Node Placement == 110 110 ))) 111 111 112 112 **Site Analysis**: ... ... @@ -115,12 +115,12 @@ 115 115 * Take photographs from various angles to document the site setup thoroughly. Have a colleague stand next to it pointing at it. 116 116 * Include a detailed site description in your notes. 117 117 118 -== 3. GPS Considerations ==126 +== 4. GPS Considerations == 119 119 120 120 (% class="wikigeneratedid" %) 121 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 122 123 -== 4. Visibility and Location Marking ==131 +== 5. Visibility and Location Marking == 124 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 ... ... @@ -129,12 +129,11 @@ 129 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 130 * Also write the GPS down on paper (ie your [[LOG SHEET>>http://auspass.edu.au/field/NODES_blank_fieldlog.pdf]]). 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(%%) ==140 +== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)6. Charge Time, Pre-Deployment & Post-Deployment(%%) == 133 133 134 134 * **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state. 135 135 * **Pre-Deployment Charging**: 136 136 ** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment. 137 - 138 138 * **Operational Duration**: 139 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 140 ... ... @@ -149,7 +149,7 @@ 149 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 150 151 151 ((( 152 -== 6. Data Sharing and Metadata Creation ==159 +== 7. Data Sharing and Metadata Creation == 153 153 ))) 154 154 155 155 **GPS Data**: ... ... @@ -164,7 +164,7 @@ 164 164 165 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. 166 166 167 -== 7. Additional Best Practices ==174 +== 8. Additional Best Practices == 168 168 169 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. 170 170 ... ... @@ -441,15 +441,15 @@ 441 441 'gain':1, 442 442 'sensitivity': 257019225.55108312} 443 443 444 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]] 451 +[[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"]] 445 445 446 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]] 453 +[[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"]] 447 447 448 448 == IGU 16-1C == 449 449 450 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. 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:IGU16_1C_Z_huddle.png]] 459 +[[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"]] 453 453 454 454 == BD3C-5 == 455 455 ... ... @@ -465,7 +465,7 @@ 465 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 466 467 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). In the next two figures the filter is **0.1** to 5 Hz: 475 +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 469 470 470 471 471 [[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
- BD3C_N_huddle.0.1.png
-
- Size
-
... ... @@ -1,1 +1,1 @@ 1 - 72.1KB1 +65.9 KB - Content
- BD3C_N_huddle.0.5.png
-
- Size
-
... ... @@ -1,1 +1,1 @@ 1 - 73.3KB1 +68.4 KB - Content
- BD3C_Z_huddle.0.1.png
-
- Size
-
... ... @@ -1,1 +1,1 @@ 1 - 52.1KB1 +64.3 KB - Content
- BD3C_Z_huddle.0.5.png
-
- Size
-
... ... @@ -1,1 +1,1 @@ 1 - 64.6KB1 +52.5 KB - Content
- 16HR1C_Z_huddle.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.robert - Size
-
... ... @@ -1,0 +1,1 @@ 1 +92.1 KB - Content
- 16HR_N_huddle.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.robert - Size
-
... ... @@ -1,0 +1,1 @@ 1 +88.4 KB - Content
- 16HR_Z_huddle.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.robert - Size
-
... ... @@ -1,0 +1,1 @@ 1 +80.8 KB - Content
- 1786503344572-296.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.robert - Size
-
... ... @@ -1,0 +1,1 @@ 1 +1.4 MB - Content
- 1786503808210-822.02.28 PM.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.robert - Size
-
... ... @@ -1,0 +1,1 @@ 1 +437.8 KB - Content
- 1786503812585-338.02.28 PM.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.robert - Size
-
... ... @@ -1,0 +1,1 @@ 1 +437.8 KB - Content
- XWiki.XWikiComments[0]
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +Mark Goldman - Comment
-
... ... @@ -1,0 +1,1 @@ 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. - Date
-
... ... @@ -1,0 +1,1 @@ 1 +2026-07-09 10:45:51.967