software:anaconda:farber

Differences

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

Link to this comparison view

Next revision
Previous revision
software:anaconda:farber [2020-02-03 18:11] – created anitasoftware:anaconda:farber [2020-11-02 11:54] (current) – [Recipes] anita
Line 24: Line 24:
 </code> </code>
  
 +See [[software:anaconda:farber#Recipes|Recipes]] for examples of building virtual environments for specific packages.
 ===== Virtual Environment ==== ===== Virtual Environment ====
  
-If you are going to follow the instructions for creating an Anaconda virtual environment on Farber 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 part of the message while building your virtual environment.+If you are going to follow the instructions for creating an Anaconda virtual environment on Farber 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 Python3also specify a path in your home directory not in the system path for Anaconda, and ignore the warnings to update ''conda'' while 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 ''qlogin'' to verify the new ''fenicsproject'' Anaconda environment is working properly.  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 ''qlogin'' to verify the new ''fenicsproject'' Anaconda environment is working properly. 
Line 89: Line 90:
 Your interactive job 3985323 has been successfully scheduled. Your interactive job 3985323 has been successfully scheduled.
 Establishing /opt/shared/univa/local/qlogin_ssh session to host n038 ... Establishing /opt/shared/univa/local/qlogin_ssh session to host n038 ...
 +[(it_css:traine)@n038 ~]$ vpkg_devrequire anaconda/5.2.0:python3
 +Adding package `anaconda/5.2.0:python3` to your environment
 [(it_css:traine)@n038 ~]$ source activate ~/fenicsproject [(it_css:traine)@n038 ~]$ source activate ~/fenicsproject
-(/home/1201/fenicsproject) [traine@r00n56 ~]$ python -c "import mshr" +(/home/1201/fenicsproject) [(it_css:traine)@n038 ~]$ python3 -c "import mshr" 
-(/home/1201/fenicsproject) [traine@r00n56 ~]$ source deactivate +(/home/1201/fenicsproject) [(it_css:traine)@n038 ~]$ source deactivate 
-[traine@r00n56 ~]$ exit+[(it_css:traine)@n038 ~]$ exit
 exit exit
-salloc: Relinquishing job allocation 5434421 +Connection to n038 closed. 
-[(it_css:traine)@login00 ~]$+/opt/shared/univa/local/qlogin_ssh exited with exit code 0 
 +[(it_css:traine)@farber ~]$
 </code> </code>
 +
 +===== 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]]
 +  * [[technical:recipes:emcee-in-virtualenv|Python Virtualenv: emcee and pyKLIP]]
 +  * [[technical:recipes:mpi4py-in-virtualenv|Python Virtual Environments with mpi4py]]
  • software/anaconda/farber.1580771477.txt.gz
  • Last modified: 2020-02-03 18:11
  • by anita