Skip to Content
Last modified by robert on 2026/06/29 16:42
From version 110.2
edited by Jack Dent
on 2026/06/15 09:47
Change comment: (Autosaved)
To version 90.1
edited by KB
on 2025/12/04 12:31
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.JackD
1 +XWiki.KB
Content
... ... @@ -6,17 +6,15 @@
6 6  
7 7  ANSIR supply two types of three-channel nodes, and one type of one-channel node:
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 +* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
10 +* **SmartSolo BD3C-5 (5 Second Broadband)**
11 +* **SmartSolo IGU 16 1C (5 Hz Short Period, single channel)**
12 12  
13 -Visit the [[SmartSolo page>>https://smartsolo.com/igu.html]] for more detail.
13 +The three-channel nodes have a 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.
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.
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.
17 +**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 feasibility for 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 20  )))
21 21  
22 22  ----
... ... @@ -23,13 +23,12 @@
23 23  
24 24  = **Programming Defaults** =
25 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.
24 +The nodes must be programmed in the SoloLite software prior to use. Screenshots for the short period 16HR-3C and broadband BDC3-5 are shown with our recommended parameters.
27 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"]]
26 +[[IGU-16 3C (short period node) programming screen set at 250 Hz. Ensure that the highlighted areas are set!>>image:SP_programming.labels.png||alt="IGU-16 3C programming screen"]]
29 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!"]]
28 +[[BD3C-5 (broadband node) programming screen set at 250 hz. Ensure that the highlighted areas are set!>>image:BB_programming.labels.png||alt="BD3C-5 programming screen"]]
31 31  
32 -
33 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 34  
35 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.
... ... @@ -44,9 +44,9 @@
44 44  
45 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 46  
47 -Bluetooth (BD3C-5 only) should be turned OFF to conserve power.
44 +Bluetooth (BB nodes only) should be turned OFF to conserve power.
48 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).
46 +We recommend that the SP 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 50  
51 51  {{info}}
52 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!
... ... @@ -69,10 +69,8 @@
69 69  
70 70  == Animal-Proofing ==
71 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.
69 +We have experienced times where foxes (or some other animal) will dig up nodes and potentially carry them off for tens or hundreds of meteres. Being sanitary with the rope handles (e.g. not getting food grease on them) seems to help, as well as spraying the nodes and handles with methylated spirits et al. when deploying. There are other specialized products available depending on your environment.
73 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 78  (% class="box infomessage" %)
... ... @@ -97,6 +97,8 @@
97 97  == 2. Node Placement ==
98 98  )))
99 99  
95 +**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
96 +
100 100  **Site Analysis**:
101 101  
102 102  * **Take compass measurements away from the sensor as it will affect your measurement.**
... ... @@ -127,14 +127,11 @@
127 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.
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).
127 +** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
128 +* **Storage and Shipping Charge Level**:
129 +** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
130 +** This charge level is recommended to prevent battery damage and is safe for transportation.
131 +** Nodes should not be stored fully charged, and **they should especially not be stored with 0 charge as this damages lithium batteries.**
138 138  
139 139  (((
140 140  == 6. Data Sharing and Metadata Creation ==
... ... @@ -142,7 +142,7 @@
142 142  
143 143  **GPS Data**:
144 144  
145 -* Ensure you have __carefully documented__ precise lat/lon locations for each station.
139 +* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
146 146  
147 147  **Photo Sharing**:
148 148  
... ... @@ -215,22 +215,20 @@
215 215  (((
216 216  == 2. Disassembling the Node: ==
217 217  
218 -* For the IGU-16HR, remove the battery section (bottom half) from the sensor by unscrewing the spike section counter-clockwise.
212 +* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
219 219  )))
220 220  
221 221  (((
222 222  == 3. Setting Nodes in the Charging Box: ==
223 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.
218 +* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
227 227  )))
228 228  
229 229  (((
230 230  == 4. Monitoring the Charging Process: ==
231 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.
224 +* Once the nodes are set in the charging box and the charging process begins, lights adjacent to the batteries will illuminate. These lights indicate that charging is underway.
225 +* 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. For storage, the goal is to charge them to ORANGE.
234 234  )))
235 235  
236 236  (((
... ... @@ -312,7 +312,7 @@
312 312  
313 313  * Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
314 314  * If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
315 -* Select all nodes and right-click to “force download”. This starts the download process.[[image:Smartsolo harvesting #4 copy.png]]
307 +* Select all nodes and right-click to “force download”. This starts the download process.
316 316  * Completed downloads will appear as new folders in the Downloaded Data panel.
317 317  )))
318 318  1. (((
... ... @@ -319,27 +319,23 @@
319 319  **Exporting Data in Readable Format**:
320 320  
321 321  * Go to the “Tool” menu and select “export seismic data”.
322 -* Tailor other parameters to project preference and ensure "Sample Interval" matches the setting used during node reset.
323 -* **Ensure export data is set to "COUNTS" (int32), not "mV" (float). This is critical!**
324 -* 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.
325 -Set 'Remove DC' to 'Yes' to centre the data around the zero value
326 -Set the correct Start Time (UTC) and End Time (UTC) of the project to prevent the unnecessary export of older data
327 -* [[image:Smartsolo harvesting #9 copy.png]]
314 +* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
315 +* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
328 328  * (% class="box warningmessage" %)
329 329  (((
330 -
331 -)))Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
318 +* **Ensure to export data as "COUNTS" (int32), not "mV" (float). This is critical!**
319 +
320 +* **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.**
332 332  )))
322 +)))
333 333  
334 -== Smart Solo IGU-16HR Polarity Notice ==
324 +== Smart Solo Z Polarity bug (SP nodes ONLY!) ==
335 335  
336 -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.
326 +See [[https:~~/~~/auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodeZPolaritybug>>https://auspass.edu.au/xwiki/bin/view/Data/AusPass%20Data/#HSmartSoloNodeZPolaritybug]] for discussion. If data is headed to AusPass, we prefer to invert the IGU-16HR 3 Z channel data manually rather than in the SoloLite software or inverting the response metadata. **The BD3C-5 data does not require a polarity inversion.**
337 337  
338 -**The BD3C-5 data does not require any sort of polarity inversion.**
339 -
340 340  == 18 Leap Second bug ==
341 341  
342 -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.
330 +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 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.
343 343  
344 344  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.
345 345  
... ... @@ -395,8 +395,11 @@
395 395  **Finalizing the Download**:
396 396  
397 397  * After downloading, mark the //"D"// box on your temporary labels to indicate completion.
386 +
387 +
398 398  )))
399 399  
390 +[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
400 400  
401 401  
402 402  
... ... @@ -417,78 +417,23 @@
417 417  
418 418  ----
419 419  
420 -= Instrument Response =
421 -
422 -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]]
423 -
424 -== IGU 16HR-3C ==
425 -
426 - '16HR3C': {'poles':[(-22.211059+22.217768j), (-22.211059-22.217768j)],
427 - 'zeros':[0j, 0j],
428 - 'gain':1,
429 - 'sensitivity': 257019225.55108312}
430 -
431 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:IGU16_Z_huddle.png]]
432 -
433 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz bandpass filter>>image:IGU16_N_huddle.png]]
434 -
435 -== IGU 16-1C ==
436 -
437 -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.
438 -
439 -[[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]]
440 -
441 -== BD3C-5 ==
442 -
443 - 'BD3C': {'poles':[(-1720.4+0j), (-1.2+0.9j), (-1.2-0.9j)],
444 - 'zeros':[(14164+0j), (-7162+0j), 0j, 0j],
445 - 'gain':1.69726e-05,
446 - 'sensitivity': 702651512.6046528}
447 -
448 -Above 0.5 Hz, the BD3C-5 response fits well:
449 -
450 -[[X axis is samples (.01 s), Y axis is velocity (m/s), 0.5-5 Hz filter>>image:BD3C_Z_huddle.0.5.png]]
451 -
452 -[[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]]
453 -
454 -(% class="wikigeneratedid" %)
455 -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:
456 -
457 -
458 -[[BD3C **0.1 **to 5 Hz bandpass filter>>image:BD3C_Z_huddle.0.1.png]]
459 -
460 -[[BD3C **0.1** to 5 Hz bandpass filter>>image:BD3C_N_huddle.0.1.png]]
461 -
462 -== IGU-16 Horizontal noise & how to avoid ==
463 -
464 -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.
465 -
466 -[[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]]
467 -
468 -(% class="wikigeneratedid" %)
469 -The BD3C-5 nodes do not have this issue:
470 -
471 -[[BD3C-5 test, as above. There is no additional noise on the horizontal channels.>>image:BD3C_psd.png]]
472 -
473 473  = **Cleaning** =
474 474  
475 -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.
413 +When still connected, the nodes are water resistant (don't submerge them!) and can handle a good spray / wipe-down. A strong, non-wire brush is helpful to reach areas between the metal spikes on the bottom.
476 476  
477 477  = **Weights (for shipping)** =
478 478  
479 479  The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
480 480  
481 -1 bag + 6*IGU-16HR nodes: 18 kg
419 +1 bag + 6 SP (IGU-16HR) nodes: 18 kg
482 482  
483 -1*IGU-16HR data harvester: 21.5 kg
421 +1 SP (IGU-16HR) data harvester: 21.5 kg
484 484  
485 -1*IGU-16HR charger: 26.3 kg
423 +1 SP (IGU-16HR) charger: 26.3 kg
486 486  
487 -1*BD3C-5 charger (with and without 16 cables): 21 kg / 14.5 kg
425 +1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
488 488  
489 -1 case + 5*BD3C-5 nodes: 22 kg (aggregate battery weight <5kg, 168Wh)
490 -
491 -1 case + 6*BD3C-5 nodes: 25 kg (aggregate battery weight >5kg, 168Wh)
427 +1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
492 492  )))
493 493  
494 494  (% class="col-xs-12 col-sm-4" %)
... ... @@ -572,8 +572,8 @@
572 572  |**Dimensions (LxHxW)**|558 x 357 x 300mm
573 573  |**Input rating**|100-210V - 50/60Hz
574 574  |**Power**|1000W
575 -|**Weight**|14.5 kg
576 -|**Weight with cables**|21 kg
511 +|**Weight**|14.5kg
512 +|**Weight with cables**|21kg
577 577  )))
578 578  
579 579  (% class="box" id="HSmartSoloBD3C-16PortableBatteryCharger" %)
... ... @@ -585,8 +585,8 @@
585 585  |**Dimensions (LxHxW)**|625 x 500 x 366mm
586 586  |**Input rating**|100-210V - 50/60Hz
587 587  |**Power**|100W
588 -|**Weight**|21.5 - 24 kg
589 -|**Capacity**|16 nodes
524 +|**Weight**|21.5 - 24kg
525 +|**Slots no.**|16
590 590  |**Download Speed**|20MB/sec/slot
591 591  )))
592 592  
... ... @@ -596,11 +596,11 @@
596 596  
597 597  [[image:20250729_124644.jpg]]
598 598  
599 -|**Dimensions (LxHxW)**|625 x 500 x 366 mm
600 -|**Input rating**|100-210V - 50/60 Hz
601 -|**Power**|640 W
602 -|**Weight**|26.3 kg
603 -|**Capacity**|16 nodes
535 +|**Dimensions (LxHxW)**|625 x 500 x 366mm
536 +|**Input rating**|100-210V - 50/60Hz
537 +|**Power**|640W
538 +|**Weight**|26.3kg
539 +|**Slots no.**|16
604 604  )))
605 605  
606 606  (% class="box" %)
... ... @@ -610,9 +610,9 @@
610 610  [[image:20250729_124957.jpg]]
611 611  
612 612  
613 -|**Dimensions (LxHxW)**|590 x 225 x 405 mm
614 -|**Weight**|8.2 kg
615 -|**Capacity**|6 nodes
549 +|**Dimensions (LxHxW)**|590 x 225 x 405mm
550 +|**Weight**|8.2kg
551 +|**Slots no.**|6
616 616  )))
617 617  
618 618  (% class="box" %)
... ... @@ -622,13 +622,9 @@
622 622  [[image:20250729_124502.jpg]]
623 623  
624 624  |**Dimensions (LxHxW)**|230 x 340 x 310mm
625 -|**Weight**|(((
626 -3.6kg (empty)
627 -
628 -18.0kg (full)
561 +|**Weight**|3.6kg
562 +|**Slots no.**|6
629 629  )))
630 -|**Capacity**|6 nodes
631 -)))
632 632  
633 633  (% class="box" %)
634 634  (((
... ... @@ -638,7 +638,7 @@
638 638  
639 639  |**Dimensions (LxHxW)**|225 x 200 x 550mm
640 640  |**Weight**|
641 -|**Capacity**|8 nodes
573 +|**Slots no.**|6
642 642  )))
643 643  )))
644 644  )))
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
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.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -73.3 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.0.5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.robert
Size
... ... @@ -1,1 +1,0 @@
1 -64.6 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
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 #9 copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.JackD
Size
... ... @@ -1,1 +1,0 @@
1 -28.7 KB
Content