Changes for page SmartSolo Node Seismometers

Summary

• Page properties (3 modified, 0 added, 0 removed)
• Attachments (0 modified, 4 added, 0 removed)
  • 1706153266647-145.png
  • 1706153354750-415.png
  • 1706153556166-231.jpeg
  • example_metadata.txt

Details

Page properties

Title

...	...	@@ -1,1 +1,1 @@
1		-SmartSolo Nodes
	1	+SmartSolo Node Seismometers

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.sima
	1	+XWiki.robert

Content

...	...	@@ -2,23 +2,48 @@
2	2	(((
3	3	(% class="col-xs-12 col-sm-8" %)
4	4	(((
5		-= **Node Setup** =
	5	+= **Node Types** =
6	6
7		-Short term (~~30 day) battery powered nodes
	7	+ANSIR carry two types of three-channel nodes
8	8
9		-== **Pre-Fieldwork Preparation** ==
	9	+* **SmartSolo IGU 16HR 3C (5 Hz Short Period)**
	10	+* **SmartSolo BD3C-5 (5 Second Broad-Band)**
10	10
	12	+Both have a battery capacity of around 30 days. The programming, operation, and downloading procedures for both types of SmartSolo nodes are also similar.
	13	+
	14	+
	15	+----
	16	+
	17	+= **Programming Defaults** =
	18	+
	19	+We recommend that the SP 16HR-3C be set to a gain of 24db 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). These are what we use for our internal experiments.
	20	+
	21	+**Note that this gain must be removed when exporting to miniseed, **otherwise amplitudes will be a factor of either 15.84893192 (24db) or 2 (6db) too high. We also recommend disabling bluetooth to increase battery life, and to enable "FIFO" mode just in case old data is still present on the units and you run out of space (although it is unlikely you will go over 64 Gb for one deploy). If using the "timed turn-on" option, please be aware that **the units will not begin recording until they have acquired a GPS lock**, which may nor occur if they are buried too deeply or have very poor sky view.
	22	+
	23	+
	24	+= **Fieldwork Preparation** =
	25	+
11	11	(% class="box infomessage" %)
12	12	(((
13	13	(% class="box warningmessage" %)
14	14	(((
15		-**~ INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING **
	30	+**INVEST IN FAST EXTERNAL HARD DRIVES – DO NOT LET THIS BE THE LIMITATION OF DATA HARVESTING**
	31	+
	32	+**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.**
16	16	)))
17	17	)))
18	18
	36	+== Magnets ==
	37	+
	38	+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).
	39	+
	40	+== Animal-Proofing ==
	41	+
	42	+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.
	43	+
19	19	= **Installation** =
20	20
21		-=== **1- Logbook documentation** ===
	46	+== **1. Logbook documentation** ==
22	22
23	23	(((
24	24	**Essential Details**: Record the following in a logbook:
...	...	@@ -30,20 +30,24 @@
30	30	* Serial number (SN) of the sensor
31	31	* Detailed notes on the site conditions and setup
32	32
33		-
34		-=== **2- Node Placement** ===
	58	+== **2. Node Placement** ==
35	35	)))
36	36
37		-**Protection**: Place nodes inside thick, landfill biodegradable plastic bags for environmental protection.
	61	+**Protection**: Place nodes inside (landfill) biodegradable bags to minimize cleaning and cross-site soil contamination.
38	38
39	39	**Site Analysis**:
40	40
41		-* Conduct compass measurements away from the node and metallic structures, adjusting for inclination angle.
	65	+* **Take compass measurements away from the sensor as it will affect your measurement.**
42	42	* Take multiple photographs from various angles to document the site setup thoroughly.
43	43	* Include a detailed site description in your notes, specifying distances and orientations from nearby landmarks (e.g. Richards garden, Te Mini steam field eastern side)
44	44
45		-=== **3- Visibility and Location Marking** ===
	69	+== **3. GPS Considerations** ==
46	46
	71	+(% class="wikigeneratedid" %)
	72	+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.
	73	+
	74	+== **4. Visibility and Location Marking** ==
	75	+
47	47	**Flag Placement**: Position a flag, preferably in a bright color (avoid green or yellow), near the instrument to aid in its future location.
48	48
49	49	**GPS Marking**:
...	...	@@ -51,218 +51,255 @@
51	51	* Use a GPS device to mark the instrument's exact location.
52	52	* Record this location in both your paper notes and the GPS device.
53	53
54		-=== **4- Data Sharing and Metadata Creation** ===
	83	+== (% style="color:inherit; font-family:inherit; font-size:max(18px, min(20px, 14.4444px + 0.462963vw))" %)**5. Charge Time, Pre-Deployment & Post-Deployment**(%%) ==
55	55
56		-**GPS Data**:
	85	+* **Charging Duration**: Both types of nodes take approximately 6-8 hours to fully charge from a flat state.
	86	+* **Pre-Deployment Charging**:
	87	+** Although the nodes hold their charge well, it's beneficial to give them a "top up" charge before deployment.
57	57
58		-* Download the GPS file to a laptop.
59		-* Share this file on a drive accessible to all team members for uniform understanding of node locations.
	89	+* **Operational Duration**:
	90	+** 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.
60	60
61		-**Photo Sharing**:
	92	+* **Post-Retrieval Charging**:
	93	+** After retrieval, charge the instruments to about 50-60% (indicated as "orange" level) unless they are to be immediately re-deployed.
	94	+* **Storage and Shipping Charge Level**:
	95	+** Maintain a battery charge level of around 50-60% (e.g. "orange") for both storage and shipping purposes.
	96	+** This charge level is recommended to prevent battery damage and is safe for transportation.
	97	+** Nodes should not be stored fully charged, and it **they should especially not be stored with 0 charge.**
62	62
63		-* Upload site photos to a shared platform (OneDrive, Dropbox, etc.).
64		-* Integrating photos into Google Maps or Google Earth can be particularly beneficial for easy location referencing.
	99	+(((
	100	+== **6. Data Sharing and Metadata Creation** ==
	101	+)))
65	65
66		-**Metadata File**:
	103	+**GPS Data**:
67	67
68		-* Create a metadata XML file for each node, which is essential for data organisation and future reference.
	105	+* Ensure you have documented precise lat/lon locations for each station and **DOCUMENTED THIS CAREFULLY**
69	69
70		-=== **5- Additional Best Practices** ===
	107	+**Photo Sharing**:
71	71
72		-* **Environmental Responsibility**: Ensure that the node placement and the materials used are environmentally responsible and adhere to local regulations.
73		-* **Training and Familiarisation**: Make sure all team members are adequately trained in using the GPS devices, compass, and other equipment to ensure consistent and accurate data collection.
	109	+* It is strongly encouraged to take pictures of each site and upload these to a shared platform (OneDrive, Dropbox, etc.).
74	74
75		-= ​​​​​​​ =
	111	+**Metadata File**:
76	76
77		-= =
	113	+* Create and organize metadata according to the [[ANU metadata standard txt file>>attach:example_metadata.txt]].
78	78
79		-= =
	115	+== **7. Additional Best Practices** ==
80	80
81		-= SmartSolo IGU 16HR 3C (5 Hz) Short Period Node =
	117	+* **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.
82	82
83		-blahblah
	119	+----
84	84
85		-== Sub-paragraph ==
	121	+= **Seismic Station Demobilization and Documentation** =
86	86
	123	+1. (((
	124	+**Preparation for Demobilization**:
87	87
88		-== ==
	126	+* Before starting the demobilization process, ensure you have a compass, tape, marker, pen, masking tape, clipboard, logbook, and compass ready in your tote bag.
	127	+)))
	128	+1. (((
	129	+**Locating the instrument**:
89	89
	131	+* Use the downloaded GPS file to accurately locate the node for demobilization.
	132	+* Import this KMZ file onto your phone for easy reference and location tracking.
	133	+* Utilize Google Maps or Google Earth to create a KMZ file of the station’s location.
	134	+)))
	135	+1. (((
	136	+**Labeling Instruments for Demobilization**:
90	90
91		-= Smart Solo BD3C-5 (5 second) Broad-Band Node =
	138	+* Write the station name and the instrument’s serial number on a masking tape label to apply to the top of the node.
	139	+* Add markers 'D' (for download), 'C' (for charge), and ‘R’ (for removal) next to checkboxes on the label.
	140	+* Affix this label to the top of the instrument to avoid confusion during the charging and downloading data.
	141	+)))
	142	+1. (((
	143	+**Photographing the Setup Node**:
92	92
93		-Lorem
	145	+* Take a photo of the entire setup node with the __//label//__ and __//compass visible//__.
	146	+* This photo serves as a final record of the instrument’s condition and orientation at the time of removal.
	147	+)))
	148	+1. (((
	149	+**Logging Demobilization Details**:
94	94
95		-[[image:1705196270090-364.png]]
	151	+* Use the field logbook to note the time of demobilization, serial numbers, and station name.
	152	+* Record any observations or issues related to the instrument’s orientation, level, or any other relevant factors.
	153	+)))
	154	+1. (((
	155	+**Final Checks and Equipment Removal**:
96	96
	157	+* Before physically removing the instrument, double-check that all necessary data has been downloaded and all photos and notes have been taken.
	158	+* Carefully dismantle and pack the equipment, ensuring that all components are accounted for and securely stored for transport.
97	97
98		-== GPS Considerations ==
	160	+
	161	+)))
99	99
100		-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.
	163	+[[image:1706153556166-231.jpeg||data-xwiki-image-style-alignment="center" height="345" width="460"]]
101	101
102		-= Keeping the Instruments Clean =
	165	+----
103	103
104		-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.
	167	+= **Charging Procedure for Seismic Nodes** =
105	105
	169	+(((
	170	+== **1. Preparation for Charging**: ==
106	106
107		-= Charge Time, Instrument Life, and Charge During Storage & Shipping =
	172	+* 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.
	173	+)))
108	108
109		-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.
	175	+(((
	176	+== **2. Disassembling the Node**: ==
110	110
111		-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.
	178	+* For the IGU-16HR, remove the battery (bottom half) from the sensor. This is done by unscrewing the spikes counter-clockwise.
	179	+)))
112	112
	181	+(((
	182	+== **3. Setting Nodes in the Charging Box**: ==
113	113
114		-= Best Practices and Guide =
	184	+* Place 1-16 IGU-16HR battery components upside-down into the charger, assuring they are oriented properly.
	185	+)))
115	115
116		-== Install ==
	187	+(((
	188	+== **4. Monitoring the Charging Process**: ==
117	117
118		-Logbook is required (used again for pick up & metadata creation)
	190	+* 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.
	191	+* 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.
	192	+)))
119	119
120		-- station name
	194	+(((
	195	+== **5. Updating Charge Status**: ==
121	121
122		-- lat / long
	197	+* 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.
	198	+* This step is crucial for tracking the charging status of multiple units, especially when handling a large number of nodes.
	199	+)))
123	123
124		-- team members
	201	+[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center" height="299" width="530"]]
125	125
126		-- date and local time
127	127
128		-- SN of sensor
129	129
130		-- notes on site
131	131
132		-Place nodes in thick (“landfill biodegradable”) plastic bags in the hole
	206	+[[image:1706153354750-415.png||data-xwiki-image-style-alignment="center" height="317" width="562"]]
133	133
134		-Take compass measurement away from node and fences [make sure to adjust inclination angle]
	208	+----
135	135
136		-Take many photos from the site from different angles
	210	+= **Downloading and Converting Seismic Data to MiniSeed Format** =
137	137
138		-Add a precise site description to the notes such as distances and orientations from landmarks
	212	+== **Node Registration and Software Setup** ==
139	139
140		-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.
	214	+1. (((
	215	+**Registering Nodes in the System**:
141	141
142		-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.
	217	+* To begin, register the nodes in the system so the software can recognize them.
	218	+* Navigate to the installation folder of “SmartSoloApps SoloLite”.
	219	+* Right-click on deviceconfig.exe and choose “run as an administrator”. Save the file to the “deviceconfig” directory (refer to the snapshot below).
	220	+* To avoid double registration, replace the file each time you register a new node.
	221	+)))
	222	+1. (((
	223	+**Creating a New Project in SoloLite**:
143	143
144		-Download the GPS (Garmin) file to a laptop and share drive to share with other GPS devices
	225	+* Open the “SoloLite” software.
	226	+* Go to “File” and create a new project. Don't worry about finding the exact 16 nodes used in script writing.
	227	+* Ignore the settings for seismic recordings in the subsequent window. Resetting instruments (e.g., sampling rate, gain) requires reprogramming via script.
	228	+)))
145	145
146		-Share photos in a shared location (Google photos, OneDrive, Dropbox, etc), but most useful are those added to a Google Maps/Earth location
	230	+== **Data Downloading Process** ==
147	147
148		-Create metadata .xml file
	232	+1. (((
	233	+**Initiating Data Download**:
149	149
	235	+* Once a new project is created, the Data Transfer View panel will display connected nodes with details like series number and data size.
	236	+* If “Prospect not matched” appears, it simply means the new project doesn’t match the original programming project. This is not a concern.
	237	+* Select all nodes and right-click to “force download”. This starts the download process.
	238	+* Completed downloads will appear as new folders in the Downloaded Data panel.
	239	+)))
	240	+1. (((
	241	+**Exporting Data in Readable Format**:
150	150
151		-== Removing/Demob ==
	243	+* Go to the “Tool” menu and select “export seismic data”.
	244	+* Tailor other parameters to personal preference and ensure "Sample Interval" matches the setting used during node reset.
	245	+* Click “prepare” followed by “run” to start reformatting. Monitor this process in the small panel at the bottom left.
	246	+* (% class="box warningmessage" %)
	247	+(((
	248	+* **Ensure to export data as "COUNTS", not "mV".**
152	152
153		-Download and then use the GPS file to locate the node
	250	+* **Set "Remove Gain" to the same decibel gain as during programming** **(by default ANU sets this to 24db for short period nodes (a factor of 15.848932), and 6db for broadband nodes).**
	251	+)))
	252	+)))
154	154
155		-Use Google Maps / Google Earth to create a kmz file that can then be imported onto your phone.
	254	+== **Handling Nodes During Download** ==
156	156
	256	+1. (((
	257	+**Monitoring Download Indicators**:
157	157
158		-Upload photos of the site
	259	+* During download, green lights on nodes will blink, and associated red lights on the rack will flash.
	260	+* Disconnect nodes properly before unplugging anything.
	261	+* Be cautious: if the laptop enters sleep mode, the download will pause.
	262	+)))
	263	+1. (((
	264	+//**Investment in Storage Hardware**~://
159	159
160		-- station name
	266	+* (% class="box warningmessage" %)
	267	+(((
	268	+* **Use fast external hard drives to avoid limitations in data harvesting.**
161	161
162		-- latitude
	270	+* **Recommended specifications: USB-C, USB 3.0, and 4+ Tb of space.**
	271	+)))
	272	+)))
	273	+1. (((
	274	+**Metadata and Time Settings**:
163	163
164		-- longitude
	276	+* Ensure all metadata is saved with the file.
	277	+* System auto-determines the earliest data time as the start time. You can set it a day earlier at 00:00:00 for 24-hour data segments starting from midnight.
	278	+)))
	279	+1. (((
	280	+**Finalizing the Download**:
165	165
166		-- elevation
	282	+* After downloading, mark the //"D"// box on your temporary labels to indicate completion.
167	167
168		-* SN of sensor – SN of battery (optional)
169		-* Site notes and name of location (e.g. Richards garden, Te Mini steam field eastern side)
	284	+
	285	+)))
170	170
171		-Upload photos into Google Earth and on a shared drive
	287	+[[image:1706153266647-145.png||data-xwiki-image-style-alignment="center" height="340" width="603"]]
172	172
173		-Before removing the instrument have your compass, tape, marker, pen, clipboard, logbook and compass ready (in tote bag!).
174	174
175		-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.
176	176
177		-Take a photo of the entire setup node with the label on it + compass
	291	+[[Caption>>image:1705195543887-977.png||data-xwiki-image-style-alignment="center" height="534" width="632"]]
178	178
179		-Use existing field logbook to note time, SN and station name plus any notes – including any issues with orientation or level or anything else
180	180
181	181
182		-== Charging ==
183	183
184		-Clean node prior to charging and harvesting the data
	296	+[[Caption>>image:1705195543890-537.png||data-xwiki-image-style-alignment="center" height="397" width="665"]]
185	185
186		-Remove battery (and spike) from the sensor by twisting the spike part of the instrument
187	187
188		-Set 16 nodes into the charging box (spikes up)
189	189
190		-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.
	300	+[[Caption>>image:1705195543891-334.png||data-xwiki-image-style-alignment="center" height="379" width="650"]]
191	191
192		-This is a good time to check the "C" box on your temporary labels to mark that the unit has been charged
193	193
194		-[[IGU 16-HRcharger (left) and harvester (right)>>image:1705195933422-337.png||data-xwiki-image-style-alignment="center"]]
195	195
	304	+[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center" height="467" width="674"]]
196	196
	306	+----
197	197
198		-== Downloading and Converting Data to MiniSeed ==
	308	+= **Cleaning** =
199	199
	310	+**Procedure for Seismic Nodes:**
200	200
201		-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.
	312	+Top half:
202	202
203		-[[image:1705195543887-977.png]]
	314	+Bottom half: The metal spikes on the bottom half of the nodes can be cleaned using a wire brush, though should still be wiped down for dust afterwards.
204	204
205	205
206		-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.
	317	+= **Weights (for shipping)** =
207	207
208		-[[image:1705195543890-537.png||data-xwiki-image-style-alignment="center"]]
	319	+The weights of bags of nodes, as well as data harvesters and node chargers, are listed below:
209	209
	321	+1 bag + 6 SP (IGU-16HR) nodes: 18 kg
210	210
211		-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.
	323	+1 SP (IGU-16HR) data harvester: 21.5 kg
212	212
213		-[[image:1705195543891-334.png||data-xwiki-image-style-alignment="center"]]
	325	+1 SP (IGU-16HR) charger: 26.3 kg
214	214
215		-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.
	327	+1 BB (BD3C-5) charger/data harvester (with and without 16 cables): 21 kg / 14.5 kg
216	216
217		-(% class="box warningmessage" %)
218		-(((
219		-**Please make sure that data is exported as "COUNTS" and NOT "mV"!**
	329	+1 case + 5 BB (BD3C-5) nodes and 6 BB nodes: 22 kg / 25 kg
220	220	)))
221	221
222		-(% class="box warningmessage" %)
223		-(((
224		-**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.**
225		-)))
226		-
227		-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.
228		-
229		-Now the data should be ready. Then you can select these data and right click to output the GPS information associated with them.
230		-
231		-[[image:1705195543898-365.png||data-xwiki-image-style-alignment="center"]]
232		-
233		-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.
234		-
235		-(% class="box infomessage" %)
236		-(((
237		-**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!
238		-)))
239		-
240		-When downloading, ensure that all metadata is saved along with the file.
241		-
242		-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.
243		-
244		-//Once downloaded, mark the "D" box on your temporary labels!//
245		-
246		-== Converting data ==
247		-
248		-Check the data all have been converted to miniseed correctly
249		-
250		-– 3 files per station per day
251		-
252		-* Files are the same size (NOTE if having memory issues one or more of the components may have 0-1 kb)
253		-* ~~ 5 Gb / node / month
254		-
255		-//Tick ‘R’ box on the node label//
256		-
257		-
258		-== Cleaning ==
259		-
260		-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!
261		-
262		-
263		-)))
264		-
265		-
266	266	(% class="col-xs-12 col-sm-4" %)
267	267	(((
268	268	(% class="box" %)
...	...	@@ -269,24 +269,11 @@
269	269	(((
270	270	**Contents**
271	271
272		-(% class="wikitoc" %)
273		-* [[SmartSolo IGU 16HR 3C (5 Hz) Short Period Node>>path:#HSmartSoloIGU16HR3C285Hz29ShortPeriodNode]]
274		-** [[Sub-paragraph>>path:#HSub-paragraph]]
275		-** [[ >>path:#H]]
276		-* [[Smart Solo BD3C-5 (5 second) Broad-Band Node>>path:#HSmartSoloBD3C-5285second29Broad-BandNode]]
277		-** [[GPS Considerations>>path:#HGPSConsiderations]]
278		-* [[Keeping the Instruments Clean>>path:#HKeepingtheInstrumentsClean]]
279		-* [[Charge Time, Instrument Life, and Charge During Storage & Shipping>>path:#HChargeTime2CInstrumentLife2CandChargeDuringStorage26Shipping]]
280		-* [[Best Practices and Guide>>path:#HBestPracticesandGuide]]
281		-** [[Install>>path:#HInstall]]
282		-** [[Removing/Demob>>path:#HRemoving2FDemob]]
283		-** [[Charging>>path:#HCharging]]
284		-** [[Downloading and Converting Data to MiniSeed>>path:#HDownloadingandConvertingDatatoMiniSeed]]
285		-** [[Converting data>>path:#HConvertingdata]]
286		-** [[Cleaning>>path:#HCleaning]]
	338	+{{toc/}}
	339	+
	340	+
287	287	)))
288	288
289		-
290	290	(% class="box" %)
291	291	(((
292	292	= SmartSolo [[BD3C-5>>url:https://smartsolo.com/cp-4.html]] =
...	...	@@ -300,8 +300,12 @@
300	300	|(% style="width:189px" %)**Size (without spike)**|(% style="width:221px" %)158 x160mm
301	301	|(% style="width:189px" %)**Weight**|(% style="width:221px" %)2.8 kg
302	302	|(% style="width:189px" %)**Data Storage**|(% style="width:221px" %)64 Gb
303		-|(% style="width:189px" %)**Battery**|(% style="width:221px" %)Li_etc XXAh
	356	+|(% style="width:189px" %)**Battery**|(% style="width:221px" %)(((
	357	+Lithium-ion battery contained in equipment (168.84 Wh)
	358	+
	359	+UN3481 PI967 S1
304	304	)))
	361	+)))
305	305
306	306	(% class="box" %)
307	307	(((
...	...	@@ -314,10 +314,14 @@
314	314	|(% style="width:187px" %)**Frequency Band**|(% style="width:224px" %)5 Hz to 1652Hz
315	315	|(% style="width:187px" %)**Sensitivity**|(% style="width:224px" %)67.7 V/m/s
316	316	|(% style="width:187px" %)**Size (with spike)**|(% style="width:224px" %)103mm(L) × 95mm(W) × 187mm
317		-|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.3 kg
	374	+|(% style="width:187px" %)**Weight**|(% style="width:224px" %)2.4 kg
318	318	|(% style="width:187px" %)**Data Storage**|(% style="width:224px" %)64 Gb
319		-|(% style="width:187px" %)**Battery**|(% style="width:224px" %)Li_etc XXAh
	376	+|(% style="width:187px" %)**Battery**|(% style="width:224px" %)(((
	377	+Lithium-ion battery contained in equipment (96.48 Wh)
	378	+
	379	+UN3481 PI967 S2
320	320	)))
	381	+)))
321	321
322	322
323	323	)))

1706153266647-145.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.sima

Size

...	...	@@ -1,0 +1,1 @@
	1	+1.7 MB

Content

1706153354750-415.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.sima

Size

...	...	@@ -1,0 +1,1 @@
	1	+2.1 MB

Content

1706153556166-231.jpeg

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.sima

Size

...	...	@@ -1,0 +1,1 @@
	1	+839.4 KB

Content

example_metadata.txt

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.robert

Size

...	...	@@ -1,0 +1,1 @@
	1	+2.7 KB

Content

...	...	@@ -1,0 +1,46 @@
	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!