DLR-RM / DLR-RM/BlenderProc

How to map the instance information in the generated BOP dataset to the pose information one by one

Open
#1,189 1 comment 0 reactions 0 assignees View on GitHub
first answer provided question
Dominant language
Python
Stars
3.7k
Forks
518
PR merge metrics
No merged PRs in 30d

Description

### Describe the issue

Dear developers and fellow code users,

I have a question regarding the generation of the BOP instance segmentation dataset using BlenderProc. I noticed that the segmented instances in **scene_gt_coco.json** do not correspond sequentially to the pose instances in **scene_gt.json**. How can I match the instances in **scene_gt_coco.json** to their corresponding pose entries in **scene_gt.json**?

For example, after visual inspection, the second instance in **scene_gt_coco.json** corresponds to the eighth instance in **scene_gt.json**.

![Image](https://github.com/user-attachments/assets/57d5caad-3b46-4f5c-8241-90509e4cd189)

### Minimal code example

```python
None
```

### Files required to run the code

_No response_

### Expected behavior

map the instance information in the generated BOP dataset to the pose information one by one

### BlenderProc version

2.8.0

Contributor guide

Open the contributing guide

Research direction

Start by comparing the instance entries in scene_gt_coco.json with the pose entries in scene_gt.json for one generated scene, using the reported second-versus-eighth example as a check. Document the reliable correspondence rule and identify how users can map every segmented instance to its pose entry without relying on visual inspection.

Written by the indexing model from the issue text.

Assessment

Tech stack
blender, python
Domain
computer-vision, data
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.