Documentation/Labs/SlicerCondaIntegration - Revision history

JChris.FillionR: /* Update 2015-10-10 */

2016-03-22T22:19:30Z

Update 2015-10-10

2016-01-22T19:09:16Z

Added survey for Anaconda packages

2015-12-08T16:41:00Z

Update 2015-10-10

2015-12-08T16:17:02Z

Update 2015-10-10

2015-12-08T16:16:53Z

Update 2015-10-10

2015-12-08T16:15:10Z

2015-09-22T22:46:09Z

2015-09-22T22:44:06Z

Next steps

2015-09-22T22:43:42Z

Next steps

2015-09-22T22:43:30Z

Proposed tasks

@@ Line 14: / Line 14: @@
 It turns out that there are a lot of issues with this approach.
-See https://docs.google.com/spreadsheets/d/1aQSEr5JjeNVqiaWNB0ZPLWJqo32E-yAfynXJawYGwY8/edit?usp=sharing
+See https://goo.gl/VNy7yV
 Next step: We suggest to continue with the initial approach where Slicer is built against miniconda Python libraries.

← Older revision		Revision as of 19:09, 22 January 2016
Line 2:		Line 2:

	Instead of attempting to use the whole Anaconda package, our approach will be to use Miniconda, a reduced version of Anaconda, and (1) install a pre-defined set of packages and (2) provide a way to easily install new ones.		Instead of attempting to use the whole Anaconda package, our approach will be to use Miniconda, a reduced version of Anaconda, and (1) install a pre-defined set of packages and (2) provide a way to easily install new ones.
		+
		+	== Update 2016-01-22 (Jorge) ==
		+	After a follow up with JC about this topic, and due to the apparent complexity of this task, it has been decided to make a small survey to have a better idea of which would be the most needed packages for the community from those ones available in Anaconda.
		+
		+	The link to indicate your preferences is: https://docs.google.com/spreadsheets/d/1j4iugjs0GkHEn1elUbceMW2KJ21FM-QrYoFtZ4P9yOc/edit?usp=sharing

	== Update 2015-10-10 ==		== Update 2015-10-10 ==

@@ Line 9: / Line 9: @@
 It turns out that there are a lot of issues with this approach.
-See https://docs.google.com/spreadsheets/d/1aQSEr5JjeNVqiaWNB0ZPLWJqo32E-yAfynXJawYGwY8/edit
+See https://docs.google.com/spreadsheets/d/1aQSEr5JjeNVqiaWNB0ZPLWJqo32E-yAfynXJawYGwY8/edit?usp=sharing
 Next step: We suggest to continue with the initial approach where Slicer is built against miniconda Python libraries.

@@ Line 11: / Line 11: @@
 See https://docs.google.com/spreadsheets/d/1aQSEr5JjeNVqiaWNB0ZPLWJqo32E-yAfynXJawYGwY8/edit
-Next step: We suggested to continue with the initial approach where Slicer is built against miniconda Python libraries.
+Next step: We suggest to continue with the initial approach where Slicer is built against miniconda Python libraries.
 == Virtual Hackfest: August 24, 9am ==

@@ Line 5: / Line 5: @@
 == Update 2015-10-10 ==
-We did few experiments where we copied the anaconda numpy and SciPy packages into a Slicer build tree and run the associated tests. The link below summarizes the results.
+We (Kitware) did few experiments where we copied the anaconda numpy and SciPy packages into a Slicer build tree and run the associated tests. The link below summarizes the results.
-It turns out that there are a lot of issues with this approach. I would then suggest we continue with our initial approach where Slicer is built against miniconda Python libraries.
+It turns out that there are a lot of issues with this approach.
 See https://docs.google.com/spreadsheets/d/1aQSEr5JjeNVqiaWNB0ZPLWJqo32E-yAfynXJawYGwY8/edit
 == Virtual Hackfest: August 24, 9am ==

← Older revision		Revision as of 16:15, 8 December 2015
Line 2:		Line 2:

	Instead of attempting to use the whole Anaconda package, our approach will be to use Miniconda, a reduced version of Anaconda, and (1) install a pre-defined set of packages and (2) provide a way to easily install new ones.		Instead of attempting to use the whole Anaconda package, our approach will be to use Miniconda, a reduced version of Anaconda, and (1) install a pre-defined set of packages and (2) provide a way to easily install new ones.
		+
		+	== Update 2015-10-10 ==
		+
		+	We did few experiments where we copied the anaconda numpy and SciPy packages into a Slicer build tree and run the associated tests. The link below summarizes the results.
		+
		+	It turns out that there are a lot of issues with this approach. I would then suggest we continue with our initial approach where Slicer is built against miniconda Python libraries.
		+
		+	See https://docs.google.com/spreadsheets/d/1aQSEr5JjeNVqiaWNB0ZPLWJqo32E-yAfynXJawYGwY8/edit
		+

	== Virtual Hackfest: August 24, 9am ==		== Virtual Hackfest: August 24, 9am ==

← Older revision		Revision as of 22:46, 22 September 2015
Line 203:		Line 203:

	Although the code in https://github.com/jonieva/Slicer/tree/Conda should work with Windows too (using the setting Slicer_USE_CONDA_python=ON), it has not been tested at the moment.		Although the code in https://github.com/jonieva/Slicer/tree/Conda should work with Windows too (using the setting Slicer_USE_CONDA_python=ON), it has not been tested at the moment.
		+
		+
		+	==Compile Slicer and python 2.7.10 + drop in conda binary packages ==
		+
		+	=== Initial experiments ===
		+
		+	TBD

	== Next steps ==		== Next steps ==

@@ Line 206: / Line 206: @@
 == Next steps ==
 Copied from the conclusion of the [[Developer_Meetings/20150324#Conclusions|Developer hangout of March 24th 2015]]
@@ Line 217: / Line 218: @@
 </s>
 {{done}} See https://github.com/jcfr/Slicer/tree/slicer-miniconda

@@ Line 216: / Line 216: @@
 ** For now, let's consider only the case OpenSSL disabled.
 </s>
-Done - See https://github.com/jcfr/Slicer/tree/slicer-miniconda
+{{done}} See https://github.com/jcfr/Slicer/tree/slicer-miniconda

@@ Line 12: / Line 12: @@
 === Proposed tasks ===
-* Review and consolidate contributions of Jorge and Adam
+* <s>Review and consolidate contributions of Jorge and Adam</s> {{done}}
-* Implement miniconda external project files as outlined [[#Next_steps|below]]
+* <s>Implement miniconda external project files as outlined [[#Next_steps|below]]</s> {{done}}
 * Create a Slicer module providing:
 ** (1) scripted interface to install additional conda package