900731 Data Handling for Eye-in-the-Sea on MARS : VARS-AVED Mapping This page last changed on Apr 30, 2007 by brian. This page lists the different VARS objects and their fields. It attempts to describe the mapping from AVED Event information into VARS annotations. ## VARS Class Diagram This is a simplified diagram showing only the fields and classes important to EITS. More details can be found on Sourceforge ## Mapping of AVED Events to VARS Annotations
| Fields that are listed in BOLD can be determined a priori or from the AVED XML. The other fields will need to be figured out.
### VideoArchiveSet Describes a group of related videos. We use them at MBARI to group tapes by expedition. How will group videos from EITS?
VARS | AVED
--- | ---
TrackingNumber | String YYYYDDD of Recording. This can be parsed from the movie file name which will be YYYYMMDDThhmmss format
ShipName | "MARS"
PlatformName | "EITS"
FormatCode | 'o' or outline mode. Annotators can change this to detailed later
StartDTG | The start time of the recording. This is parsed from the filename
EndDTG | The end time of the recording. Where will we get this?
### CameraPlatformDeployment Some information about the deployment
VARS | AVED
--- | ---
SeqNumber | We use this to store dive-number for ROV's. For EITS, I'm currently using yyyymmdd which relatively closly matches the file names
Chief Scientist | "Edie Widder"
### VideoArchive Describes an individual video source. For EITS this will be a movie file.
VARS | AVED
--- | ---
StartTimeCode | eventDataStream.startTimeCode
videoArchiveName | URL pointing to a QuickTime compatible movie
### VideoFrame Pretty self explanatory.
VARS | AVED
--- | ---
RecordedDTG | Moment in time when the frame was recorded. This is EXTREMELY IMPORTANT; it's how we key into the anxillary data (salinity, temperature, location, etc.). This is calculated by the process, ingest.groovy, that combines the filename (iso8601 date stamp) and TapeTimeCode (which is UTC time of day) NOTE: If the timecode rolls over 23:59:59 we will have roll-over issues since the date is calculated by add the year, month and day of the filename to the timecode (assumed to be UTC time)
TapeTimeCode | As HH:MM:SS:FF. frameEventSet.timeCode
### Observation Records information about 'events' that occurs within a video-frame. There can be multiple observations in a video frame.
VARS | AVED
--- | ---
Observer | "AVED"
ConceptName | "Object"
Notes | ""
### Association Descriptive information associated with an Observation. We need to define what we will store here. We can encode such information as Saliency, ObjectID, BoundingBox information, etc. The usual way of encoding is linkName -> toConcept -> LinkValue. Currently considered associations are: "identity-reference | self | <objectID>" "saliency | self | <saliency>" "start-timecode | self | <frameNumber converted to Timecode (HH:MM:SS:FF)>" ### CameraData Describes information about camera settings.
VARS | AVED
--- | ---
Name | Name of the camera. Will we be able to swap cameras during the deployment? If so , we will want to keep track of which one is out.
Direction | This is set in the annotation application
Zoom | From anxillary data?
Focus | From anxillary data?
Iris | From anxillary data?
FieldWidth | From anxillary data?
StillImageURL | URL to a framecapture of the current Frame
### PhysicalData This table encapsulates all the physical parameters we will receive from EITS. We may need to modify this class and tables specifically for EITS.
VARS | AVED
--- | ---
Depth | From anxillary data?
Temperature | From anxillary data?
Salinity | From anxillary data?
Oxygen | From anxillary data?
Light | From anxillary data?
Latitude | From anxillary data?
Longitude | From anxillary data?
Attachments: VARS-AnnotationModel.png (image/png)

Document generated by Confluence on Feb 03, 2026 14:51