Use correct calibration matrices for each frame #64
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As also pointed out in #43 , for both training and testing the calibration matrices used are always the averaged one instead of the correct ones for each single frame.
In different frames this creates a visible offset that might hinder the training process.
The modifications here implemented address this problem: first fetching the correct calibration matrices P, T and R, then passing them down to the functions used (mainly in utils.py)