Sergey Sharybin ed131e67c4 Add check for points behind camera in euclidan BA cost functor ... In cases keyframes are no so good, algebraic two frames construction could produce result, for which more aggressive Ceres-based BA code will fall to a solution for which points goes behind the camera, which is not so nice. Seems in newer Ceres returning false from cost functor wouldn't abort solution, but will restrict solver from moving points behind the camera. Works fine in own tests, but requires more tests.		2013-05-09 16:38:58 +00:00
..
libmv	Add check for points behind camera in euclidan BA cost functor	2013-05-09 16:38:58 +00:00
patches	Updates to libmv's bundle.sh to make sure libmv upstream	2013-03-01 11:52:38 +00:00
third_party	Update Ceres to current upstream version	2013-04-22 09:25:37 +00:00
bundle.sh	Updates to libmv's bundle.sh to make sure libmv upstream	2013-03-01 11:52:38 +00:00
ChangeLog	Fix for bundle adjusting with motion restricted	2013-04-14 23:43:00 +00:00
CMakeLists.txt	Reconstructed scene scale ambiguity improvement	2013-05-09 16:38:43 +00:00
files.txt	Reconstructed scene scale ambiguity improvement	2013-05-09 16:38:43 +00:00
libmv-capi.cpp	Reconstructed scene scale ambiguity improvement	2013-05-09 16:38:43 +00:00
libmv-capi.h	Multi-threaded frame calculation for movie clip proxies	2013-03-15 11:59:46 +00:00
mkfiles.sh	Initial Ceres integration into Blender	2012-06-10 15:27:41 +00:00
SConscript	Updates to libmv's bundle.sh to make sure libmv upstream	2013-03-01 11:52:38 +00:00