-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
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
[registration] GICP alternates optimizing trans and rot part #5269
base: master
Are you sure you want to change the base?
[registration] GICP alternates optimizing trans and rot part #5269
Conversation
/// \brief optimization functor structure for translation part | ||
struct OptimizationFunctorWithIndicesTranslation | ||
: public BFGSDummyFunctor<double, 3> { | ||
OptimizationFunctorWithIndicesTranslation(GeneralizedIterativeClosestPoint* gicp) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Need to update gicp_->current_transformation_
so const
from const GeneralizedIterativeClosestPoint*
removed.
@@ -329,16 +376,19 @@ GeneralizedIterativeClosestPoint<PointSource, PointTarget>:: | |||
} | |||
g.head<3>() *= 2.0 / m; | |||
dCost_dR_T *= 2.0 / m; | |||
gicp_->computeRDerivative(x, dCost_dR_T, g); | |||
// gicp_->computeRDerivative(x, dCost_dR_T, g); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should I remove all rotation-related codes from OptimizationFunctorWithIndicesTranslation
?
@@ -506,6 +711,7 @@ GeneralizedIterativeClosestPoint<PointSource, PointTarget>::computeTransformatio | |||
break; | |||
} | |||
nr_iterations_++; | |||
is_translation_turn_ = !is_translation_turn_; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If current iteration is optimizing translation part, next iteration will optimize rotation part. There may be a better way.
@mvieth |
Any chance to get this moved forward? |
Ref: #5180