Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
| installation_guide [2025/07/22 13:43] – updated macOS peterk | installation_guide [2026/04/01 06:00] (current) – [Installation of a full version] doll | ||
|---|---|---|---|
| Line 21: | Line 21: | ||
| '' | '' | ||
| - | When your licence is valid for one specific computer only (e.g. licences of type node8, node32, and especially if you hold a trial licence), then it is necessary to determine and enter the sysid on your account page. Only after that, a valid token may be downloaded. | + | When your licence is valid for one specific computer only (e.g. licences of type node16, node32, and especially if you hold a trial licence), then it is necessary to determine and enter the sysid on your account page. Only after that, a valid token may be downloaded. This works on Linux or Mac. On Windows, a sysid cannot be determined, and thus the Molpro binary for Windows can only be used with a group (or site or service) licence. Problematic are also tools such as |
| + | WSL (Windows Subsystem for Linux) because the sysid may change after every reboot. | ||
| Other configuration options may also be specified in the molpro script file found in the bin directory of the install. | Other configuration options may also be specified in the molpro script file found in the bin directory of the install. | ||
| - | ==== Detailed installation of the trial version ==== | + | ==== Detailed installation of the free trial version ==== |
| - | If you hold a trial licence, then this corresponds to the installation of pre-built binaries as just described | + | If you hold a free trial licence, then this corresponds to the installation of pre-built binaries as just described |
| ([[installation_guide# | ([[installation_guide# | ||
| , for one specific | , for one specific | ||
| Line 57: | Line 58: | ||
| **Please give your username for accessing molpro** (enter the account name of your account)\\ | **Please give your username for accessing molpro** (enter the account name of your account)\\ | ||
| **Please give your password for accessing molpro** (enter the password of your account)\\ | **Please give your password for accessing molpro** (enter the password of your account)\\ | ||
| - | When things have worked well, you should get a message: | + | When things have worked well, you should get a message: |
| You may now try to run molpro: | You may now try to run molpro: | ||
| ==== Installation of a full version ==== | ==== Installation of a full version ==== | ||
| - | licences for single machines: the steps are the same as when installing the trial version | + | licences for single machines: the steps are the same as when installing the free trial version |
| - | group, site, service licences: it is not necessary to determine a sysid. The other steps are similar as when installing the trial version. | + | group, site, service licences: it is not necessary to determine a sysid. The other steps are similar as when installing the free trial version. |
| File permissions should be set in such a way that the code is only made available to users which are covered by the licence. | File permissions should be set in such a way that the code is only made available to users which are covered by the licence. | ||
| Line 79: | Line 80: | ||
| - The '' | - The '' | ||
| - Machine-ready basis-set, and other utilities and libraries. | - Machine-ready basis-set, and other utilities and libraries. | ||
| - | * **Tuning** The program can be tuned for production by running tuning inputs and by making manual changes to the environment. | ||
| * **Testing** A suite of self-checking test jobs is run to provide assurance that the code as built will run correctly. | * **Testing** A suite of self-checking test jobs is run to provide assurance that the code as built will run correctly. | ||
| * **Final Install** The program can be run directly from the source tree in which it is built, but it is usually recommended to run the procedure that installs the essential components in standard system directories. | * **Final Install** The program can be run directly from the source tree in which it is built, but it is usually recommended to run the procedure that installs the essential components in standard system directories. | ||
| Line 98: | Line 98: | ||
| - A large scratch file system containing a directory that users may write on. | - A large scratch file system containing a directory that users may write on. | ||
| - An MPI wrapped C++ compiler, eg. '' | - An MPI wrapped C++ compiler, eg. '' | ||
| + | - [[https:// | ||
| - The source code of Molpro. | - The source code of Molpro. | ||
| - | There are example Dockerfiles for {{: | + | There are example Dockerfiles for {{: |
| < | < | ||
| #!/bin/sh | #!/bin/sh | ||
| Line 108: | Line 109: | ||
| # prerequisite 2: install homebrew, starting from https:// | # prerequisite 2: install homebrew, starting from https:// | ||
| PREFIX=$HOME/ | PREFIX=$HOME/ | ||
| - | remove=1 # if not 1, the source/ | ||
| brew info open-mpi | egrep ' | brew info open-mpi | egrep ' | ||
| - | brew install doxygen eigen gcc lapack python3 mpich cmake coreutils wget | + | brew install doxygen eigen gcc lapack python3 mpich cmake coreutils wget make |
| brew link mpich | brew link mpich | ||
| + | export PATH=${HOMEBREW_PREFIX}/ | ||
| GA_VERSION=5.9.2 | GA_VERSION=5.9.2 | ||
| - | wget -O - https:// | + | wget -O - https:// |
| HDF5_VERSION=1.14.6 | HDF5_VERSION=1.14.6 | ||
| - | wget -O - https:// | + | wget -O - https:// |
| if [ x$1 = xbuild ]; then | if [ x$1 = xbuild ]; then | ||
| Line 136: | Line 137: | ||
| deploy_environment=molpro-build # change this to an existing environment in which you want molpro, if you like | deploy_environment=molpro-build # change this to an existing environment in which you want molpro, if you like | ||
| - | conda create -y -n ${build_environment} cxx-compiler c-compiler fortran-compiler mpich mkl-devel | + | source $(dirname $(dirname $CONDA_EXE))/ |
| + | conda create -y -n ${build_environment} cxx-compiler c-compiler fortran-compiler mpich eigen cmake git curl wget make | ||
| conda activate ${deploy_environment} && deploy_prefix=${CONDA_PREFIX} || exit 1 | conda activate ${deploy_environment} && deploy_prefix=${CONDA_PREFIX} || exit 1 | ||
| - | conda activate ${build_environment} | + | conda activate ${build_environment} |
| - | wget -O - https:// | + | if [ $(uname -m) != arm64 ]; then conda install -y mkl-devel; fi |
| - | cd ga-5.8.1 && ./configure --prefix=${CONDA_PREFIX} | + | |
| + | GA_VERSION=5.9.2 | ||
| + | wget -O - https:// | ||
| + | |||
| + | HDF5_VERSION=1.14.6 | ||
| + | wget -O - https:// | ||
| git clone git@github.com: | git clone git@github.com: | ||
| cd molpro | cd molpro | ||
| - | ./configure --prefix=${deploy_prefix} CXX=mpicxx && make -j20 && version=$(grep PACKAGE_VERSION build/ | + | ./configure --prefix=${deploy_prefix} CXX=mpicxx && make -j20 && version=$(grep PACKAGE_VERSION build/ |
| </ | </ | ||
| ==== Configuration ==== | ==== Configuration ==== | ||
| Line 190: | Line 198: | ||
| in the Molpro base directory. Most of the standard options for GNU //make// can be used safely; in particular, '' | in the Molpro base directory. Most of the standard options for GNU //make// can be used safely; in particular, '' | ||
| - | ==== Tuning ==== | + | ==== Adjusting the default environment for Molpro |
| - | + | ||
| - | Molpro can be tuned for a particular system by running the Molpro input file '' | + | |
| - | + | ||
| - | **Adjusting the default environment for Molpro** | + | |
| The default running options for Molpro are stored in the script '' | The default running options for Molpro are stored in the script '' | ||