Data Post-Processing Tool Requirements

A priori knowledge of the data types and fields in data files not required.

• Implemented in unserialize.cpp and LogEntry::Read, which can read the data and metadata stored in a LRAUV log file.

Provide some basic time correlation functionality

• e.g., through binning
• TextTableLogWriter can provide this in a very basic way – it assumes values stay constant until they are reported as changed.

• Todo:

  Provide more robust Data Post-Processing tool for meeting requirement: Provide some basic time correlation functionality

Provide basic position (lat/lon/depth) correlation functionality

• KmlLogWriter and GPXLogWriter provided such correlations in a very rudimentary way, but only for lat, lon, and depth data.

• Todo:

  Provide more robust Data Post-Processing tool for meeting requirement: Provide basic position (lat/lon/depth) correlation functionality

Allow for renavigation of vehicle data.

• This should be done in a way which is traceable and without modifying original source data.

• Todo:

  Provide Data Post-Processing tool for meeting requirement: Allow for renavigation of vehicle data.

Deal with data files both as a continuous time stream and as a sequence of discrete missions

• Todo:

  Provide Data Post-Processing tool for meeting requirement: Deal with data files both as a continuous time stream and as a sequence of discrete missions

Filter system logs (see \ref req_syslog) on software unit or severity.

• Implemented through SeverityRule