InfiniTAM
InfiniTAM copied to clipboard
A Framework for the Volumetric Integration of Depth Images (with some experimental code to handle dynamic scenes)
There is absolutely no need for fully-expanded template stubs. Instead, make the client classes have templated compartments, i.e. for this case: - [ ] Make a DynamicSceneVoxelEngine_IndexSpecialized class, specialized for...
- [x] the separate visible entry lists should be used as they were before in some versions of allocation functions (see old SceneReconstructionEngine) - [x] BuildVisibleLists functions (see TODOs in...
Right now the mechanism for reading data for / switching between frames is almost duplicated by InfiniTAM and SDFViz. It should be conglomerated inside the ITMSceneLogger class instead.
Atomic cross-platform functionality should be provided via templated atomic type wrapper, not macros
- [ ] To prevent modifying existing bit structure, the way to abstract this away is by making the member variable private, and provide two public access method: one returning...
(but preserve organization using comments) -This will make adding new files much easier in CLion (add-to-existing-target may be used).
Part of / relates to #192
- [x] Re-enable Appveyor testing - [x] Update Appveyor config to skip VTK build - [x] ~Add alternative configuration -- CPU-only~ - [x] Set up local cloud - [x] Adjust...
~add variadic argument to DIEWITHEXCEPTION and it's variant(s), i.e. DIEWITHEXCEPTION( x, __VA_ARGS__), and use this to somehow put in data into the exception message.~ - [ ] The check-kernel routine...