A key component of the vehicle communications scheme is the ability to transmit subsets of mission data back to shore, either for mid-mission quality control or to provide input for mission changes.

A "decimator" software component could fulfill this role by using flexible data parsing "recipes" to sub-select log data and compress the data to minimize packet size.

The decimator could run in two modes: running persistent recipes to make data subsets in realtime, and executing recipes over archived data, for example in anticipation of communications (as the vehicle is surfacing) or on demand from the topside.

Allow selection of pre-defined decimation "recipes".

Not implemented.
Todo:
Implement Allow selection of pre-defined decimation "recipes".

Allow specification of ad-hoc decimation commands

i.e. "now send me temperature data from 8 PM to 10 PM in higher resolution"
Not implemented.
Todo:
Implement Allow specification of ad-hoc decimation commands

Allow for optimization on data packet size, data precision, time resolution

Not implemented.
Todo:
Implement Allow for optimization on data packet size, data precision, time resolution

Include provisions for including or excluding variables.

Not implemented.
Todo:
Implement Include provisions for including or excluding variables.

Allow selection based on time windows

Not implemented.
Todo:
Implement Allow selection based on time windows

Allow selection based on vehicle state changes

e.g. data from the first hour of the mission "Mission1"
Not implemented.
Todo:
Implement Allow selection based on vehicle state changes

Allow selection based on other variables

e.g. data from 20 minutes centered around every time the temperature went about 20deg K)
Not implemented.
Todo:
Implement Allow selection based on other variables