Class Hierarchy

Go to the graphical class hierarchy

This inheritance list is sorted roughly, but not completely, alphabetically:

[detail level 123]

CActionClientWrapper< ActionT >	Convenience wrapper for a rclcpp_action::Client that introduces synchronous goal handling functions
CActionContext< ActionT >
CActionContext< auto_apms_interfaces::action::CommandTreeExecutor >
CActionContext< auto_apms_interfaces::action::StartTreeExecutor >
▼CActionNodeBase
CRosActionNode< auto_apms_interfaces::action::CommandTreeExecutor >
CRosActionNode< auto_apms_interfaces::action::StartTreeExecutor >
CRosActionNode< auto_apms_interfaces::action::ArmDisarm >
CRosActionNode< auto_apms_interfaces::action::EnableHold >
CRosActionNode< auto_apms_interfaces::action::GoTo >
CRosActionNode< auto_apms_interfaces::action::Land >
CRosActionNode< auto_apms_interfaces::action::Mission >
CRosActionNode< auto_apms_interfaces::action::RTL >
CRosActionNode< auto_apms_interfaces::action::Takeoff >
CRosActionNode< ActionT >	Abstract class to wrap rclcpp_action::Client<>
CRosServiceNode< ServiceT >	Abstract class use to wrap rclcpp::Client<>
▼CClassLoader
CNodePluginClassLoader	Version of pluginlib::ClassLoader specifically for loading installed behavior tree node plugins
CTreeBuilderClassLoader	Version of pluginlib::ClassLoader specifically for loading installed behavior tree builder plugins
▼CConditionNode
CRosSubscriberNode< GlobalPositionMsg >
CRosPublisherNode< MessageT >	Abstract class to wrap a ROS publisher
CRosSubscriberNode< MessageT >	Abstract class to wrap a Topic subscriber. Considering the example in the tutorial: https://docs.ros.org/en/humble/Tutorials/Beginner-Client-Libraries/Writing-A-Simple-Cpp-Publisher-And-Subscriber.html
▼CModeBase
▼CModeBase< GoToActionType >
CPositionAwareMode< GoToActionType >
▼CModeBase< ActionT >	Class to model the mode referring to an external task
CPositionAwareMode< ActionT >
CModeExecutorFactory< ActionT, ModeT >
CModeExecutorFactory< GoToActionType, GoToMode >
CNodeManifest	Data structure for resource lookup data and configuration parameters required for loading and registering multiple behavior tree node plugins
▼CNodeRegistrationInterface
CNodeRegistrationFactory< T, requires_ros_node_params >
CNodeRegistrationParams	Behavior tree node registration parameters
CRosNodeContext
▼Cruntime_error
▼CExceptionBase	Base class for all exceptions of AutoAPMS
CResourceIdentityFormatError
CRosNodeError
CTreeBuildError
CTreeExecutionError
CTreeXMLFormatError
CResourceNotFoundError
▼CStatusChangeLogger
CBTStateObserver
▼CTask< ActionT >	Generic base class for robot actions
CModeExecutor< ActionT >
CTask< auto_apms_interfaces::action::ArmDisarm >
▼CTask< auto_apms_interfaces::action::EnableHold >
CModeExecutor< auto_apms_interfaces::action::EnableHold >
▼CTask< auto_apms_interfaces::action::Land >
CModeExecutor< auto_apms_interfaces::action::Land >
▼CTask< auto_apms_interfaces::action::Mission >
CModeExecutor< auto_apms_interfaces::action::Mission >
▼CTask< auto_apms_interfaces::action::RTL >
CModeExecutor< auto_apms_interfaces::action::RTL >
▼CTask< auto_apms_interfaces::action::Takeoff >
CModeExecutor< auto_apms_interfaces::action::Takeoff >
CTreeBuilder	Class for creating behavior trees according to the builder design pattern
CTreeBuilderBase
▼CTreeBuilderFactoryInterface
CTreeBuilderFactoryTemplate< T >
▼CTreeExecutor
CTreeExecutorServer
CTreeResource	Struct containing behavior tree resource data
CVehicleCommandClient