Arne Nordmann
Arne Nordmann
Minor, low-priority issue but curious: The system modes package build/installation seems to fail, if the package sources are not placed in the ros2 workspace, but just (symbollically) linked into the...
Introduce consistency check of SMH file (yaml). Examples for - currently not detected - inconsistencies: 1. systems specify parts that are themselves not specified in the SMH file 1. system...
When calling `ros2 lifecycle set`, the tool will abort with an error (*"Node not found"*). Reproduce: 1. Start mode manager with example system (see [system_modes_examples](system_modes_examples/README.md) 2. Execute `ros2 lifecycle set...
This PR introduces the necessary changes to build the system modes packages on Windows, e.g., visibility control. Part of https://github.com/micro-ROS/system_modes/issues/35 and the quality level
When calling the services provided by the mode manager (e.g., `/{system}/change_state`), the service call never returns and never executes. This blocks #35.
Mode manager raises a segfault when working with nodes that live in namespaces. The error happened when trying to prepend a namespace (e.g., in the example for one of the...
If we know through mode inference, that a certain state or mode of a (sub-)system can't be transitioned to, should `get_available_states` and `get_available_modes` of (sub-)systems report accordingly? Example: * Subsystem...
See https://github.com/micro-ROS/system_modes/pull/33: Builds on windows and macos are failing for different reasons: windows fails due to failing osrf_testing_tools_cpp, macos fails due to missing boost.
The mode manager usually knows the **target** state/mode and the **current** state/mode (via mode_inference) of a system or node. Currently we assume, that there is a trivial transition to the...