Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus/customizations/robotics"
< Papyrus
(Merge edit by Christophe.aussagues.cea.fr) |
(→User Guidance) |
||
| Line 12: | Line 12: | ||
* General Workflow | * General Workflow | ||
| − | |||
* [[Papyrus/customizations/robotics/servicedef|Service Definition]] - How to create a service definition | * [[Papyrus/customizations/robotics/servicedef|Service Definition]] - How to create a service definition | ||
| − | * System Design | + | * [[Papyrus/customizations/robotics/compdef|Component Definition]] - How to create a component definition |
| + | * [[Papyrus/customizations/robotics/servicedef|System Design]] - How to design a system | ||
* [[Papyrus/customizations/robotics/bt|Task Modelling]] - Use or define new skill definitions to describe robotics tasks as behavior trees | * [[Papyrus/customizations/robotics/bt|Task Modelling]] - Use or define new skill definitions to describe robotics tasks as behavior trees | ||
* Risk Assessment | * Risk Assessment | ||
| − | |||
** [[Papyrus/customizations/robotics/hara|Task-based HARA]] - Learn how to perform hazard analysis and risk assessment (HARA) of robotic behaviors. | ** [[Papyrus/customizations/robotics/hara|Task-based HARA]] - Learn how to perform hazard analysis and risk assessment (HARA) of robotic behaviors. | ||
* Safety Analysis | * Safety Analysis | ||
Revision as of 09:18, 6 August 2020
Documentation
Introduction
- Installation - Installation instructions
- Getting started - Introduction to the concept of ecosystem tiers and the approach for the composition of software components.
- Modular and role based design - General Concepts (supported diagrams depending on the modeling viewpoint)
User Guidance
- General Workflow
- Service Definition - How to create a service definition
- Component Definition - How to create a component definition
- System Design - How to design a system
- Task Modelling - Use or define new skill definitions to describe robotics tasks as behavior trees
- Risk Assessment
- Task-based HARA - Learn how to perform hazard analysis and risk assessment (HARA) of robotic behaviors.
- Safety Analysis
Developer Guidance
- Release Roadmap
- Development Conventions, see Papyrus coding standards
- Quality Assurance
- Installation of the Development Environment
- Build process
Other Documentation
- Publications
- FAQ
- Community -- RobMoSys wiki, 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 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.