Differences

This shows you the differences between two versions of the page.

--- software:anaconda:caviness [2020-02-03 18:13] – anita
+++ software:anaconda:caviness [2021-01-27 10:21] – [Recipes] anita
@@ Line 12: / Line 12: @@
 </code>
+See [[software:anaconda:caviness#Recipes|Recipes]] for examples of building virtual environments for specific packages.
 ===== Virtual Environment ====
-If you are going to follow the instructions for creating an Anaconda virtual environment on Caviness consider using a slight modification to the documentation provided by each software package and use VALET to load the proper version of Anaconda for Python 2 or Python3 and also specify a path in your home directory not in the system path for Anaconda, and ignore the warnings to update ''conda'' as it is building your virtual environment.
+If you are going to follow the instructions for creating an Anaconda virtual environment on Caviness consider using a slight modification to the documentation provided by each software package and use VALET to load the proper version of Anaconda for Python 2 or Python 3, specify a path in your home (''$HOME'') or workgroup (''$WORKDIR'') directory not in the system path for Anaconda, and also ignore the warnings to update ''conda'' as it is building your virtual environment.
-See the example below which creates a virtual Anaconda environment based on Python3 for FEniCS called ''fenicsproject'' in the ''traine'' home directory and installs all the fenics packages and mshr. Once the environment is created, then a simple interactive test is done on a compute node via the ''devel'' partition to verify the new ''fenicsproject'' Anaconda environment is working properly.
+See the example below which creates a virtual Anaconda environment based on Python 3 for FEniCS called ''fenicsproject'' in the ''traine'' home directory and installs all the fenics packages and mshr. Once the environment is created, then a simple interactive test is done on a compute node via the ''devel'' partition to verify the new ''fenicsproject'' Anaconda environment is working properly.
 <code>
@@ Line 50: / Line 51: @@
-The following NEW packages will be INSTALLED:
+The following packages will be downloaded:
 ...
@@ Line 79: / Line 80: @@
 salloc: Waiting for resource configuration
 salloc: Nodes r00n56 are ready for job
+[traine@r00n56 ~]$ vpkg_devrequire anaconda/5.2.0:python3
+Adding package `anaconda/5.2.0:python3` to your environment
 [traine@r00n56 ~]$ source activate ~/fenicsproject
-(/home/1201/fenicsproject) [traine@r00n56 ~]$ python -c "import mshr"
+(/home/1201/fenicsproject) [traine@r00n56 ~]$ python3 -c "import mshr"
 (/home/1201/fenicsproject) [traine@r00n56 ~]$ source deactivate
 [traine@r00n56 ~]$ exit
@@ Line 88: / Line 91: @@
 </code>
-Using Anaconda's version of [[technical:recipes:pyqt5-in-virtualenv|Python virtualenv to build PyQt5]] by hand serves as a recipe for this specific installation, but can perhaps help others in solving similar installation dilemmas.
+===== Recipes ====
+Examples documented as recipes to be used for specific installations including using a ''workgroup'' directory as well as creating VALET packages for these environments and job scripts setup for batch runs, but can also perhaps help others in solving similar installation dilemmas.
+  * [[technical:recipes:pyqt5-in-virtualenv|Building PyQt5 in a Python Virtual Environment]]
+  * [[technical:recipes:keras-in-virtualenv|Keras Python Virtual Environment]]
+  * Gurobi Python Virtual Environments
+    * [[software:gurobi:caviness#serial-or-threaded-python-environment|Gurobi Python Threaded and Serial]]
+    * [[software:gurobi:caviness#mpi-python-environment|Gurobi Python MPI]]
+  * [[technical:recipes:emcee-in-virtualenv|Python Virtualenv: emcee and pyKLIP]]
+  * [[technical:recipes:mpi4py-in-virtualenv|Python Virtual Environments with mpi4py]]
+  * [[technical:recipes:tensorflow-in-virtualenv|TensorFlow Python Virtual Environment]]