Skip to content
Snippets Groups Projects

Feature/manipulation pipeline

Closed Christoph Pohl requested to merge feature/manipulation-pipeline into master

@reister, @peller This is the branch from our ICRA paper. Does any of this need to be merged into the master? Otherwise, we should delete the branch

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • We should merge the following changes (at least):

    • Changes to the grasp memory: @peller initially had a point in separating the object xml from the grasps defined on the objects. However, as Simox tools will store the grasps in the main object xml file, this is rather unintuitive to work with. Therefore, I'd merge it.
    • The common places visu is also a nice feature.

    Hence, I'd propose to revert the changes to the ObjectPoseProvider and merge the rest.

  • AFAIK the grasps of the Manipulation Object are already Part of the Grasp Memory. However i would propose to change the structure of the grasps but this is not related to this MR.

  • Fabian Reister added 765 commits

    added 765 commits

    • 7aceef04...203afee5 - 764 commits from branch master
    • 42bbf5a8 - Merge remote-tracking branch 'origin/master' into feature/manipulation-pipeline

    Compare with previous version

  • Do not merge this. It's better to request objects that should be detected.

Please register or sign in to reply
Loading