2008 Winter Project Week:PythonSupport - Revision history

Lantiga: /* June 2007 Project Week */

2008-01-14T11:03:30Z

June 2007 Project Week

Lantiga at 21:24, 6 January 2008

2008-01-06T21:24:56Z

Lantiga at 21:19, 6 January 2008

2008-01-06T21:19:41Z

Lantiga at 11:16, 13 December 2007

2007-12-13T11:16:22Z

Lantiga at 09:53, 13 December 2007

2007-12-13T09:53:26Z

Lantiga: New page: {| |Return to [[2008_Winter_Project_Week ]] |valign="top"|Todo |} NOTOC ===Key Investigators...

2007-12-07T08:34:45Z

New page: {| |thumb|320px|Return to [[2008_Winter_Project_Week ]] |valign="top"|thumb|320px|Todo |} __NOTOC__ ===Key Investigators...

New page

{|
|[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2008_Winter_Project_Week]] ]]
|valign="top"|[[Image:Case24-coronal-tensors-edit.png |thumb|320px|Todo]]
|}

__NOTOC__
===Key Investigators===
* Mario Negri Institute: Luca Antiga
* UCSD: Bryan Smith

<div style="margin: 20px;">

<div style="width: 27%; float: left; padding-right: 3%;">

<h1>Objective</h1>
Todo.

</div>

<div style="width: 27%; float: left; padding-right: 3%;">

<h1>Approach, Plan </h1>
Todo.
</div>

<div style="width: 40%; float: left;">

<h1>Progress</h1>

====June 2007 Project Week====
Todo.

====Jan 2007 Project Half Week====
Todo.

</div>

<br style="clear: both;" />

</div>

← Older revision		Revision as of 11:03, 14 January 2008
Line 38:		Line 38:

	<h1>Progress</h1>		<h1>Progress</h1>
		+
		+	====January 2008 Project Week====
		+
		+	* Matplotlib with a Cairo backend is almost there
		+	* Python command line modules now work correctly (handling arguments multiple=true has been fixed)
		+	* A set of working Python command line modules has been committed
		+	* Scripted modules have been extended to Python, and a sample scripted module has been written
		+	* Meta-modules are now possible; the first meta-modules will be written soon

	====June 2007 Project Week====		====June 2007 Project Week====

@@ Line 18: / Line 18: @@
 * Python command line modules (advantages: easy to write, access to Python libraries, don't need a compiler to write new modules)
 * matplotlib and scipy Python modules (they provide a matlab-like processing environment for images directly within Slicer).
-* Python as Slicer's scripting language (for automating task and programmatically access modules - this is Dan's new baby!)
+* Python as Slicer's scripting language (for automating tasks, programmatically access modules - this is Dan's new baby! - enabling staged processing)
 </div>
@@ Line 28: / Line 28: @@
 * solve building issues, check stability on different platforms
 * threading issues: modifying the MRML scene from Python command line modules in a thread-safe way
-* calling modules from Python
+* stabilize calling modules from Python, write example on staged processing
 * provide a Python equivalent to ScriptedModules
 * define what aspects will end up in the next release
@@ Line 54: / Line 54: @@
 Later on, after the meeting
-* command line parsing has been completed (in a very simple way, without needing access to XML)
+* command line parsing has been completed
-* API has been simplified
+* Python scripting and Python modules have been made independent of Numpy
 </div>

@@ Line 26: / Line 26: @@
 <h1>Approach, Plan </h1>
 In the project week, we plan to
-* consolidate Python support in Slicer3 from a design point of view (eg. can we allow Python command line modules to modify the MRML scene in a thread-safe way? ) (can we provide a Python equivalent to ScriptedModules?)
+* solve building issues, check stability on different platforms
 * define what aspects will end up in the next release
-* solve issues (building issues, threading issues, etc)
+* propose a working set of Python command line modules (interact with Sonia's breakout session on Tuesday?) to be included in the next release
-* propose a way of making Python scripting and Python modules independent of Numpy (etc..) support (so one can have the former without the latter in case there are issues with the dependencies or one wants to keep Slicer leaner)
+* write documentation on how to write Python command line modules
 </div>

@@ Line 29: / Line 29: @@
 * define what aspects will end up in the next release
 * solve issues (building issues, threading issues, etc)
 * propose a working set of Python command line modules (interact with Sonia's breakout session on Tuesday?) to be included in the next release.
 </div>

@@ Line 1: / Line 1: @@
 {|
 |[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2008_Winter_Project_Week]] ]]
-|valign="top"|[[Image:Case24-coronal-tensors-edit.png |thumb|320px|Todo]]
+|[[Image:Python-logo.png |thumb|320px|[http://www.python.org]]]
 |}
@@ Line 14: / Line 15: @@
 <h1>Objective</h1>
-Todo.
+Python has a great potential in Slicer3. Its uses span:
 </div>
@@ Line 21: / Line 25: @@
 <h1>Approach, Plan </h1>
-Todo.
+In the project week, we plan to
 </div>
@@ Line 29: / Line 37: @@
 ====June 2007 Project Week====
-Todo.
+These are the results of the MIT project week (largely Dan's work)
-====Jan 2007 Project Half Week====
+Later on, after the meeting
-Todo.
+* command line parsing has been completed (in a very simple way, without needing access to XML)
 </div>