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
We want fine grained control of our ros nodes to allow better integration with the autonomy group. We will therefore implement this node as a state machine with predefined states from the Managed nodes concept.
We want the node to be able to transition between states controlled by a supervisor node that executes the current mission. To transition between the states we need to implement callbacks for the various transitions that will be invoked by the supervisor node.
The Aruco detector node already has many initialization functions implemented in a modular design so moving these into the relevant transition callbacks shouldn't require too much reconfiguration.
The current aruco detector is set up to filter the board detection directly inside the node in the camera frame using EKF of the vortex-vkf repo. This filtering will be moved over to the pi where we can easily access the camera_frame->odom transform and do filtering in the odom frame instead. Link up with the person responsible for this issue to help with the removal of everything related to the vortex-vkf.
Description of task
We want fine grained control of our ros nodes to allow better integration with the autonomy group. We will therefore implement this node as a state machine with predefined states from the Managed nodes concept.
We want the node to be able to transition between states controlled by a supervisor node that executes the current mission. To transition between the states we need to implement callbacks for the various transitions that will be invoked by the supervisor node.
These are the relevant callbacks taken from the Lifecycle demo README that we need to integrate into the aruco detector node.
The lifecycle_talker.cpp node of this demo shows how to implement these transition callbacks.
The Aruco detector node already has many initialization functions implemented in a modular design so moving these into the relevant transition callbacks shouldn't require too much reconfiguration.
The current aruco detector is set up to filter the board detection directly inside the node in the camera frame using EKF of the vortex-vkf repo. This filtering will be moved over to the pi where we can easily access the camera_frame->odom transform and do filtering in the odom frame instead. Link up with the person responsible for this issue to help with the removal of everything related to the vortex-vkf.
Suggested Workflow
Specifications
Contacts
No response
Code Quality
The text was updated successfully, but these errors were encountered: