Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
E
example-robot-data
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 7
    • Issues 7
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Gepetto
  • example-robot-data
  • Issues
  • #1

Closed
Open
Opened Feb 22, 2019 by Carlos Mastalli@cmastallDeveloper

Agreement with the data organization

Robot folders hasn't exactly organization as original ROS packages. This point was raised here: https://gepgitlab.laas.fr/loco-3d/crocoddyl/merge_requests/107. And I copy from there the following motivations of actual description:

  • A package.xml is used by ROS, we probably don't want to add ROS dependency.
  • We don't depend on xacro files, so we don't need to create URDF folder for putting just one file.

Additionally we might want add extra information for ensuring that users don't use these models for robot deployment.

@ostasse, @gsaurel, @jmirabel and @nmansard let's find an agreement here.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: gepetto/example-robot-data#1