So every time there is a new keyframe that's supposed to be added to the map, I believe goes into ProcessNewKeyFrame().
This is when the mutual information between a map-point and the keyframe gets updated.
I was wondering why don't we do mpCurrentKeyFrame->AddMapPoint(pMP, i) as well?
Everywhere else pMP->AddObservation() and mpCurrentKeyFrame->AddMapPoint() are used commonly..
I believe both these lines should be written to maintain the consistency of the graph (a graph that connects keyframes and mappoints).
It is only in LocalMapping::ProcessNewKeyFrame() I see some problem.
Can you guys please explain why mpCurrentKeyFrame->AddMapPoint(pMP, i) is skipped in ProcessNewKeyFrame() ?
So every time there is a new keyframe that's supposed to be added to the map, I believe goes into ProcessNewKeyFrame(). This is when the mutual information between a map-point and the keyframe gets updated.
I was wondering why don't we do
mpCurrentKeyFrame->AddMapPoint(pMP, i)
as well?Everywhere else
pMP->AddObservation()
andmpCurrentKeyFrame->AddMapPoint()
are used commonly.. I believe both these lines should be written to maintain the consistency of the graph (a graph that connects keyframes and mappoints).It is only in LocalMapping::ProcessNewKeyFrame() I see some problem.
Can you guys please explain why
mpCurrentKeyFrame->AddMapPoint(pMP, i)
is skipped inProcessNewKeyFrame()
?