Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can you solve multiple orphaned graphs? #518

Closed
keevindoherty opened this issue Jul 4, 2018 · 7 comments · Fixed by #519
Closed

Can you solve multiple orphaned graphs? #518

keevindoherty opened this issue Jul 4, 2018 · 7 comments · Fixed by #519

Comments

@keevindoherty
Copy link
Contributor

For example, a sequence of poses joined by factors and a separate landmark with a prior.

@dehann
Copy link
Member

dehann commented Jul 5, 2018

Hi,

Not yet in the current implementation but shouldn't be too hard to add that -- the solver can be repeated (in parallel) across all orphaned graphs. I'll add it to a milestone as a feature request. Thanks for commenting!

@dehann
Copy link
Member

dehann commented Jun 25, 2019

xref JuliaRobotics/Caesar.jl#279

@dehann
Copy link
Member

dehann commented Oct 16, 2019

fixed this by accident (seriously). new CSM in IIF v0.7.x allows for forest of trees to be solved.

@dehann dehann closed this as completed Oct 16, 2019
@dehann dehann reopened this Dec 13, 2019
@dehann
Copy link
Member

dehann commented Dec 13, 2019

still a bug somewhere a few cases.

@Affie
Copy link
Member

Affie commented Jan 15, 2020

One bug is related to buildCliquePotentials. It starts from clique 1 and follows children. So an orphaned tree section does not have its potentials build.
Looking for all the roots isRoot(tree, cliqId) and then traversing the tree from all cliqId (and not 1) fixes this.

@dehann
Copy link
Member

dehann commented Jan 16, 2020

Right, that makes sense thanks for pushing the fix up too!

@dehann
Copy link
Member

dehann commented Jan 16, 2020

Note for later readers, this issues was transferred over from Caesar.jl, and is now fixed with PR #519

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants