Noteworthy frontend changes¶
The backend change log is here.
- Only internal changes.
- Fixes related to the display of waypoints for TethysL missions. (As with XML, such display is only available for missions with recognized lat/lon parameters).
- The account button now includes the name of the user (in an abbreviated form).
- Better alignment with the ODSS in terms of coloring of LRAUV positions on the map.
- Internal: removal of long unneeded "pusher" dependency, both from frontend and backend (also, lots of cleanup in the latter). Our direct websockets based mechanism has proved reliable for a good while already.
- With a fix in the backend, the system now properly handles the desired maximum number of positions to display on the map. (Thanks, Brett, for the report).
- Adjustments in underlying asynchronous message handling.
- A popup notification should now get displayed upon expiration of the session as reported from the backend server. The user will be advised to sign in again.
New Status button in the map area to display the LRAUV and ESP status widgets (if available) for the selected vehicles. The expanded area allows for various sizes and can be "pinned" (so it auto-reopens next time the Map tab is selected).
Improved visualization of the various positions on the map: hovering your mouse under the "Layers" dropdown now triggers a corresponding highlight on the map for entries that were not considered before, including GPS fixes, waypoints, reached waypoints, emergency positions, Argos positions, and tracking DB assets:
- Circles and connecting lines are drawn for these specific entries, as well as a label for each point indicating corresponding lat/lon.
- For grouping nodes (e.g., a specific LRAUV like "brizo", or the "LRAUVs" root), only circles are drawn (for all associated points).
Fixed a regression where the waypoint layer was not auto-refreshing when adding/removing an LRAUV.
4.10.4 / 4.10.3 (2022-05-24)
- The vehicle/tab selection is now retained when the user signs in. Thanks for the suggestion, Monique.
- Fixed a bug that prevented the pre-selection of some layers (GPS fixes, waypoints, reached waypoints, emergency locations) from being displayed on the map upon the addition of an LRAUV. This was a regression arising from the recent added feature of saving the layer selection in local storage. (Thanks for reporting, Monique, Brent, Steve.)
Improvements under Map > Layers, including:
New ability to save a marker as a station: use the new button for this in the marker popup.
The station will be overwritten if already existing. Note that the marker itself will still remain as such upon saving the location as a station. You can then remove it if you'd like.
Section renamed to "My markers" to emphasize they are only stored locally.
- Latitude/longitude info is included again in the tooltip for stations.
- Other adjustments/fixes.
4.10.1 / 4.10.0 (2022-05-10)
- Under the "Layers" dropdown in the Map tab, this version brings enhancements related with the definition of stations, and a new similar handling for polygons:
- The layer selection is now saved in the local storage of your browser.
- Adjustments in backend and docker-based release.
- Adjustments in backend and docker-based release.
4.9.6 is a proper release after satisfactory operations with the 4.9.6pre1 prerelease. The key enhancement in this version is that operators can now schedule mission scripts that have been written in TethysL. From the Dash user perspective, the handling of such missions is done exactly as with the usual XML scripts.
👉 More details here.
A link to mission documentation is now included in the Mission tab.
The frontend settings related with the "Current Position Point Cloud" have been moved to the Map section in the dialog (from the Experimental section).
- Preparations for allowing operators to schedule mission scripts that have been written in TethysL.
- Maintenance release.
- Layout adjustments in the email notification settings dialog.
- Debug options to facilitate diagnosing issue with unreported events from the backend depending on selection of event types.
- Fixed elapsed times in the async subscriber dialog during playback mode.
- (Internal) Upgraded underlying framework.
- (Backend) Fixed regression in email notification handling. (Thanks, Brian, for the report.)
- Dash logging enhancements.
4.9.3 / 4.9.2 (2022-01-31)
- Adjustment is scale control.
- Validation of regular expression in the email notification settings.
- The waypoint popup on the map (displayed when clicking one of the planned trajectory lines) now uses a scroll area to avoid the popup to get too tall when there are many waypoints to list.
A scale control added to the map.
Under testing: In the email notification settings, for every notification line where the text filter is used, operators can now indicate the type of filtering to be applied, with three options:
L: Literal, meaning the usual simple substring check
G: Glob filtering
R: Regex filtering
Various minor style adjustments in the frontend, including:
- more prominent display of
Default mission has been running for ...events
- adjustment in the "Async users/sessions" dialog pagination
- more prominent display of
NOTE: More significant changes are in the backend component, regarding the removal of the legacy TethysDash UI, see here.
Note: The legacy TethysDash UI will be shut down on January 21, 2022
Dec 17, 2021: On Oct 19, 2021, we announced a plan to decommission the legacy TethysDash UI in early 2022. The prompt feedback received (thanks again!), has allowed us not only fix some behaviors but also enhance Dash4 in general. These various improvements have already been tested and well received, and we have now determined a concrete shutdown date as indicated above.
- Backend fix in the logic that handles incoming SBD emails.
Many thanks Ryan G. (WHOI) for your valuable input and testing!
- Other adjustments in the backend (in preparation for legacy UI removal).
4.8.93 - 4.8.92 (2022-01-14)
Backend fix in the logic that gathers the waypoint information that then gets displayed on the map upon the
New generation of grid mapping waypoints (#96).
See Waypoint Generation.
- Adjustments/fixes and more documentation to recently added features.
New features under testing. These can be enabled in the General section of the Frontend Settings:
[ ]Auto reload my last vehicle selection when opening Dash
[ ]Include advanced modes for event filtering.
See Advanced filtering.
(Thanks, Mike G., for the suggestions.)
Font size adjustments to address display issues that occur in some Windows/Chrome environments. Thanks, Yanwu, for the heads-up and testing.
Improved refresh handling in vehicle selection dropdown: This refresh now reflects changes in the available list of vehicles according to the branch that is currently checked out in the lrauv-config repository clone maintained by the backend.
- Critical security dependency update applied in the backend.
Deployment report page now with a
Download as...button to download the generated report in one of the following format options: plain text, HTML, markdown.
- WIP: New handling of Argos battery low flag indication.
Improvements in the functionality related with the Map tab:
- Now used is a new backend mechanism that should make the display of vehicle positions more reliable in general.
- In case of any
emergencyevents, these will now be included on the map.
- The "Map" section in the Frontend Settings now includes a 'Maximum time in hours to show positions' parameter, which will be applied along with the usual 'Maximum number of GPS positions to display per vehicle' parameter for actual display of the positions on the map.
- Although all relevant asynchronous events are handled to keep the map up-to-date, there's now also a refresh button to facilitate explicit updates.
Various backend and frontend components were updated as part of the above, so your feedback would be especially welcome here.
4.8.0 / 4.7.9 (2021-11-09)
Adjustments in deployment and git tag listings:
- Bug fix: Under the Deployment tab, no more filtering out of any non-standard tag names
when listing deployments. This was inconsistent with the inclusion of such tags in the
selection dropdown when initially starting a deployment.
(Thanks, Mike G., for the heads-up.)
- Along with the above, some related improvements:
- The git tag selection dropdown is now sorted by tag date, not by tag name (this mainly because not all tags may follow the "standard" naming convention YYYY-MM-DD).
- As operators are typically only interested in a few of the most recent tags, now a maximum number of tags is displayed in the dropdown, by default 30, but the parameter can be adjusted as desired under the Query section in the Frontend settings.
- Bug fix: Under the Deployment tab, no more filtering out of any non-standard tag names when listing deployments. This was inconsistent with the inclusion of such tags in the selection dropdown when initially starting a deployment.
Adjustment in the handling of received asynchronous events to better align with the recent event type selection dispatch overhaul: filtering by the selected event types is also applied in this case.
- Adjustments toward more robust handling of interactions with backend.
- A fix in underlying query related with
Sat Comms Receivedevents. The specific symptom was not getting such events back when they should. (Thanks, Brian, for the heads-up.)
- Internal: new database index to improve performance of certain event type queries.
- Internal: logging adjustments.
- Adjustment in mission selection menu.
- A popup is now used to show details about async sessions.
- More adjustments in the Log tab to closely align with legacy UI in terms of the event type selection dispatch logic. Please see the Log Tab section for details.
- A fix in the "Load more events" functionality:
The event type selection is now used to build the corresponding query to the backend.
Previously, such query was done with default event types
(basically, all except
dataProcessed), while the subsequent filtering, according to the event selection, was completely done in the frontend. (Thanks, Brian and Brett, for the heads-up).
Reprocess/Replot options (only for admins) have been added to the Data tab, with same functionality as in the legacy UI. (Thanks, Ben, for the heads-up).
Deployment playback enhancements.
- Deployment report adjustments.
- Internal adjustments per enhanced backend APIs.
Gathering the waypoint information associated to the last started mission is now done in (and exposed by the API of) the backend. With no more dependency on the query parameters in the frontend settings, this should fix the occasional issue of such waypoints not showing on the map when they should be.*
* This FAQ entry is still relevant.
4.6.9 (2021-10-07) (With a hotfix in the UI wrt 4.6.8)
- Reflect adjustment in the LRAUV codebase, which now generates
Command.xmlas the command XML file (previously
- As part of this, note that
CommandExecis now the component name in some events reported from the vehicle (previously,
- Various important underlying dependencies updated, including LRAUV and Tomcat.
- Reflect adjustment in the LRAUV codebase, which now generates
- Fixed issue that prevented the refresh button under the "Build a command" dropdown from working;
- A bit more prominent display of the "Started mission <id>" important event in the Log table.
- More adjustments required in the backend arising from the recent new handling involving the
"sender" email address, initially implemented to circumvent restriction by tmobile
in notifications from
- Associated with the address for outbound emails, new
replyToconfiguration setting, which allows to indicate the primary address that is regularly monitored.
- However, it turns out, the
replyTomechanism is not honored by some external carriers, so, TethysDash now also checks the inbox for the address used for outbound, but in this case only for "request-by-operator" purposes (e.g., a 'note' reply via text to an event notification email).
- New configuration setting to explicitly indicate the sender for Iridium purposes.
- Associated with the address for outbound emails, new
- MBARI instance: For event notifications and other emails from the system,
the sender is now
The "extra" email addresses (used for event notifications purposes) can now be edited and also deleted. When an extra email address is edited, all associated notification settings are transferred to the new address.
Once an extra email address is selected in the notification settings dialog, use the indicated button to edit or delete it:
The map includes two additional base layers for selection: a dark layer (CARTO/OpenStreetMap), and an "empty" layer (i.e., no base layer).
- Adjustments in backend logic to reply to text message in case of error in the request. (Thanks, Pat, for the heads-up.)
- As a shortcut, new button in main page to switch light and dark modes. The button is located next to the 3-dot main menu (only for widescreen).
Various color adjustments for dark mode, including some for small screens. Thanks for the feedback!
Dark mode adjustments also include some under the Docs tab.
Depending on color attributes possibly already incorporated in a document, the rendering of such document in dark mode may not be as readable. You can switch to light mode in those cases.
Dark mode has arrived!
The default mode ('Auto') should reflect the "theme" preference in your browser. However, you can explicitly set the mode in the Frontend Settings:
It is possible that not all associated coloring has been adjusted for dark mode in this first version, not to mention that the color selection itself is open to suggestions. As always, your feedback is welcome.
MTMSM numbers are now highlighted for certain events in the Log table. This is done for the event types that explicitly capture such piece of information:
sbdReceive. Also highlighted are
MTMSN=in the description (e.g.,
- (Experimental) Operators can now post notes via text messages.
More details in this page. Thanks, Monique, for the suggestion. (td#85)
- New "admin" option to remove events timestamped in the future (for the 'sim' vehicle).
- Data file access has been enabled in the backend, so a file like
- Other changes in the backend, mainly associated with the service ("odss2dash") that relays platform positions from the Tracking DB, eventually exposed to the Dash UI via websockets.
Enhancements in the 'Recent Runs' dropdown under the Mission tab:
- Initial number of loaded 'Mission Request' events has been increased.
- One can now also click a 'Load more' button to load more in increments of 50.
- So, along with the filter one can now really search for pretty much any issued mission while going back in time as much as needed.
- Other associated improvements:
- Event timestamp is now also included in the dropdown list
- The filter is now also applied to the note and timestamp
Ability to indicate specific list of vehicles to be exposed.
Default map location is no longer hard-coded to Monterey Bay; instead, the whole world gets displayed by default. One can then just click one of the relevant buttons, e.g., "Zoom to all", to restrict the area to actual vehicle positions, or use any other mechanism to change the location and zoom level. Subsequently, as usual, the last selected area and zoom level will continue to be "remembered" in your browser's local storage.
Fixed issue about wrong waypoint extraction recently exposed with
front_tracking_2Dfor WHOI. (As is the case with several other missions,
front_tracking_2Dis not to be considered for waypoint display given the general limited support for this.)
Adjusted width of waypoint trajectory details dialog so one doesn't have to do scrolling when on a wide screen.
Various adjustments related with vehicle selection, including automatic selection when only one vehicle is available from configuration (which is the current WHOI case).
A fix in the websockets endpoint setting when running dockerized system locally.
- Internal adjustments and code cleanup.
Fixed issue that prevented the addition of email address for event notification purposes.
For operators, the dash can now play a quick sound as soon as cell connection to a vehicle is reestablished. Use the cell connection status dialog to enable this feature:
Important improvement in the 'reset password' workflow, now more secure and standard: instead of an immediate effect, the request now generates an email with a special, account-specific link to a form where the user can then enter the new password.
Further adjustments in formatting of event notification emails, and a fix to regression related with display of waypoint trajectory. Thanks, Ben for the report and suggestions.
Various adjustments and fixes (both UI and backend). Thanks, Ryan G. for the productive sessions and feedback.
Adjustments in event notification email formatting (backend 4.1.1). (#176).
More legible "Use plain text in emails" toggle in the email notification settings dialog.
Various API call adjustments per security enhancements in backend 4.1.0. Make sure you are using this or newer version especially if you need to create an account, sign in, or change your account details or password.
Fixed issue in playback mode that prevented the point cloud feature from displaying.
This is a significant release, involving both backend and frontend components.
The main change in this release is the use of a new underlying mechanism for handling asynchronous messages.
- These changes are mostly internal.
- The selection of this new mechanism is done via configuration in the backend,
so, we could revert to using the traditional mechanism if necessary.
Any change in the selected mechanism should only require:
- (1) A restart of the TethysDash system;
- (2) That users reload the Dash4 page in the browser.
Missiontab: The unit names associated with any overwritten parameters are now translated to their corresponding abbreviations when constructing the resulting command text to be sent out. (Thanks Ben for the heads-up.)
Using the "Preview SBDs" feature, one can see the effect like this:
Summarytab, the displayed ESP status widget for a vehicle will be the last one "archived" when there is no active deployment; otherwise, just the widget being updated during the ongoing deployment. (Thanks Steve.)
Logtab, and located next to the usual
shore.loglink, there is now also a link to the "ESP Logs" listing page. (Thanks Brent R. for the suggestion.)
PIC: Only the most recent "Signed-in as PIC" operator is shown. (Thanks Ben for the suggestion.) (The On-Call case still may display multiple operators.)
Adjustments in admin sections related with email notification settings. (Thanks WHOI for the suggestion.)
Adjustments in handling of selected tracking database assets:
- In general, the recent positions for the selected tracking DB assets are now retrieved automatically upon a reload of the Dash page.
- For the "Current Position Point Cloud", there's now a setting (saved in local storage), "Display on the map," to toggle the display of such points.
Filtering in the TrackDB selection now also considers the associated abbreviation as captured in the tracking database. E.g., entering
wrin the filter text field should include
WW_205881 (WrWlkr)in the filtered list. When available, this abbreviation is also included in the popup information for the asset on the map.
Experimental: new "Current Position Point Cloud" handling for asset positions managed in MBARI's Tracking Database. (Thanks John R. for the suggestion!)
Adjustments related with Slack notifications.
The tooltip for the version text located at the top right of the page will also show the version of the TethysDash backend system.
- Adjustments related with asynchronous notifications for the cell connection status updates. (Initially for the WHOI instance).
- All mission inserts, including all nested ones, should now get exposed in corresponding sections for editing the associated parameters as needed.
- Any overrides for a "Re-run" should also get properly reflected.
More visible popup notification upon submitting a mission or a command to the TethysDash backend. (Thanks Steve H. for the suggestion.)
- (Adjustments in the backend regarding the
4.3.2 (2020-12-16) - https://okeanids.mbari.org/dash4/
For vehicle selection, while refreshing the list, only show vehicles with a deployment. (Thanks, Ryan G., for the suggestion).
Remove the "status widget" section in "UI Settings -> Experimental." Having the toggle under the Summary tab suffices.
4.3 (2020-12-14) - https://okeanids.mbari.org/dash4/
- Experimental initial use of proper websockets server for asynchronous notifications:
- New Websockets section under UI Settings -> Experimental. Use the toggle there to connect/disconnect to the websocket server.
- Only vehicle cell connection status ("ping") are handled through this mechanism.
4.2.3 (2020-12-13) - https://okeanids.mbari.org/dash4/
Adjustments/fixes in async notification state handling
UI settings: Auto-refresh period now with ~0.5 minutes as minimum allowed (this is approximate).
4.2.2 (2020-12-11) - https://okeanids.mbari.org/dash4/
Fixed issue that would make command's Send button to stay disabled. (#84)
Spaces are now trimmed in all parameter values (including lat/lon) before issuing a mission. This is a general proper handling that also, in particular, should help avoid parsing problems on the vehicle side. (#82)
A fix in dispatch of deployment to properly reflect updates upon a launch or recover action. (For example, after a launch, the "Launch" button would still be displayed when coming back to the Deployment tab.)
Some minor layout adjustment under the Deployment tab to avoid partially obscuring contents in "DList" sections.
There's now a checkbox for inclusion of the ESP status widget for each vehicle in the Summary tab.
4.2.1 (2020-12-07) - https://okeanids.mbari.org/dash4/
Usability improvement related with the "add vehicle" button (+). This now opens a dialog listing all currently unselected vehicles along with associated deployment status: first, vehicles with an active deployment (with a green circle icon), then those with ended deployments (red icon), and finally those without any registered deployments. On desktop, the tooltip for a line will show more details about the deployment. The dialog will remain open until one is happy adding any vehicles for dispatch in the UI.
(Thanks Monique M. for the suggestion.)
Internal: Configurability related with MBARI's "ODSS-2-Dash" service, which supports the inclusion of tracking DB asset positions on the map.
4.2 (2020-10-30) - https://okeanids.mbari.org/dash4/
Implemented solution in the backend to handle improper URL encoding of commands caused by browsers that are not compliant with the HTTP/1.1 specification. Issue manifested by trying to issue a command that includes characters like
! onESPclient brent – 'slots [24,26,31] => [:dry,:archive_bac]'
Thanks Brent R. for reporting the problem. (#78)
4.1.4 (2020-10-14) - https://okeanids.mbari.org/dash4/
Fixed issue that caused incorrect waypoint dragging on the map (i.e., during mission preparation started from the Mission tab) in the case where some of the other waypoints are set to
Mission Tab: responsiveness adjustments specially when dealing with a large mission script (e.g.,
Science/isotherm_depth_canon, which has more than 500 parameters!).
4.1.3 (2020-10-12) - https://okeanids.mbari.org/dash4/
- Fixed issue in the "Note" dialog that occasionally made the Send button to remain disabled. (Thanks John R. for reporting.)
- Fixed logic for parsing of waypoints to be displayed on the map.
(As the concrete case recently noted, the pair of parameters
Science/circle_acoustic_contactmission was mistakenly extracted as a waypoint. Thanks Yanwu for the heads-up.)
4.1.1 (2020-10-09) - https://okeanids.mbari.org/dash4/
The Summary tab now includes Steve's ESP cartridge status widget.
Note: this for now has been included in a rather ad hoc way and only for Makai.
4.1 (2020-10-08) - https://okeanids.mbari.org/dash4/
Waypoint editor issues noted today should be fixed.
Improved display performance in the "send note" dialog, in particular when also opening the emoji selection 😉.
- Adjustments related with administrative options.
- The main page at https://okeanids.mbari.org/ has been updated and simplified as all functionality is now captured in the Dash UI itself.
- Branding adjustment (primary UI color).
🙌 First v4 release.
Versions in this new series will be available under the URL path
that is, https://okeanids.mbari.org/dash4/ in the MBARI case.
Only the new corresponding implementations are now exposed in the revamped Command and Mission tabs.
Performance improvement involving tracking DB position updates on the map.
Boat mode improvements.
Various usability, style, and layout adjustments.
Internal adjustments related with Google APIs.
Instead of pointing to the User/Admin webapp (which will also be undergoing some updates), Dash now directly handles creation of user account, update of user account details, as well as the main administration page.
Version 3 release notes have been moved to this page.