If you are doing a dnf install on hdf5 packages, you will notice errors like the one below
nothing provides libsz.so.2()(64bit) needed by hdf5-1.10.5-4.el8.x86_64
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)
To resolve the issue, you will need to install and enable PowerTools
Step 1: Install DNF plugins package
dnf install dnf-plugins-core
Step 2: Install EPEL
The reason is that some software from its source code requires some dependencies that are available in EPEL
dnf install epel-release
Step 3: Enable PowerTools repository on Rocky Linux 8
/var/spool/pbs/mom_priv/jobs/729107.hpc-mn1.SC: line 2: $'\r': command not found
/var/spool/pbs/mom_priv/jobs/729107.hpc-mn1.SC: line 5: $'\r': command not found
/var/spool/pbs/mom_priv/jobs/729107.hpc-mn1.SC: line 8: $'\r': command not found
/var/spool/pbs/mom_priv/jobs/729107.hpc-mn1.SC: line 11: $'\r': command not found
/var/spool/pbs/mom_priv/jobs/729107.hpc-mn1.SC: line 16: $'\r': command not found
/var/spool/pbs/mom_priv/jobs/729107.hpc-mn1.SC: line 19: $'\r': command not found
/var/spool/pbs/mom_priv/jobs/729107.hpc-mn1.SC: line 22: $'\r': command not found
These errors are usually due to Windows-style newline characters that can cause issues. Please use the commands
$ dos2unix yourfile
This will remove the Windows-style newline characters
Initialising a Repository in an Existing Directory
If you wish to have a project directory under version control with GIt, do the following
$ cd /home/user/my_project
$ git init
If you wish to add existing files into the version control
$ git add *.sh
$ git add LICENSE
$ git commit --m "Gekko Menu Help Application"
[master (root-commit) c98ae91] Gekko Menu Help Application
1 file changed, 73 insertions(+)
create mode 100755 mymenu.sh
You have an initial commit and tracked files. Hooray.
Checking the status of your Files
[user1@node1 menu]$ git status
# On branch master
nothing to commit, working directory clean
This means you have a clean working directory; in other words, none of your tracked files are modified.
Adding new files to your Git Directory
Let’s say you added a new file called check_license_abaqus.sh into the Project Directory, you will have something like
# On branch master
# Untracked files:
# (use "git add <file>..." to include in what will be committed)
#
# check_license_abaqus.sh
nothing added to commit but untracked files present (use "git add" to track)
To add files
[user1@node1 menu]$ git add check_license_abaqus.sh
[user1@node1 menu]$ git status
# On branch master
# Changes to be committed:
# (use "git reset HEAD <file>..." to unstage)
#
# new file: check_license_abaqus.sh
#
To remove file
[user1@node1 menu]$ git rm check_license_abaqus.sh -f
rm 'check_license_abaqus.sh'
[user1@node1 menu]$ git status
# On branch master
nothing to commit, working directory clean
To see log, you want to use the command
[user1@node1 menu]$ git log
commit xxxxxxxxx
Author: user1 <kmyemail_used_in_Github@hotmail.com>
Date: Sun Sep 25 23:50:33 2022 +0800
Gekko Menu Help Application
GitHub is the largest code-hosting platform in the world. It uses Git as version control and the repository is based on GitHub. Features such as Pull Requests, Project Boards and GitHub are central and found in one place.
On Linux, you can generate your SSH key using the email that you have created in your GitHub User Account
[user1@node1 ~]$ ssh-keygen -t rsa -C "myemail_used_in_Github@hotmail.com"
Generating public/private rsa key pair.
Enter file in which to save the key (/home/user1/.ssh/id_rsa):
/home/user1/.ssh/id_rsa already exists.
Overwrite (y/n)? y
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/user1/.ssh/id_rsa.
Your public key has been saved in /home/user1/.ssh/id_rsa.pub.
The key fingerprint is:
........
........
Adding the SSH Key to the ssh-agent
Although this is not mandatory, adding the SSH Key to the SSH Agent is a good practice that will keep the SSH Key safe. The SSH-agent is an SSH Key Manager that helps to keep the SSH key safe because it protects your SSH keys from being exported. The SSH Agent also saves you from having to type the passphrase you create. every time your SSH key is used.
Before you check, you want to check your ~/.ssh/config first
$ vim ~/.ssh/config
Host *
AddKeysToAgent yes
At the Terminal,
$ ssh-add ~/.ssh/id_rsa
Copy your SSH Public Key to the field. In your ~/.ssh/config, it should have a .pub extension like id_rsa.pub
Configuring Git
To intialise the Git. Do the following. You may want to take a look at
NVIDIA® HPC-X® is a comprehensive software package that includes Message Passing Interface (MPI), Symmetrical Hierarchical Memory (SHMEM) and Partitioned Global Address Space (PGAS) communications libraries, and various acceleration packages. For more information, do take a look at https://developer.nvidia.com/networking/hpc-x
What is CP2K?
CP2K is a quantum chemistry and solid state physics software package that can perform atomistic simulations of solid state, liquid, molecular, periodic, material, crystal, and biological systems. CP2K provides a general framework for different modeling methods such as DFT using the mixed Gaussian and plane waves approaches GPW and GAPW. Supported theory levels include DFTB, LDA, GGA, MP2, RPA, semi-empirical methods (AM1, PM3, PM6, RM1, MNDO, …), and classical force fields (AMBER, CHARMM, …). CP2K can do simulations of molecular dynamics, metadynamics, Monte Carlo, Ehrenfest dynamics, vibrational analysis, core level spectroscopy, energy minimisation, and transition state optimization using NEB or dimer method. (Detailed overview of features.). For more information, do take a look at https://www.cp2k.org/
Unpack hpcx and Optimised OpenMPI Libraries. For more information on installation, do take a look at Installing and Loading HPC-X
Extract hpcx.tbz into your current working directory.
% tar -xvf hpcx.tbz
% cd hpcx
% export HPCX_HOME=$PWD
% module use $HPCX_HOME/modulefiles
% module load hpcx
Use the CP2K Toolchain to Compile for the easiest
% cd cp2k
% cd /usr/local/software/cp2k/tools/toolchain
% ./install_cp2k_toolchain.sh --no-check-certificate --with-openmpi
Compiling the CP2K
.....
.....
==================== generating arch files ====================
arch files can be found in the /usr/local/software/cp2k/tools/toolchain/install/arch subdirectory
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local.ssmp
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local_static.ssmp
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local.sdbg
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local_coverage.sdbg
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local.psmp
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local.pdbg
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local_static.psmp
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local_warn.psmp
Wrote /usr/local/software/cp2k/tools/toolchain/install/arch/local_coverage.pdbg
========================== usage =========================
Done!
Now copy:
cp /usr/local/software/cp2k/tools/toolchain/install/arch/* to the cp2k/arch/ directory
To use the installed tools and libraries and cp2k version
compiled with it you will first need to execute at the prompt:
source /usr/local/software/cp2k/tools/toolchain/install/setup
To build CP2K you should change directory:
cd cp2k/
make -j 80 ARCH=local VERSION="ssmp sdbg psmp pdbg"
Do exactly on the ending instruction
% cp /usr/local/software/cp2k/tools/toolchain/install/arch/* /usr/local/cp2k/arch
% source /usr/local/software/cp2k/tools/toolchain/install/setup
% cd /usr/local/software/cp2k
% make -j 32 ARCH=local VERSION="ssmp sdbg psmp pdbg"
If you encounter an error during making like the one below, just do an install for liblsan
Load the Nvidia GPGPU SDK and compile. If you are using OneAPI Intel Compilers, you can use module use after compilation. It will not be covered in this write-up.
% module use /usr/local/intel/oneapi-2022/modulefiles
% module load nvhpc/22.5
% module load mkl/latest
% make veryclean
% make DEPS=1 -j
If during the make, you encounter the error
/usr/local/nvidia/hpc_sdk/Linux_x86_64/22.5/comm_libs/openmpi/openmpi-3.1.5/bin/.bin/mpif90: error while loading shared libraries: libatomic.so.1: cannot open shared object file: No such file or directory
During usage of ANSYS EM, you may encounter issues like the one below.
Fail to enable feature using current license setting. Note that pro, premium, enterprise licenses are available on your server. To use these licenses check the corresponding UI option. For more information, search "PPE" in the help documentation. Failover feature "HFSS SBR+Solve" is not available. Request name hfssbr_solve does not exist in the licensing pool. No such feature exists. Feature: hfssbr_solveLicensepath: 1055@kangkong.hpc.ntu.edu.sg: FlexNet Licensing error:-5,147
The resolution is to activate the correct product licensing which are not activated by default. See the Pix on how to activate the licensingsee less.