You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There have been a number of observed cases where the loggers fitted to certain boats have given all indications of generating data, but the data, on further examination, contains no valid depths, or positions, or times, or all three. In order to avoid volunteers blithely allowing collection to continue when there is no valid data appearing, it would be very useful if the logger firmware could give some sort of validation of the data streams, and indicate (potentially via the status LED) if there’s a problem (e.g., no depth seen after a given time interval, no valid time data, no valid positions, etc.). The status indication can be an idiot light, but the more information available, the better. Something that provides a warning light plus status on the web server interface might be plausible.
The text was updated successfully, but these errors were encountered:
Original report by Brian Calder (Bitbucket: brian_r_calder, ).
There have been a number of observed cases where the loggers fitted to certain boats have given all indications of generating data, but the data, on further examination, contains no valid depths, or positions, or times, or all three. In order to avoid volunteers blithely allowing collection to continue when there is no valid data appearing, it would be very useful if the logger firmware could give some sort of validation of the data streams, and indicate (potentially via the status LED) if there’s a problem (e.g., no depth seen after a given time interval, no valid time data, no valid positions, etc.). The status indication can be an idiot light, but the more information available, the better. Something that provides a warning light plus status on the web server interface might be plausible.
The text was updated successfully, but these errors were encountered: