EYR data collection needs to be more robust

[tanjapetersen]

• We want to ensure a robust k-index delivery (X & Y fluxgate data needed) to GfZ Potsdam. No "-1" for missing data. Data delivery within 5 days after the 1st and 16th day of each month.

• Auroraalert Otago website uses EYR (X fluxgate only??); www updates every 10 minutes

• EYR is NZ's main INTERMAGNET observatory!! We want to deliver good quality data with ideally no fluxgate data gaps. The F proton data are needed for data quality indication.

• EYR data are used for studies on Geomagnetically Induced Currents (GICs). We don't want any data gaps during geomagnetic storms.

• We want EYR to be attractive for potential future stakeholders/partners: e.g. Transpower, MetService. 1-minute fluxgate data delivered in real-time (within about 1-minute after recording).

[tanjapetersen]

Options/ideas:

Data loggers for the fluxgate: NOTE: Current Q330 only has ~24 hours of storage! More storage is needed and a second datalogger as backup.

• adopt ADvantech embedded PC system the GA geomag team is using
• use GeoNet's Campbell low rate data logger system for our 1 HZ data. Note: GeoNet is not planning to use the low data logger in streaming mode! Also: decision/purchase is still year(s) away.
• purchase a Q330 w/ storage. 3-channels currently ok, but 6-channels better for future; ~$12,000 USD
• buy a Quanterras BALER for Q330 of GeoNet to get extra storage for old Q330

NOTE: DTU (Danemark, Lars Pederson et al) have a circuit board module that allows to attach a second datalogger to the FGE Fluxgate.

[tanjapetersen]

Consider to have spare data logger channels available in case MT group would like to add electrodes to EYR (like GA Australia did as part of the AusLAMP project).

[tanjapetersen]

Minor CAPEX case for purchasing Q330 w/ storage (model S+) was approved 22 Feb 2019.

[tanjapetersen]

Q330+ installed on the 17/04/2019 Closed GeoNet/tickets/issues/4377