-
Notifications
You must be signed in to change notification settings - Fork 21
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
New localProduct
too eager on partials as 1DOF only
#1206
Comments
localProduct
too eager on partialslocalProduct
too eager on partials as 1D only
localProduct
too eager on partials as 1D onlylocalProduct
too eager on partials as 1DOF only
Need to update (adding to ongoing AMP.MKD upgrades): IncrementalInference.jl/src/GraphProductOperations.jl Lines 28 to 31 in 22898c5
IncrementalInference.jl/src/GraphProductOperations.jl Lines 82 to 85 in 22898c5
|
The plan is to do Manifolds.jl consolidation first
as the last step in this epic. cc @Affie |
Hi @lemauee, Just an update. I think this issue is a big part of the problems you were seeing in JuliaRobotics/RoME.jl#378, JuliaRobotics/RoME.jl#380 where Pose2Point2Range factors were losing correlation between dimensions because partials we treated too naively (1DOF at a time). A workaround is easy, but Optim.jl has to work harder. The proper fix is to combine with Manifolds.jl first (what i have been doing the past 3 weeks) and rebuild the approx belief product wrappers. Basically, we have incompatible partials and Optim.jl plumbing in the existing/old code. This was not an issue before, but in consolidating parametric and nonparametric plumbing this incompatibility showed up through the refactoring. Previously Optim was just grinding away until the right answer was found. Building out the new abstractions with Manifolds.jl is the right place to make these two aspects compatible. The fix should be available either in IIF v0.22.x or latest v0.23.0 (depending on how semver deprecation rules play out). Best, |
partials
means dimension constrained, as in only some dimensions are effected by the partial factor. Something like a Range factor operates on XY (Z) dimensions simultaneously through the Minimization process. It is wrong to overconstrict partials to work one dimension at a time. Related issue #1010 .MWE:
NOTE,
RoME.Pose2Point2Range
is indicated as apartial
https://github.com/JuliaRobotics/RoME.jl/blob/03129f5bd100a3d6e2600bf692b98c9bb9e928c4/src/factors/Range2D.jl#L51
The text was updated successfully, but these errors were encountered: