SIMPA Annotation

simpa-annotation is an area-based annotation application with 2 design goals:

1. Minimize duplicate annotations that can arise from the time lag between adjacent frames that occur as the ROV 'mows the lawn'.
2. Leverage the VARS annotation database.

Additional Design Goals:

1. Improve navigation by the addition of anchor points
   • Anchor point user-interface

Activity Diagram

Other workflows

Tile load path options

1. Load the tile description file using a script that automates the capture of the framegrabs and uploads them into VARS. The SIMPA annotation UI would then open a completely loaded tile set for the user to annotate.
   • PROS:
     • Easy for the user
     • Loading is encapsulated in a single script
     • Simplifies UI development. There's no image capture involved in the UI
   • CONS:
     • User must run the script that loads the tile info and captures the images
     • Grabbing images from multiple tapes will be a pain.
2. Open a tile description file directly from the UI.
   • PROS:
     • All work is done form a single application. So conceptually simpler for a user; easier to remember what to do.
     • Can either load a file or open an existing Mosaic that's been stored in the VARS database.
     • Image capture is done as needed. It will slow down the annotation flow slightly as the UI seeks the correct timecode and loads the image though.
     • If an image can't be captured from the current video source, a dialog can be displayed to prompt the user to select a different video source and or change the tape.
   • CONS:
     • Need logic for capturing images and controlling the Video Source in the UI
     • How do we upload the captured images from the UI to a directory on a web server? Should we pop up a dialog showing the target directory? The user will need to know the URL used to mount the target directory on a web server.

Processing Activity.png (image/png)