Skip to content

widget: Timeline #2596

@ES-Alexander

Description

@ES-Alexander

Problem to solve

Vehicle operation involves many disparate data forms that can be challenging to reason about without understanding their correlations with each other, particularly since such reasoning is valuable in all of the future, present, and past tenses (through desires/expectations, status tracking, and playback/analysis/reporting).

Desired approach

A time (and/or horizontal distance) -based plot widget, with synchronised data about any/all of mission events (survey start/end points, waypoints, GoTo commands, PoI creation, etc), vehicle events (arm/disarm, mode changes, failsafes, etc), peripheral events (snapshots, start/stop recording of video/sonar, etc), and any other data the user wishes to track (depth + terrain alt, sensor data, text entry submissions, etc). Unlike the existing plotter, the top priority here would be full mission coverage (and additional interaction modes) rather than just high detail insight into the latest section of data.

  • During mission planning it could help visualise mission statistics, and understand relative contributions of different parts
    • It could also be used to select sequential regions of waypoints for configuration
  • During operation it could help show important status information of what is happening and has happened so far, as well as what is expected to happen from here and/or whether things are going to schedule
  • Post operation it could help with analysing what happened, including

I'm imagining a widget that sits just on top of the bottom bar, or just at the bottom of the top bar, with a collapsed mode just showing the different tracks:

Image

and a hover / lockable expanded mode (similar to the existing alerter widget) showing a more detailed view (with hovering/ clicking to preview relevant data):

Image

Additional context

This is vaguely related to #2548, though I'm imagining this more as each event type having its own "track" within the widget, rather than "just" several lines plotted on the same axes.

Given the coverage focus, memory manages may be a concern for long dives, so approaches like the data simplification in #2579 should likely be considered.

Prerequisites

  • I have checked to make sure that a similar request has not already been filed or fixed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    uiUI related issueswidget-specificA widget-specific issue

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions