HPC/Applications/atk: Difference between revisions
< HPC | Applications
Jump to navigation
Jump to search
Line 25: | Line 25: | ||
# 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 on your machine. | # Start VNL or atkpython normally on your machine. | ||
# [[HPC/Software/Modules/atk/License troubleshooting on Windows | | # [[HPC/Software/Modules/atk/License troubleshooting on Windows | Troubleshoot ATK licensing]]. |
Revision as of 08:20, 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
- Install ATK
- You will need an ATK license to run VNL or atpkypthon. Choose one of the following to remotely access Carbon's licenses:
- Basic: Set up license forwarding using PuTTY.
- Advanced: Set up license forwarding using Cygwin.
- Configure ATK to use forwarded licenses.
To connect:
- Follow section Connecting to reach clogin.
- Start VNL or atkpython normally on your machine.
- Troubleshoot ATK licensing.