Differences

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

--- technical:recipes:software-managment [2021-02-16 09:13] – [Builds] anita
+++ technical:recipes:software-managment [2024-01-04 16:48] (current) – [Builds] frey
@@ Line 40: / Line 40: @@
 </code>
 For shared installations made available to your entire workgroup:
+On DARWIN:
+<code bash>
+[(workgroup:user)@login00.darwin ~]$ LIBXC_BASEDIR="${WORKDIR_SW}/libxc"
+</code>
+On Caviness:
 <code bash>
-[(workgroup:user)@login00.darwin ~]$ LIBXC_BASEDIR="${WORKDIR}/sw/libxc"
+[(workgroup:user)@login00 ~]$ LIBXC_BASEDIR="${WORKDIR}/sw/libxc"
 </code>
@@ Line 63: / Line 70: @@
 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 ====
@@ Line 246: / Line 253: @@
 [user@login00.darwin ~]$ VALET_PKG_DIR=~/.valet ; VALET_PKG_DIR_MODE=0700
 </code>
-versus an installation made for an entire workgroup, which would store package definition files in ''$WORKDIR/sw/valet''
+versus an installation made for an entire workgroup would store VALET package definition files in
+<code bash>
+[user@login00.darwin ~]$ VALET_PKG_DIR="$WORKDIR_SW/valet"
+</code>
+on DARWIN and in
 <code bash>
 [user@login00.darwin ~]$ VALET_PKG_DIR="$WORKDIR/sw/valet" ; VALET_PKG_DIR_MODE=2770
 </code>
-Whichever scheme is in-use, ensure the directory exists:
+on Caviness.
+Whichever scheme is in-use, ensure the directory exists for personal use on Caviness and DARWIN, and entire workgroup on Caviness (entire workgroup on DARWIN is automatically created for each allocation so this is not necessary)
 <code bash>
 [user@login00.darwin ~]$ mkdir -p --mode=$VALET_PKG_DIR_MODE "$VALET_PKG_DIR"
@@ Line 448: / Line 461: @@
 </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''.
+===== 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]]