From d5eaf1650f1404ae284fc56c71882ef713019ac8 Mon Sep 17 00:00:00 2001 From: Joseph Hunkeler Date: Fri, 6 May 2016 16:54:17 -0400 Subject: Update FAQ: MKL 30-day trial fix --- source/faq.rst | 31 +++++++++++++++++++++++++++++++ 1 file changed, 31 insertions(+) (limited to 'source') diff --git a/source/faq.rst b/source/faq.rst index 827f0d9..c516df2 100644 --- a/source/faq.rst +++ b/source/faq.rst @@ -2,6 +2,7 @@ F.A.Q. ###### + After "``conda create ...``" why does "``source activate astroconda``" fail? ============================================================================ @@ -21,6 +22,36 @@ To clarify, it is impossible to execute ``source activate root``. Installing Ast Anaconda itself to be come unstable. In addition to this, removing packages from this environment is tedious and will likely break your Anaconda installation if you are not careful. *Reinstalling from scratch is the safest option.* +Why am I being prompted by NumPy/SciPy with a MKL 30-day trial warning? +======================================================================= + +The ``root`` environment of your Anaconda installation is severely outdated (``<=2.4.0``) and suffers from a crippling bug +introduced by the ``conda-3.19.x`` package. + +It is possible to verify the version of Anaconda you have by running: + +.. code-block:: sh + + $ conda info anaconda + +The only solution is to update your Anaconda installation to the latest release: + +.. code-block:: sh + + $ source deactivate + $ conda update conda + $ conda update anaconda + +Next, update the ``astroconda`` environment to realign your packages with the ``root`` environment: + +.. code-block:: sh + + $ conda update -n astroconda --all + $ source activate astroconda + +After doing this, the ``mkl`` 30-day trial warning will not be displayed while importing ``numpy``, ``scipy``, or any +other package requiring ``mkl``. + How does AstroConda differ from Ureka? ====================================== -- cgit