Documentation/Labs/OpenCV - Revision history

Fedorov: /* Status */

2016-03-07T21:05:08Z

Status

2016-01-14T20:32:17Z

Status

2015-12-16T19:51:30Z

Status

2015-11-05T19:52:15Z

Unresolved questions

2015-10-02T21:45:39Z

2015-10-02T20:18:57Z

Approach

2015-10-02T20:01:06Z

Unresolved questions

2015-10-02T20:00:33Z

References

2015-10-02T19:57:53Z

Status

2015-10-02T19:53:35Z

Approach

@@ Line 31: / Line 31: @@
 =Status=
 * Jan 2016:
 ** Slicer's version of ITK has been patched to allow building the OpenCV bridge module externally, SlicerOpenCV updated to use that functionality.

@@ Line 31: / Line 31: @@
 =Status=
 * Dec 2015: Initial tree of the extension is available publicly https://github.com/SBU-BMI/SlicerOpenCV
 * Oct 2015: Initial discussions and initial plan completed. Update posted to the developer list [1].

@@ Line 31: / Line 31: @@
 =Status=
-Initial discussions and initial plan completed. Update posted to the developer list [1].
+* Dec 2015: Initial tree of the extension is available publicly https://github.com/SBU-BMI/SlicerOpenCV
 =References=
 [1] http://slicer-devel.65872.n3.nabble.com/OpenCV-in-Slicer-td4035068.html

← Older revision		Revision as of 19:52, 5 November 2015
Line 25:		Line 25:

	Answers:		Answers:
		+	* SBU (Yi): Matrices, color space conversion, iso contour extraction
		+	** source code at [https://github.com/SBU-BMI/u24-software/tree/master/analysis-library/yi-codes/src SBU-BMI (private)] includes opencv.hpp and gpu.hpp
	* Montreal group (MNI, Louis Collins): only need camera calibration and basic functionality to track colored objects in video; no GPU or Intel libraries needed		* Montreal group (MNI, Louis Collins): only need camera calibration and basic functionality to track colored objects in video; no GPU or Intel libraries needed

@@ Line 23: / Line 23: @@
 * what OpenCV packages are needed by the target users?
 * are Intel-specific of GPU-specific computational libraries needed? (these have licensing restrictions)
 =Status=

← Older revision		Revision as of 20:18, 2 October 2015
Line 8:		Line 8:

	Extensions that need OpenCV would declare SlicerOpenCV as a dependency, which would automatically fetch the extension on install from the Extension Manager, or initialize all necessary paths to the libraries for building a dependent module. This extension will also build ITK OpenCVBridge module to facilitate integration with ITK-based applications.		Extensions that need OpenCV would declare SlicerOpenCV as a dependency, which would automatically fetch the extension on install from the Extension Manager, or initialize all necessary paths to the libraries for building a dependent module. This extension will also build ITK OpenCVBridge module to facilitate integration with ITK-based applications.
		+
		+	We should also consider building pydicom as part of that extension.
		+
		+	=Alternative approaches considered=

	Other options discussed were:		Other options discussed were:

← Older revision		Revision as of 20:00, 2 October 2015
Line 25:		Line 25:

	=References=		=References=
−	# [~~Lagerburg~~-~~2005] {{note\|Lagerburg~~-~~2005}} test~~	+	[1] http://slicer-devel.65872.n3.nabble.com/OpenCV-in-Slicer-td4035068.html

@@ Line 11: / Line 11: @@
 Other options discussed were:
-- installation of OpenCV from binary package (discarded due to incompatibility of the compilers used for OpenCV and Slicer packaged builds on Windows)
+* installation of OpenCV from binary package (discarded due to incompatibility of the compilers used for OpenCV and Slicer packaged builds on Windows)
-- reuse of the Anaconda (discarded due to the present lack of integration of anaconda (in progress), and the fact that pyopencv is not a standard package)
+* reuse of the Anaconda (discarded due to the present lack of integration of anaconda (in progress), and the fact that pyopencv is not a standard package)
-- superbuild of OpenCV within an extension providing user-level functionality (discarded since this would not allow the reuse of OpenCV libraries across extensions, and we see several potential users)
+* superbuild of OpenCV within an extension providing user-level functionality (discarded since this would not allow the reuse of OpenCV libraries across extensions, and we see several potential users)
 =Unresolved questions=