Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/customizations/robotics"
< Papyrus
(→Getting started) |
(→Get help, report bugs) |
||
| (20 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
| − | + | __NOTOC__ | |
| − | = | + | = Documentation = |
| − | Papyrus | + | === Overview === |
| + | * [[Papyrus/customizations/robotics/getstarted|Getting started]] - Introduction to the concept of ecosystem tiers and the approach for the composition of software components. | ||
| + | * [[Papyrus/customizations/robotics/modular|Modular and role based design]] - Supported diagrams depending on the modeling viewpoint. | ||
| + | * [[Papyrus/customizations/robotics/hara|Modeling behaviour (including Hazard and Risk analysis)]] | ||
| − | + | === System Specification === | |
| + | * [[Papyrus/customizations/robotics/ros2|ROS2 code generation and reverse engineering]] - Generate ROS2 code from a composition of software components; learn how to adopt the MDE approach from your existing ROS2 codebase | ||
| + | * [[Papyrus/customizations/robotics/bt|Task specification using behavior trees]] - Use or define new skill definitions to describe robotics tasks as behavior trees | ||
| − | = | + | === Safety Analyses === |
| + | * [[Papyrus/customizations/robotics/hara|Task-based HARA]] - Learn how to perform hazard analysis and risk assessment (HARA) of robotic behaviors. | ||
| + | <!-- * [[Papyrus/customizations/robotics/fta|Fault tree analysis]] - tbd. --> | ||
| − | == | + | === Get help, report bugs === |
| − | + | Please check the [[Papyrus/customizations/robotics/faq|FAQ]] first. In your question has not already been answered there, you can use the general Papyrus forum to get help for Papyrus for Robotics. The forum can be found at [https://www.eclipse.org/forums/index.php/f/121/ here], please prefix a subject with [Robotics] or [Robotics, ROS2] if your question targets the ROS2 code generation or reverse mechanisms. | |
| − | == | + | If you think that you have found a bug, you can 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. |
| − | + | ||
| − | + | ||
Revision as of 11:53, 28 March 2020
Documentation
Overview
- Getting started - Introduction to the concept of ecosystem tiers and the approach for the composition of software components.
- Modular and role based design - Supported diagrams depending on the modeling viewpoint.
- Modeling behaviour (including Hazard and Risk analysis)
System Specification
- ROS2 code generation and reverse engineering - Generate ROS2 code from a composition of software components; learn how to adopt the MDE approach from your existing ROS2 codebase
- Task specification using behavior trees - Use or define new skill definitions to describe robotics tasks as behavior trees
Safety Analyses
- Task-based HARA - Learn how to perform hazard analysis and risk assessment (HARA) of robotic behaviors.
Get help, report bugs
Please check the FAQ first. In your question has not already been answered there, you can use the general Papyrus forum to get help for Papyrus for Robotics. The forum can be found at here, please prefix a subject with [Robotics] or [Robotics, ROS2] if your question targets the ROS2 code generation or reverse mechanisms.
If you think that you have found a bug, you can use the Eclipse bugzilla to report it. In the following link, the product (Papyrus) and the the component (Robotics) are already selected 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.