Difference between revisions of "2013 Project Week:PythonModules"
From NAMIC Wiki
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2013.png|Projects List Image:ScarSeg_EM.png| Scar tissue identification. </gallery> ==Key Investigators=…') |
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/") |
||
| (5 intermediate revisions by one other user not shown) | |||
| Line 2: | Line 2: | ||
<gallery> | <gallery> | ||
Image:PW-SLC2013.png|[[2013_Winter_Project_Week#Projects|Projects List]] | Image:PW-SLC2013.png|[[2013_Winter_Project_Week#Projects|Projects List]] | ||
| − | |||
</gallery> | </gallery> | ||
==Key Investigators== | ==Key Investigators== | ||
| − | * | + | * Dave Welch, University of Iowa SINAPSE |
| − | * | + | * Hans Johnson, University of Iowa SINAPSE |
| − | * | + | * JC, UNC-Chapel Hill |
==Project Description== | ==Project Description== | ||
| Line 16: | Line 15: | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Objective</h3> | <h3>Objective</h3> | ||
| − | * | + | * Adding Python modules into the Slicer environment is currently cumbersome and difficult to do. With the growth of Python as a scientific research tool, Slicer should provide an easy mechanism for inclusion of Python modules on the fly. |
| − | * We will discuss | + | * We will discuss with lead Slicer developers how to best implement a user-friendly approach to improve Python importing. Our work will be tested and documented on the Slicer wiki. |
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
| − | * | + | * Discussions with JC, Steve, Andrey, and interested Python programmers |
| − | * | + | * Document best approaches |
| − | * | + | * Implement work in Slicer 4.3 |
</div> | </div> | ||
<div style="width: 27%; float: left; padding-right: 3%;"> | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
<h3>Progress</h3> | <h3>Progress</h3> | ||
| − | * | + | * JC has implemented and documented the steps required to install external Python packages into the Slicer environment |
| + | ** [[https://www.slicer.org/wiki/Documentation/Nightly/Developers/Python_scripting#Resources|Slicer Wiki documentation]] | ||
| + | ==== TODO ==== | ||
| + | * Add the Python function <tt>install_distributions</tt> into the <tt>slicer.util</tt> module | ||
| + | ** Rename to <tt>importExternalPythonModules()</tt> ? | ||
| + | * Add inclusion of distribute and pip installs to the CMake build (default: OFF) | ||
</div> | </div> | ||
</div> | </div> | ||
Latest revision as of 18:07, 10 July 2017
Home < 2013 Project Week:PythonModules
Key Investigators
- Dave Welch, University of Iowa SINAPSE
- Hans Johnson, University of Iowa SINAPSE
- JC, UNC-Chapel Hill
Project Description
Objective
- Adding Python modules into the Slicer environment is currently cumbersome and difficult to do. With the growth of Python as a scientific research tool, Slicer should provide an easy mechanism for inclusion of Python modules on the fly.
- We will discuss with lead Slicer developers how to best implement a user-friendly approach to improve Python importing. Our work will be tested and documented on the Slicer wiki.
Approach, Plan
- Discussions with JC, Steve, Andrey, and interested Python programmers
- Document best approaches
- Implement work in Slicer 4.3
Progress
- JC has implemented and documented the steps required to install external Python packages into the Slicer environment
TODO
- Add the Python function install_distributions into the slicer.util module
- Rename to importExternalPythonModules() ?
- Add inclusion of distribute and pip installs to the CMake build (default: OFF)
