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

Parametric Point2Point2Range #398

Closed
wants to merge 2 commits into from

Conversation

Affie
Copy link
Member

@Affie Affie commented Feb 6, 2021

cc @dehann
PR for discussing what to do with factors like Point2Point2Range.
See EuclidDistance like factor and test for batch parametric solve

@Affie Affie added this to the v0.0.x milestone Feb 6, 2021
@Affie Affie self-assigned this Feb 6, 2021
function (cfo::CalcFactor{<:Point2Point2Range})(rho, xi, lm)
# Basically `EuclidDistance`
return [rho[1] - norm(lm .- xi)]
end
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

right, understand now. Best solution would be to drop the additional theta variable, but we should look at how best to do together with the Manifolds.jl upgrade -- lots of overlap.

Copy link
Member

@dehann dehann Feb 7, 2021

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I never liked the additional theta thing. Perhaps the solution is just to skip immediately through to JuliaRobotics/IncrementalInference.jl#1051

and then we can drop the additional theta value since the inflated (high entropy) proposal will give the necessary spread.

@dehann
Copy link
Member

dehann commented Feb 7, 2021

Hi @Affie , with IIF v0.21 tagged tests starting to pass here again although "This and Masters" is failing in parametric. Perhaps just check that out when you get a chance please.

@Affie
Copy link
Member Author

Affie commented Feb 7, 2021

Point2Point2Range test is failing because its not converging correctly every time, it depends on the initial values. It seems like such a small example that I’m sure fine tuning the solver parameters can make it better.
I mainly opened PR for discussion. If we are looking at dropping theta, then i would say we keep both definitions until high entropy version works. In that case i can look at getting this passing an merge.

@dehann
Copy link
Member

dehann commented Feb 8, 2021

@Affie
Copy link
Member Author

Affie commented Feb 14, 2021

We can now consolidate and remove extra theta variable JuliaRobotics/IncrementalInference.jl#1051
I'll update for next release.

@Affie Affie modified the milestones: v0.0.x, v0.13.0 Feb 14, 2021
@Affie
Copy link
Member Author

Affie commented Feb 15, 2021

Combined with #416

@Affie Affie closed this Feb 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants