The new tracker will stick to the "Engine" convention for now. We can tentatively call it DenseColorAndDepthRigidAlignmentEngine, but it might make sense to combine the different tracker variants in a single class in case the old "Extended" tracker actually re-uses large portions of code from the old "Depth" tracker and the old "Color" tracker.
Consequence of the latter:
At this point, we should be more or less clear on what the architecture should be (how to organize the data and the classes/structs).
The parameters will need to be revised to use serializable structures and enums:
Stick to the old function interface for now, hence the following functions will need to be re-implemented and tested for CPU/GPU and PVA/VBH:
The new tracker will stick to the "Engine" convention for now. We can tentatively call it DenseColorAndDepthRigidAlignmentEngine, but it might make sense to combine the different tracker variants in a single class in case the old "Extended" tracker actually re-uses large portions of code from the old "Depth" tracker and the old "Color" tracker.
Consequence of the latter:
At this point, we should be more or less clear on what the architecture should be (how to organize the data and the classes/structs).
The parameters will need to be revised to use serializable structures and enums:
Stick to the old function interface for now, hence the following functions will need to be re-implemented and tested for CPU/GPU and PVA/VBH: