Difference between revisions of "2015 Winter Project Week Infrastructure Breakout"

From NAMIC Wiki
Jump to: navigation, search
 
Line 7: Line 7:
 
* Can Slicer use a python distribution like [https://store.continuum.io/cshop/anaconda/ Anaconda] instead of building its own python?
 
* Can Slicer use a python distribution like [https://store.continuum.io/cshop/anaconda/ Anaconda] instead of building its own python?
 
** [http://docs.continuum.io/anaconda/pkg-docs.html Packages supported by Anaconda]
 
** [http://docs.continuum.io/anaconda/pkg-docs.html Packages supported by Anaconda]
 +
 +
* Discussion
 +
** We agree that Anaconda is a viable long term solution . Need to test this and package slicer
 +
 +
* Roadmap
 +
** Build Slicer with miniAnaconda
 +
*** Set variables in [https://github.com/Slicer/Slicer/blob/f877587c83a7648a442fea17b8f282932bf6b907/SuperBuild/External_python.cmake#L127-L145 External_python] to point to your Anaconda install.
 +
*** Install numpy, scipy, pygithub… (get from build)
 +
*** Build with VS13, OSX clang
 +
** Create packages
 +
*** make package
 +
*** Look at install portion of Slicer python to bring anaconda (ExternalPython.cmake)
 +
*** Test if conda works on the package version of python
  
 
== Extension and third party libraries ==
 
== Extension and third party libraries ==
 
* Policy to use third party libraries like OpenCV with Extensions. Should they be part of Slicer main dependencies?
 
* Policy to use third party libraries like OpenCV with Extensions. Should they be part of Slicer main dependencies?

Latest revision as of 00:54, 8 January 2015

Home < 2015 Winter Project Week Infrastructure Breakout

Updating Teem release

  • Hans has merged the changes in Teem1.11.1 branch with his change and resolved a bunch of CMake issues git
  • Results are in this Dashboard
  • Talk to Gordon to bring those changes into Teem trunk and make a new branch (Teem 1.11.2?)

Python Modules and Python Slicer

  • Discussion
    • We agree that Anaconda is a viable long term solution . Need to test this and package slicer
  • Roadmap
    • Build Slicer with miniAnaconda
      • Set variables in External_python to point to your Anaconda install.
      • Install numpy, scipy, pygithub… (get from build)
      • Build with VS13, OSX clang
    • Create packages
      • make package
      • Look at install portion of Slicer python to bring anaconda (ExternalPython.cmake)
      • Test if conda works on the package version of python

Extension and third party libraries

  • Policy to use third party libraries like OpenCV with Extensions. Should they be part of Slicer main dependencies?
Retrieved from "https://www.na-mic.org/w/index.php?title=2015_Winter_Project_Week_Infrastructure_Breakout&oldid=88440"