Developer Meetings/20150113 - Revision history

Unknown user: Text replacement - "slicerWiki/index.php" to "wiki"

2019-11-21T17:05:12Z

Text replacement - "slicerWiki/index.php" to "wiki"

Wangk at 20:15, 13 January 2015

2015-01-13T20:15:44Z

Wangk: /* To discuss */

2014-12-30T21:00:22Z

To discuss

Wangk at 20:59, 30 December 2014

2014-12-30T20:59:13Z

Nicole: Created page with '== To discuss == *'

2014-12-30T20:08:03Z

Created page with '== To discuss == *'

New page

== To discuss ==

*

@@ Line 12: / Line 12: @@
 * Discussed integrating multidimen data into slicer superbuild and agreed it is a natural step to do. Kevin to discuss with Andras to get final approval and then will start the integration.
 * Discussed PET SUV calculation work in Slicer community.
-** http://www.slicer.org/slicerWiki/index.php/Documentation/4.4/Extensions/LongitudinalPETCT
+** http://www.slicer.org/wiki/Documentation/4.4/Extensions/LongitudinalPETCT
-** http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/Modules/dPetBrainQuantification
+** http://wiki.slicer.org/wiki/Documentation/Nightly/Modules/dPetBrainQuantification
 * Discussed how to work around for extensions that are only built and tested on certain platform (such as windows).
 ** Developers should keep in mind to make their code cross-platform but can state that they can only support in certain platform.
 ** in extension CMakeLists.txt, check build platform and disable building for other unsupported platforms.

← Older revision		Revision as of 20:15, 13 January 2015
Line 6:		Line 6:
	* possibility to add multidimen data to slicer superbuild and ask people to migrate their modules to use it in stead of the multivolume module.		* possibility to add multidimen data to slicer superbuild and ask people to migrate their modules to use it in stead of the multivolume module.
	* a new PET SUV module and how best to display results (data probe mouse over showing calculation at each voxel vs returning a new volume with the calculation as the image data)		* a new PET SUV module and how best to display results (data probe mouse over showing calculation at each voxel vs returning a new volume with the calculation as the image data)
		+
		+	== Conclusion ==
		+
		+	* Discussed Dicom export - Kevin will talk to Csaba to continue the work.
		+	* Discussed integrating multidimen data into slicer superbuild and agreed it is a natural step to do. Kevin to discuss with Andras to get final approval and then will start the integration.
		+	* Discussed PET SUV calculation work in Slicer community.
		+	** http://www.slicer.org/slicerWiki/index.php/Documentation/4.4/Extensions/LongitudinalPETCT
		+	** http://wiki.slicer.org/slicerWiki/index.php/Documentation/Nightly/Modules/dPetBrainQuantification
		+	* Discussed how to work around for extensions that are only built and tested on certain platform (such as windows).
		+	** Developers should keep in mind to make their code cross-platform but can state that they can only support in certain platform.
		+	** in extension CMakeLists.txt, check build platform and disable building for other unsupported platforms.

@@ Line 1: / Line 1: @@
 == To discuss ==
 * DICOM export improvements
 ** possible improvements to deal with all types of objects versus just one and ignoring the rest, as well as having to pass information between plugins
 * possibility to add multidimen data to slicer superbuild and ask people to migrate their modules to use it in stead of the multivolume module.
 * a new PET SUV module and how best to display results (data probe mouse over showing calculation at each voxel vs returning a new volume with the calculation as the image data)

← Older revision		Revision as of 20:59, 30 December 2014
Line 1:		Line 1:
	== To discuss ==		== To discuss ==

−	*	+	* DICOM export improvements
		+	** possible improvements to deal with all types of objects versus just one and ignoring the rest, as well as having to pass information between plugins
		+	* possibility to add multidimen data to slicer superbuild and ask people to migrate their modules to use it in stead of the multivolume module.
		+	* a new PET SUV module and how best to display results (data probe mouse over showing calculation at each voxel vs returning a new volume with the calculation as the image data)