I haven't figured out the best way to go through the status. We have been:
- Watching cockpit (about every hour)
- Scanning WWW plots (not exhaustively)
- Scrolling through QCtables
- Using S+ (on Boulder servers) to look at covars for longer-term trends.
- We do not yet have a way to look at high-rate data in S+ in real-time -- just when data are copied to Boulder via sneakernet.
At the moment, we are only aware of 3 issues:
- Vmote.g dropped quite low last night. This was just after a change of batteries, so we may have a weak battery.
- The TRH "wagon wheels" that have failed had evidence of corrosion. We are about to attempt to coat the back of the Binder connectors on all sensors (prior to the next predicted rain event).
- We have had 2 NIDAS issues that Gordon is working on:
- ntpd started using too much CPU time on A8 last night that blocked all data acquisition
- A few days ago, we had an Emerald interrupt issue that stopped acquisition of the higher serial ports, I believe on A3.