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
As we are 'enhancing' our logs with additional data, the introduction of new data formats is necessary!
Current suggestions for added data in the logs:
remote controlled
water depth
wave information
Two main models can be distinguished here:
time synchronous CSV format; as no sensors will be time-synchronous, this will mean data that has been post-processed on the boat already
time a-syncronouse; every log line starts with a timestamp, then a string indicating the type of data ('RC', 'DEPTH', 'WAVE' etc.), followed by the measurement in a given format
The text was updated successfully, but these errors were encountered:
I was about to write that we should ask previous competitors about the capabilities of their systems to store logs, but I've just changed my mind: the requirements shouldn't need to be fitted to what teams can do.
We might want to explicitly say that it's OK to process logs from your boat into the standard format, so the boat doesn't have to write the standard format directly, in case that's a challenge for anyone. But obviously the processing stage can't generate any new data.
Another question worth asking: Is the binary format still required? It is difficult to give examples for, and not readable without the added big/little endian information. As data storage gets cheaper, I would expect this to be obsolete nowadays.
As we are 'enhancing' our logs with additional data, the introduction of new data formats is necessary!
Current suggestions for added data in the logs:
Two main models can be distinguished here:
The text was updated successfully, but these errors were encountered: