Projects:Iowa Longitudinal PETCT Analysis using 3DSlicer - Revision history

Fedorov: /* Items under development */

2013-03-06T15:01:10Z

Items under development

Fedorov: /* Slicer-related infrastructure discussion issues */

2013-02-25T03:15:30Z

Slicer-related infrastructure discussion issues

Fedorov: /* Items under development */

2013-02-25T03:08:33Z

Items under development

Fedorov at 16:56, 21 February 2013

2013-02-21T16:56:48Z

Fedorov at 19:53, 20 February 2013

2013-02-20T19:53:40Z

Fedorov at 21:43, 7 November 2012

2012-11-07T21:43:39Z

Fedorov at 21:35, 7 November 2012

2012-11-07T21:35:55Z

Fedorov: Created page with '=Summary= =Participants= =Technical details= ==Use-case workflow== ==Items under development== ==Slicer-related infrastructure discussion issues== ==References=='

2012-11-07T21:35:46Z

Created page with '=Summary= =Participants= =Technical details= ==Use-case workflow== ==Items under development== ==Slicer-related infrastructure discussion issues== ==References=='

New page

=Summary=

=Participants=

=Technical details=

==Use-case workflow==

==Items under development==

==Slicer-related infrastructure discussion issues==

==References==

@@ Line 13: / Line 13: @@
 * there is a crash switching between Editor and Charts layout, only on linux (Andrey will test)
 * need to discuss how Markus' SUV calculation extension can be integrated with Paul's module; Steve: makes sense to package that CLI together with the Paul's module (Paul started working on this)
 Other feature requests:
 * use box-and-whiskers for charts (request from Ron; problem: max/mean are not included)

@@ Line 21: / Line 21: @@
 * should there be an infrastructure for extension/module-specific parameter settings, and an interface to keep them in Slicer settings file? Should these settings be accessibel from Slicer Settings dialog, or from a panel in the extension?
 * It is important for reproducibility purposes to be able to keep track of the parameters and initialization (e.g., fuducials) used for certain processing operation. Should we consider how to do this on the Slicer infrastructure level, or resolve on a per-case basis?
-* PET SUV CLI module improvements: output SUV volume, and use another module for statistics calculations?
+* does it make sense to do SUV correction on PET import, and store SUV volume together with the original data?
 =References=

@@ Line 9: / Line 9: @@
 ==Items under development==
 Issues raised by Reinhard and Marcus on Feb 19, 2013 call:
-* scene save/load is not working in LongPETCT
+* scene save/load is not working in LongPETCT (Paul is working on this)
-* would like to be able to segment on the whole image volume without having to specify the ROI
+* would like to be able to segment on the whole image volume without having to specify the ROI (Paul will look into adding this as an option)
-* there is a crash switching between Editor and Charts layout, only on linux
+* there is a crash switching between Editor and Charts layout, only on linux (Andrey will test)
-* need to discuss how Markus' SUV calculation extension can be integrated with Paul's module; Steve: makes sense to package that CLI together with the Paul's module
+* need to discuss how Markus' SUV calculation extension can be integrated with Paul's module; Steve: makes sense to package that CLI together with the Paul's module (Paul started working on this)
 Other feature requests:
-* use box-and-whiskers for charts (request from Ron)
+* use box-and-whiskers for charts (request from Ron; problem: max/mean are not included)
-* report ROI SUV statistics in the findings table
+* report ROI SUV statistics in the findings table (Paul will implement)
-* allow externally supplied label to be specified for the finding segmentation
+* allow externally supplied label to be specified for the finding segmentation (under consideration)
 ==Slicer-related infrastructure discussion issues==

@@ Line 13: / Line 13: @@
 * there is a crash switching between Editor and Charts layout, only on linux
 * need to discuss how Markus' SUV calculation extension can be integrated with Paul's module; Steve: makes sense to package that CLI together with the Paul's module
 ==Slicer-related infrastructure discussion issues==

← Older revision		Revision as of 19:53, 20 February 2013
Line 8:		Line 8:

	==Items under development==		==Items under development==
		+	Issues raised by Reinhard and Marcus on Feb 19, 2013 call:
		+	* scene save/load is not working in LongPETCT
		+	* would like to be able to segment on the whole image volume without having to specify the ROI
		+	* there is a crash switching between Editor and Charts layout, only on linux
		+	* need to discuss how Markus' SUV calculation extension can be integrated with Paul's module; Steve: makes sense to package that CLI together with the Paul's module

	==Slicer-related infrastructure discussion issues==		==Slicer-related infrastructure discussion issues==

← Older revision		Revision as of 21:43, 7 November 2012
Line 10:		Line 10:

	==Slicer-related infrastructure discussion issues==		==Slicer-related infrastructure discussion issues==
		+	* should there be an infrastructure for extension/module-specific parameter settings, and an interface to keep them in Slicer settings file? Should these settings be accessibel from Slicer Settings dialog, or from a panel in the extension?
		+	* It is important for reproducibility purposes to be able to keep track of the parameters and initialization (e.g., fuducials) used for certain processing operation. Should we consider how to do this on the Slicer infrastructure level, or resolve on a per-case basis?
		+	* PET SUV CLI module improvements: output SUV volume, and use another module for statistics calculations?

	=References=		=References=

← Older revision		Revision as of 21:35, 7 November 2012
Line 11:		Line 11:
	==Slicer-related infrastructure discussion issues==		==Slicer-related infrastructure discussion issues==

−	==References==	+	=References=