Annotation Comparison Functionality

[BryonLewis]

Capability to load two sets of annotations at the same time and compare them.

• This requires adding a tagging system to annotations so annotations can be tagged as 'ground truth' or other custom tags. Ground truth will be a special tag to make it easier to do comparisons.
• Implement the capability to load two sets of annotations at the same time. This would include the ability to toggle on/off the main annotation and the tagged annotation.
• Need to figure out how to display these two sets of annotations: how the colors are different/modified. How types appear
• Add in some tools for doing comparisons such as visualization of IOU and other options.
• Determine if the Timeline views need to have information regarding the tagged version vs the current version of annotations.

[BryonLewis]

Loading Two Annotation sets simultaneously issues:

• Conflicting Track Ids
  • Track Ids would conflict so they can't be in the same exact list, or at least the secondary tracks need to be renumbered/appended to the system
• Should comparison be in a read-only mode to prevent the complications of editing tracks/annotations?
• I don't have a concept of linking trackIds from a comparison to a ground_truth so I can't properly toggle or connect individual annotations.
• Coloring differences between the two sets of tracks
  • hue/color shift, something like pastel or saturation adjustments?
  • opacity adjustment so types remain similar color by the type color changes
  • Box fill with opacity being set?
  • Symbol/Icon on the Track classification? I.E a * near the name to indicate it is ground_truth/comparison version.
• Is there a new area to turn on/off collections of tracks. I.E above the types area there is a tags section which allows for quick toggling of alternative tracks/tags.

Implementation: Should tracks have a new property called 'tag' associated with them when rendering multiple sets of tracks?

• Then during the loading process we can properly tag the tracks as well as have a way to render and properly display the tag for each track that is displayed.
• So now a track is unique by it's Id+tag. This would require a bunch of changes to make it so references to tracks utilize this new scheme. By default the tag is empty to prevent conflicts from occuring.
• This method then has the benefit of having one singular track list but a way to differentiate how tracks are displayed using the tag property.