HPC/Applications/atk: Difference between revisions
< HPC | Applications
Jump to navigation
Jump to search
Line 24: | Line 24: | ||
To connect: | To connect: | ||
# Follow [[HPC/Network Access/PuTTY Configuration#Connecting | section Connecting]] to reach clogin. | # Follow [[HPC/Network Access/PuTTY Configuration#Connecting | section Connecting]] to reach clogin. | ||
# Start VNL or atkpython normally. | # Start VNL or atkpython normally on your machine. | ||
# [[HPC/Software/Modules/atk/License troubleshooting on Windows | License troubleshooting]] | # [[HPC/Software/Modules/atk/License troubleshooting on Windows | License troubleshooting]] |
Revision as of 08:17, August 29, 2012
Module conflicts
This package uses MPICH2 (which Intel-MPI provides) and hence clashes with VASP, which uses HPC/Applications/openmpi.
Co-existence is possible as follows:
module unload openmpi module load atk module load openmpi … module load vasp5 # … or other versions
Parallel jobs
- Local changes
- We use Intel-MPI instead of MPICH2, with the Hydra process manager instead of MPD. See the sample.job file for details:
$ATK_HOME/sample.job
Remote access from Windows
- ATK Installation
- Remote access to Carbon's ATK licenses require one of the following:
- Basic: PuTTY tunnel setup for clogin.
- Advanced: Remote Access and startup using Cygwin.
- License configuration
To connect:
- Follow section Connecting to reach clogin.
- Start VNL or atkpython normally on your machine.
- License troubleshooting