FAQ

Waypoints on the map¶

There is waypoint information in the ongoing mission but not being displayed. Why?¶

Waypoints in mission scripts are in general only defined for purposes of the internal logic of the mission itself, and not actually designed for easy ingestion outside of the LRAUV framework. (An aspect of this is that the two components of a waypoint, latitude and longitude, are captured separately, with no explicit connection between them.)

However, we have been adding support by considering some variations of the parameter naming to recognize latitude/longitude pairs. The logic and requirements are described in this page.

So, not all missions may be covered. Let us know about the particular mission and corresponding parameters that you think we could incorporate in this handling.

The waypoint trajectory was being displayed but then disappeared even with the mission still ongoing. Why?¶

This has been addressed in Dash 4.7.0. Please let us know if you still notice this issue.

Markers¶

Why are my markers forgotten?¶

As with other various frontend settings, marker definitions are saved in local storage, which is a shared space across any multiple Dash sessions on your browser. So, this effect is very likely caused by having multiple open browser Dash sessions — you define the markers in one session, and some other session overwrites such definitions with whatever marker definitions (or lack thereof) on that other session. A general recommendation is to have only one Dash session active in your browser.

Log tab¶

My browser's 'Find' feature seems of little use in the log table. Why?¶

The regular browser 'Find' is rather limited here mainly due to the underlying mechanism in the Dash to display the log table contents.(*) However, there's a string filter in the Dash itself, which, although not exactly behaving like a typical find or search, allows to quickly select only the lines containing the given string. Please let us know of any suggestions to improve the search and navigation capabilities.

(*) In short, this mechanism (which allows for efficient display and navigation even when dealing with tens of thousands of events) only puts a small section of the loaded events in the displayed table. So, the browser's Find feature will only "see" the currently displayed section at a given time.

Sat Comms Vehicle Acks aren't showing up when just Sat Comms events are selected. Why?¶

This is a known limitation mainly arising from a major renaming/categorization of event kinds a couple of years ago, but not with all necessary support from the backend database.

In this case, sbdReceive is the common event type that gets reflected as just Sat comms or as Received (Vehicle ACK) (among other possibilities) depending on other attributes in the event. The associated filtering logic is not yet fully correct in these cases.

Workaround: You can select all event types and then use the filter field. (Not ideal, but hopefully helpful enough for the time being.)

UI¶

Some documents don't look well in dark mode. Why?¶

Depending on color attributes possibly already incorporated in a document, the rendering of such document in dark mode may not be as readable. This known issue seems exacerbated in some particular browsers (e.g., Safari). We will try to improve this rendering in a future version. In the meantime, you can try using a different browser or switch to light mode in those cases.

User account¶

How can I change my password?¶

On a wide screen:
On a small screen:

How can I create an account?¶

Visit https://okeanids.mbari.org/dash4/, click "Sign in," then click "Create account," then complete and submit the form. More details, here.