add a component that lists all running nodes
project time: 1-2 weeks
all ros2 nodes have a name and you can check for a list of all nodes that are running with roslib js.
finding all the nodes that are running
the useRos hook returns a ROSLIB.Ros object whose functions can be found here.
Use the getNodes method (unless you have a better idea).
react UX
ideally the component has two boxes (one red and one green). Compare the list of running nodes to the known list of nodes that should be running (this list will be provided later). Any nodes that are not running that should be running get put into the red box. All nodes that are running (and should be go in the green box).
optional
Nodes that are running, but are not in the list of expected nodes should be colored yellow.
example behavior
expected_nodes = [a, b, c]
actual_nodes = [a, b, d]
red:
c (the c node is missing)
yellow:
d (running, even though we don't expect it)
green:
a, b (both running, both expected)
add a component that lists all running nodes
project time: 1-2 weeks
all ros2 nodes have a name and you can check for a list of all nodes that are running with roslib js.
finding all the nodes that are running
the useRos hook returns a ROSLIB.Ros object whose functions can be found here.
Use the getNodes method (unless you have a better idea).
react UX
ideally the component has two boxes (one red and one green). Compare the list of running nodes to the known list of nodes that should be running (this list will be provided later). Any nodes that are not running that should be running get put into the red box. All nodes that are running (and should be go in the green box).
optional
Nodes that are running, but are not in the list of expected nodes should be colored yellow.
example behavior
expected_nodes = [a, b, c]
actual_nodes = [a, b, d]
red:
c (the c node is missing)
yellow:
d (running, even though we don't expect it)
green:
a, b (both running, both expected)