What happens to keyframes received by the front-end ?

[Tariq-Abuhashim]

Is this source complete?
What happens to keyframes received at the front-end?
In communicator_base.cpp , looking at auto CommunicatorBase::ProcessBufferIn()->void function, nothing seems to be using buffer_keyframes_in or buffer_landmarks_in.

Also, the following functions don't do anything:

if(this->TryLock()){
    this->ProcessKeyframeMessages()
    this->ProcessLandmarkMessages()
    this->ProcessNewKeyframes()
    this->ProcessNewLandmarks()
    this->ProcessAdditional()
    this->UnLock()
}

Are you planing on releasing the full code anytime in the future?

[patriksc]

Yes, this is complete. As explained in the manual, COVINS provides the infrastructure to send data from the server back to an agent to allow the re-use information from the server onboard the agent. However, we do not provide a certain algorithm for map re-use, this needs to be implemented by the user. Unfortunately, there is currently no active work on including such an algorithm into the COVINS framework.

[patriksc]

Problem seems resolved for the moment - closing this issue.