You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm calling it a 'user dasboard', but what I really mean here is a graphical user interface (GUI) for some users to be able to interact with the rover. Initially it will only be visual stuff, but we can even add useful commands and other things into here (which will be great).
First, we need to investigate what tools we need to create the front-end. Mainly we need to:
Be easily able to send over ROS data for camera streams, mapping data (which pretty much end up being ROS topics). Whatever we use needs to be able to 'consume' these messages easily.
Needs to be able to easily add visual features, and configure them. There's alot of GUI tools out the (QT GUI is one, there's probably a bunch more. We can also make something ourselves straight from scratch but that's probably not worth it). We need to find a tool that is robots to be able to display data, display mapping information, maybe calibrate/configure things on our rover easily.
Needs to be relatively easy to use. I want people to be able to work on this collaboratively, let's try to see if we can keep it to C++, maybe python since it's easy just to stick on topic for our team. Open to other suggestions but C++ is preferred.
Look into this and come up with a few tooling options. Let's start by using THE EASIEST, MOST SIMPLE ONE first (and try to make sure that this one is good for scaling up our basic stuff).
The text was updated successfully, but these errors were encountered:
I'm calling it a 'user dasboard', but what I really mean here is a graphical user interface (GUI) for some users to be able to interact with the rover. Initially it will only be visual stuff, but we can even add useful commands and other things into here (which will be great).
First, we need to investigate what tools we need to create the front-end. Mainly we need to:
Look into this and come up with a few tooling options. Let's start by using THE EASIEST, MOST SIMPLE ONE first (and try to make sure that this one is good for scaling up our basic stuff).
The text was updated successfully, but these errors were encountered: