Difference between revisions of "2015 Winter Project Week Infrastructure Breakout"
From NAMIC Wiki
(Created page with '== Updating Teem release == * Hans has merged changes in Teem1.11.1 branch with his change and resolve a bunch of CMake issues * Results are in this [http://cdash.airwayinspector…') |
|||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
== Updating Teem release == | == Updating Teem release == | ||
| − | * Hans has merged changes in Teem1.11.1 branch with his change and | + | * Hans has merged the changes in Teem1.11.1 branch with his change and resolved a bunch of CMake issues [https://github.com/BRAINSia/teem/tree/20150107_Slicer git] |
* Results are in this [http://cdash.airwayinspector.org/index.php?project=Teem Dashboard] | * Results are in this [http://cdash.airwayinspector.org/index.php?project=Teem Dashboard] | ||
* Talk to Gordon to bring those changes into Teem trunk and make a new branch (Teem 1.11.2?) | * Talk to Gordon to bring those changes into Teem trunk and make a new branch (Teem 1.11.2?) | ||
== Python Modules and Python Slicer == | == Python Modules and Python Slicer == | ||
| − | * Can Slicer | + | * 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] | ||
| + | |||
| + | * 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 BreakoutUpdating 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
- Can Slicer use a python distribution like Anaconda instead of building its own python?
- 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
- Build Slicer with miniAnaconda
Extension and third party libraries
- Policy to use third party libraries like OpenCV with Extensions. Should they be part of Slicer main dependencies?
