General UI considerations

[SeaTechRC]

Hello,

Here are some considerations about the UI of the robot that we deemed important for users:

• A rough explanation of the navigation modes (MAYBE with a small demo gif/video?)
• A general status display containing in part (considering row on field navigation):
  1. What row is the robot in? (live update when you are trying to start the robot in a certain row)
  2. How far in the row is the robot?
  3. Current average speed (maybe over a timespan of 1-5 minutes?)
  4. What is my current action? (using rosys @track decorator would be suited)
  5. Estimated time left in row and or field.
  6. Deviation from target line (the 3d view gives some indication, but it can be very clunky at times.)
• A slider for confidence values (perhaps with coloration). Users that do not have experience with AI-classifiers might be unsure what value is suited. This could perhaps be a percentage relative to the average confidence for a given crop in the training data?
• A simplified log only showing the basic tasks executed by the robot. (finished row, starting workflow of implement, no rtk, bumper hit, etc.). This information should enable users to get a better understanding about the robots behavior without needing to watch it throughout the big portion of its automation. The enries could potentially be collapsable if the log entries follow the @track hierarchy or when an entry is repeated a certain amount of times.
• A general info field about the robot with software versions for critcal parts such as (they should also indicate if it is a release version or a changed version similar to how lizard version are declared dirty when changed):
  1. Lizard
  2. Rosys
  3. FieldFriend
  4. nicegui
  5. on-air?
• More connection information:
  1. What is the signal quality of WIFI or GSM?
  2. Data usage statistics
• GNSS info should contain correction data age (if possible) and how many satellites have been found/are in use.
• Runtime in automation needs to be on main page or in the sidebar menu.
• An indicator what values can be adjusted at runtime. Perhaps simply disabling unchangeable values when an automation is started. (Tornado turns, linear speed, tornado angle, etc.)
• Explanation to learning loop tags.
• Headers for most things (currently missing for the navigation and implement selection section.)

A special mention is localization.
A lot of potential users might not understand english.
There should be a way to localize all text on the main page of the robot.

We hope these considerations are of use.
Kind regards

[rodja]

Thanks for the great roundup. We will need to split this into several pull requests and feature requests to discuss them individually. But this is a great start.

[Johannes-Thiel]

Hi,

We had a internal discussion about what features fit into our next milstones and added some of the requested features.

• We added the @track decorator. The diagram for this can be seen on the /dev page on the top. Add @track to the Automations and Navigations #251
• We implemented a simple Log view. This will show all past notifications. For this we also did some restructuring for the logs and adding/remmoving some notifications. Furthermore we moved some of the info logs to the debug log. The logging scope can be changed on the /logging page. Add log view #253
• The automation time tracking is already implemented and can be seen in the sidebar. KPI Time Logging Fix #208
• Currently we are working on a robot dashboard. This will diesplay the current status of the robot, the rosys version and will provide links to nicegui on air. Swarm Dashboard Connection #250

I hope this will help with some of youre issues.
Kind regards.