technical:recipes:software-managment

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
technical:recipes:software-managment [2021-04-28 14:05] – [VALET Setup] anitatechnical:recipes:software-managment [2024-01-04 16:48] (current) – [Builds] frey
Line 70: Line 70:
 Each of the compilers chosen in building //variants// of the 5.1.0 release will follow the same general procedure. Each of the compilers chosen in building //variants// of the 5.1.0 release will follow the same general procedure.
  
-<note>The notation '':'' (colon) in output examples throughout this document indicates lines of output displayed from the command entered.</note>+<note>The notation '':'' (colon) in output examples throughout this document indicates lines of output are displayed by the command entered but have been omitted from this documentation.</note>
  
 ==== System GCC ==== ==== System GCC ====
Line 461: Line 461:
 </code> </code>
 As mentioned at the start of this document, the ''$LIBXC_PREFIX'' can be particularly helpful when configuring an Autoconf or CMake build of software that depends on this version/variant of **libxc**.  The development context is the most common use of context in VALET that it can be shortened from ''vpkg_require --context=development'' to just ''vpkg_devrequire''. As mentioned at the start of this document, the ''$LIBXC_PREFIX'' can be particularly helpful when configuring an Autoconf or CMake build of software that depends on this version/variant of **libxc**.  The development context is the most common use of context in VALET that it can be shortened from ''vpkg_require --context=development'' to just ''vpkg_devrequire''.
 +
 +===== Recipes for Specific Software =====
 +
 +All recipes are provided based on a specific cluster, Caviness and/or DARWIN.  However each recipe may be used as a reference from one cluster to another by using the appropriate file system (directory structure) and VALET packages for the cluster you are trying to install the software.
 +
 +==== MCFOST ====
 +[[technical:recipes:mcfost|Building MCFOST on Caviness]]
 +
 +
 +==== Python ====
 +
 +  * [[technical:recipes:pyqt5-in-virtualenv|Building PyQt5 in a Python Virtual Environment]]
 +  * [[technical:recipes:jupyter-notebook|Jupyter Notebook 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]]
 +
 +==== WRF ====
 +
 +  * [[software:wrf:caviness|WRF on Caviness]]
 +  * [[software:wrf:darwin|WRF on DARWIN]]
 +
 +==== VASP ====
 +[[technical:recipes:vasp-6-darwin|Building VASP 6 on Caviness/DARWIN]]
 +
  • technical/recipes/software-managment.1619633154.txt.gz
  • Last modified: 2021-04-28 14:05
  • by anita