Links get disconnected while tracking

Open
#62 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
computer-vision

Research direction

The report provides only a Link/Constraint/Optimizer configuration and no source file, test, or reproducible sequence. Start by reproducing the disconnection with the shown configuration and trace how parent_link and child_link are handled during tracking. Done means the configured parent-child relationship remains attached throughout tracking, with a regression test or reproducible verification.

Written by the indexing model from the issue text.

Description

Hi,

Firstly, Excellent work on the tracking system!

I'm currently experiencing an issue with the link functionality in M3t. It seems that the links are getting disconnected during the tracking process. My understanding is that the child and parent links should remain attached irrespective of the real-world object?

Here is a blueprint of the links in the config file:

Link:
  - name: child_link
    metafile: child_link.yaml
    body: child
    modalities: [child_region_modality, child_texture_modality, child_depth_modality] 
  - name: parent_link
    metafile: parent_link.yaml
    body: parent
    modalities: [parent_region_modality, parent_texture_modality, parent_depth_modality] 
    child_links: [child_link]

Constraint:
  - name: constraint
    metafile: constraint.yaml
    link1: parent_link
    link2: child_link

Optimizer:
  - name: optimizer
    root_link: parent_link
    constraints: [constraint]

Could you let me know if I am missing something in my implementation?

I appreciate your support in addressing this issue.
Let me know if you need any further clarification or information.

Thank you,

Dominant language
C++
Stars
1k
Forks
185
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DLR-RM/3DObjectTracking

All issues in DLR-RM/3DObjectTracking

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.