Dash applies the following logic to eventually display the waypoint trajectory (as a sequence of lines connecting such points) associated to a running mission on the map:
The logic is triggered when the
Started mission <name>important event is generated.
The name of the mission indicated in such
Started missionevent MUST match the simple name (i.e., no path, no extension) of the mission file itself as exposed in the preceding
For example, if the started mission event is:
Started mission sci2
then Dash will recognize the preceding "load" command:
got command load ./Missions/Science/sci2.xml`
- The name of the mission is what is captured with the
Idattribute in the XML file.
- Currently, not all missions scripts have the value of this
Idequal to the simple name of the file.
Then, Dash will gather the waypoints from:
The arguments in the corresponding mission file that refer to "latitude" or "longitude" (see below).
All immediately preceding
setcommands in the event flow (with respect to the
Started missionevent) overriding any such arguments.
Extraction of latitude/longitude positions to collect the waypoints is ONLY based on:
Defined arguments in the mission with names Lat, Lon, Latitude, or Longitude, plus those same names with a numeric suffix, e.g., Lat1. (Dash will pair them, e.g.,
Lon3, assuming they define specific locations.)
"Set" commands in the event flow that look like the following (using Lat3 as an example):
got command set <mission-name>.Lat3 <val> degree
For a displayed waypoint trajectory, clicking or tapping on any of the dashed lines will open a popup containing the following:
- Last started mission event
- Vehicle position at time of the started mission event
- All collected (non-NaN) waypoints
- Hovering the mouse on a line with coordinates will highlight the corresponding position on the map
A "center at" button to center the map at the given position
Also a button 'More details' to open one other popup with further details about the relevant mission events: