package org.mbari.trex

Mouse Melon logoGet desktop application:
View/edit binary Protocol Buffers messages

message Predicate

trex.proto:3

Used in: SensorMessage

message Predicate.FloatDomain

trex.proto:4

Used in: Variable

message Predicate.Variable

trex.proto:9

Used in: Predicate

message SensorMessage

sensor.proto:5

message SensorMessage.GpsError

sensor.proto:50

Information on position error deduced from a GPS fix This data will be produced when TREX identifies an important "jump" during a gps fix (in the order of tens to hundreds of meters): As this information will come after the samples are propagated the receiver of the message may need to apply this error to previously received samples. The way to apply it is the following for all sample such as gps_fix.from_time <= sample.utime < gps_fix.to_time sample.northing = sample.northing + (sample.utime-gps_fix.from_time)*gps_fix.northing_rate sample.easting = sample.easting + (sample.utime-gps_fix.from_time)*gps_fix.easting_rate end for

Used in: SensorMessage

message SensorMessage.Sample

sensor.proto:18

One data sample Location (northing,easting) is not corrected as it is sampled in real-time. Do also note that we used UTM instead of lat,lon here. This is mostly due to the fact that TREX uses this reference for navigation and his lat,lon information is pretty bad (2 decimal places of accuracy which can result on an error of 100s of m) Note : based on Mike McCann suggestion northing and easting have been made optional as they may be replaced in the future by lat/lon

Used in: SensorMessage