Follow-up from "Resolve "Add Object Memory""

The following discussions from !128 (merged) should be addressed:

• @RainerKartmann started a discussion: (+2 comments)

  Can we create separate ARON types for ObjectID and OrientedBoundingBox? It would be good when we can re-use them separately. There should be a way to include other ARON types.

• @RainerKartmann started a discussion:

  Same here (define it in another xml)

• @RainerKartmann started a discussion: (+3 comments)

  How does this work? Where is ObjectAttachmentInfo defined in ARON? o:

• @RainerKartmann started a discussion: (+1 comment)

  Yes it would be good if we have a definite, stron timestamp type in ARON. @fratty Don't we have something like that?

• @RainerKartmann started a discussion:

  1. This is duplicated?
  2. We only need the object-local bounding box. The OOBB in robot and global frame are computed on-demand by armarx::objpose::ObjectPose.

see https://gitlab.com/ArmarX/RobotAPI/-/issues/32

changed the description

marked this issue as related to #32 (closed)

marked the checklist item @RainerKartmann started a discussion: (+3 comments) as completed

marked the checklist item @RainerKartmann started a discussion: (+1 comment) as completed

marked the checklist item @RainerKartmann started a discussion: as completed

added module::armem label

created merge request !133 (merged) to address this issue

mentioned in merge request !133 (merged)

marked the checklist item @RainerKartmann started a discussion: (+2 comments) as completed

marked the checklist item @RainerKartmann started a discussion: as completed

closed