| ... | ... | @@ -22,7 +22,7 @@ |
|
|
|
* link:safecc[Contracts and Assertions] - How to specify assertions and constraints
|
|
|
|
|
|
|
|
* link:ros2/ros2[Code generation (for ROS 2)]
|
|
|
|
* link:"reverse/reverse engineering"[Reverse Engineering (from ROS 2)]
|
|
|
|
* link:reverse/reverse-engineering[Reverse Engineering (from ROS 2)]
|
|
|
|
* Simulation
|
|
|
|
|
|
|
|
[[application_examples]]
|
| ... | ... | @@ -31,7 +31,7 @@ |
|
|
|
* link:demos/pick-and-place[Pick-and-Place use-case from RobMoSys project] - The description of the pick and place task and its execution with the behavior tree in simulation using ISybot robot
|
|
|
|
* link:demos/drone[Drone use-case from C4D project] - Simulated reactive drone navigation and landing using behavior trees
|
|
|
|
* link:demos/nav2[Low-Code programming of a Nav2 example] - Simulated mobile robot with reactive battery management in Nav2
|
|
|
|
* link:"demos/autonomous vehicle"[Autonomous vehicle use-case from DIH4AI project] - Scenario-based validation of behavior tree-based autonomous driving policies in CARLA (using the CARLA/ROS 2 bridge)
|
|
|
|
* link:demos/autonomous-vehicle[Autonomous vehicle use-case from DIH4AI project] - Scenario-based validation of behavior tree-based autonomous driving policies in CARLA (using the CARLA/ROS 2 bridge)
|
|
|
|
|
|
|
|
[[developer_guidance]]
|
|
|
|
=== Developer Guidance
|
| ... | ... | @@ -48,4 +48,4 @@ |
|
|
|
* Publications
|
|
|
|
* link:faq[FAQ]
|
|
|
|
* Community -- RobMoSys wiki, https://www.eclipse.org/forums/index.php/f/121/[Papyrus forum] (please prefix a subject with [Robotics] or [Robotics, ROS2])
|
|
|
|
* Bug reporting: use the Eclipse bugzilla to report it. In the following link, the product (Papyrus) and the the component (Robotics) are already selected https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Papyrus&component=Robotics[File a Papyrus for Robotics bug]. Use the same naming convention as for the forum, i.e. prefix with [Robotics] or [Robotics, ROS2] and check out whether the bug is eventually already existing (the browser proposes possible existing bugs as you type your bug title]. Please make also sure that the steps to reproduce the bug are clearly described, eventually add your model. |
|
|
|
* Bug reporting: use gitlab issue mechanism. Use the same naming convention as for the forum, i.e. prefix with [Robotics] or [Robotics, ROS2] and check out whether the bug is eventually already existing (the browser proposes possible existing bugs as you type your bug title]. Please make also sure that the steps to reproduce the bug are clearly described, eventually add your model. |
aradermache <ansgar.radermacher@cea.fr>