Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Papyrus/customizations/robotics"

(Documentation)
(Introduction)
Line 5: Line 5:
 
== Introduction ==
 
== Introduction ==
  
* Installation
+
* [[Papyrus/customizations/robotics/installation|Installation]] - Installation instructions
 
* [[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/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/modular|Modular and role based design]] - General Concepts (supported diagrams depending on the modeling viewpoint)
* General Concepts
+
  
 
== User Guidance ==
 
== User Guidance ==

Revision as of 07:42, 14 July 2020


Documentation

Introduction

User Guidance

  • 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
  • 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.

Back to the top