| Both sides previous revision Previous revision Next revision | Previous revision |
| software:software [2019-09-11 07:51] – [Availability] anita | software:software [2024-03-27 09:13] (current) – mkyle |
|---|
| Each cluster has a unique complement of development tools, libraries, and applications. Documentation for all software is organized in alphabetical order on the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> | Each cluster has a unique complement of development tools, libraries, and applications. Documentation for all software is organized in alphabetical order on the <html><span style="color:#ffffff;background-color:#2fa4e7;padding:3px 7px !important;border-radius:4px;">sidebar</span></html> |
| |
| A list of installed software that IT builds and maintains for each cluster can be found by logging into the cluster (e.g. [[abstract:caviness:system_access:system_access#logging-on-to-caviness|Caviness]] or [[abstract:farber:system_access:system_access#logging-on-to-farber|Farber]]) and using the VALET command ''vpkg_list''. | A list of installed software that IT builds and maintains for each cluster can be found by logging into the cluster (e.g. [[abstract:caviness:system_access:system_access#logging-on-to-caviness|Caviness]] or [[abstract:darwin:system_access:system_access#logging-on-to-darwin|DARWIN]]) and using the VALET command ''vpkg_list''. |
| |
| Review the [[http://www.nvidia.com/content/PDF/gpu-accelerated-applications.pdf|nVidia'a GPU-Accelerated Applications list]] for applications optimized to work with GPUs. These applications would be able to take advantage of nodes equipped with nVidia Tesla K20X coprocessors. | Review the [[http://www.nvidia.com/content/PDF/gpu-accelerated-applications.pdf|nVidia'a GPU-Accelerated Applications list]] for applications optimized to work with GPUs. These applications would be able to take advantage of nodes equipped with nVidia Tesla K20X coprocessors. |
| ===== VALET commands ===== | ===== VALET commands ===== |
| |
| The following table provides a brief summary of the most often-used VALET commands. Additional information is available in the [[:software:valet:valet|VALET software documentation]]. These commands are available in login shells and batch scripts (since they are run as login shells). | The UD-developed //VALET// system facilitates your use of compilers, libraries, programming tools and application software. It provides a uniform mechanism for setting up a package's required UNIX environment. VALET is a recursive acronym for **//V//**//ALET //**//A//**//utomates //**//L//**//inux //**//E//**//nvironment //**//T//**//asks//. It provides functionality similar to the **Modules** package used at other HPC sites. |
| |
| ^Command ^Description ^ | VALET commands set the basic environment for software. This may include the ''PATH'', ''MANPATH'', ''INFOPATH'', ''LDPATH'', ''LIBPATH'' and ''LD_LIBRARY_PATH'' environment variables, compiler flags, software directory locations, and license paths. This reduces the need for you to set them or update them yourself when changes are made to system and application software. For example, you might find several versions for a single package name, such as Mathematica/8 and Mathematica/8.0.4. You can even apply VALET commands to packages that you install or alter its actions by customizing VALET's configuration files. |
| |''vpkg_list''|List all available //packages// by their <<package-id>>| | |
| |''vpkg_versions'' <<package-id>>|List the versions/variants of a specific package by their <<version-id>>| | |
| |''vpkg_require'' <<versioned-package-id>>|Attempt to configure the environment to use the given software| | |
| |''vpkg_rollback'' <<number or all>>|Roll back a number of package additions, use all for every package| | |
| |
| A <<versioned-package-id>> is the combination of a package identifier (found using the ''vpkg_list'' command) with a version/variant identifier (via the ''vpkg_versions'' command). The two pieces are joined using a forward slash (/). For example, the commercial software "Matlab" has a <<package-id>> of ''matlab'' and the 2012 release has a <<version-id>> of ''r2012a'', producing the <<versioned-package-id>> ''matlab/r2012a''. | The following table provides a brief summary of the most often-used VALET commands. Additional information is available by typing **man valet** for instructions or see the [[:software:valet:valet|VALET software documentation]] for complete details. These commands are available in login shells and batch scripts (since they are run as login shells). |
| |
| <note>In the context of a <<versioned-package-id>>, a blank <<version-id>> implies the default version of the package. If the 2012 release of Matlab were the default, then using ''matlab'' (or ''matlab/default'') as the <<versioned-package-id>> would imply ''matlab/r2012a''.</note> | ^ Command ^ Function ^ |
| | | ''vpkg_help'' | VALET help. | |
| | | ''vpkg_list'' | List the packages that have VALET configuration files. | |
| | | ''vpkg_versions ''<<//package-id//>> | List versions available for a single package. | |
| | | ''vpkg_info ''<<//package-id//>> | Show information for a single package (or package version). | |
| | | ''vpkg_require ''<<//versioned-package-id//>> | Configure environment for one or more VALET packages. | |
| | | ''vpkg_devrequire ''<<//versioned-package-id//>> | Configure environment for one or more VALET packages including software development variables such as ''CPPFLAGS'' and ''LDFLAGS''. | |
| | | ''vpkg_rollback ''<<//# or all//>> | Each time VALET changes the environment, it makes a snapshot of your environment to which it can return.\\ ''vpkg_rollback'' attempts to restore the UNIX environment to its previous state. You can specify a number (''#'') to revert one or more prior changes to the environment or ''all'' to remove all changes. | |
| | | ''vpkg_history'' | List the versioned packages that have been added to the environment. | |
| | | ''man valet'' | Complete documentation of VALET commands. | |
| |
| VALET environment changes apply to the shell in which the ''vpkg_require'' command is issued; the changes do not "stick" after exiting that shell (by logging-out, for example). Thus, one way to discard changes affected by a ''vpkg_require'' command is to just exit the shell. The ''vpkg_rollback'' command is a more graceful alternative and iteratively discards the changes produced by prior ''vpkg_require'' commands issued in the shell. To undo all changes, ''vpkg_require all'' can be used. | A <<//versioned-package-id//>> is the combination of a package identifier (found using the ''vpkg_list'' command) with a version/variant identifier (via the ''vpkg_versions'' command). The two pieces are joined using a forward slash (/). For example, the commercial software "Matlab" has a <<//package-id//>> of ''matlab'' and the 2012 release has a <<//version-id//>> of ''r2012a'', producing the <<//versioned-package-id//>> ''matlab/r2012a''. |
| | |
| | <note>In the context of a <<//versioned-package-id//>>, a blank <<//version-id//>> implies the default version of the package (marked with an asterisk ''*''). If the 2012 release of Matlab were the default, then using ''matlab'' (or ''matlab/default'') as the <<//versioned-package-id//>> would imply ''matlab/r2012a''.</note> |
| | |
| | VALET environment changes apply to the shell in which the ''vpkg_require'' command is issued; the changes do not "stick" after exiting that shell (by logging-out, for example). Thus, one way to discard changes affected by a ''vpkg_require'' command is to just exit the shell. The ''vpkg_rollback'' command is a more graceful alternative and iteratively discards the changes produced by prior ''vpkg_require'' commands issued in the shell. To undo all changes, ''vpkg_rollback all'' can be used. |
| |
| A script contains commands to be executed in a shell. | A script contains commands to be executed in a shell. |