Difference between revisions of "Abaqus Guide"
| Line 5: | Line 5: | ||
===Loading Abaqus Modules=== | ===Loading Abaqus Modules=== | ||
To use Abaqus 6.12 on Hornet you will need first load the Abaqus module using this command: | To use Abaqus 6.12 on Hornet you will need first load the Abaqus module using this command: | ||
| − | + | '''module load abaqus/6.12''' | |
To load Abaqus 6.11, use this command instead: | To load Abaqus 6.11, use this command instead: | ||
'''module load abaqus/6.11''' | '''module load abaqus/6.11''' | ||
Only one Abaqus version could be loaded in one session. For example, if Abaqus 6.11 has been loaded and you want to run Abaqus 6.12 command, at first you need to unload the Abaqus 6.11 module using this command: | Only one Abaqus version could be loaded in one session. For example, if Abaqus 6.11 has been loaded and you want to run Abaqus 6.12 command, at first you need to unload the Abaqus 6.11 module using this command: | ||
| − | + | '''module unload abaqus/6.11''' | |
Then, load the Abaqus 6.12 module. | Then, load the Abaqus 6.12 module. | ||
===Loading FORTRAN Module=== | ===Loading FORTRAN Module=== | ||
If you need to use FORTRAN subroutine with your simulation, load FORTRAN compiler as well: | If you need to use FORTRAN subroutine with your simulation, load FORTRAN compiler as well: | ||
| − | + | '''module load intelics/2012.0.032''' | |
===Loading Modules on Log-in=== | ===Loading Modules on Log-in=== | ||
If you wish Abaqus and FORTRAN modulus to be loaded every time you log in, To do this run: | If you wish Abaqus and FORTRAN modulus to be loaded every time you log in, To do this run: | ||
| − | + | '''module initadd abaqus/6.12''' | |
| − | + | '''module initadd intelics/2012.0.032''' | |
If you decide that you no longer want a specific module to be loaded every time, simply remove that line from your ~/.bashrc. | If you decide that you no longer want a specific module to be loaded every time, simply remove that line from your ~/.bashrc. | ||
===Running Abaqus with LSF=== | ===Running Abaqus with LSF=== | ||
On Hornet Abaqus jobs are managed by LSF. To submit a job to Abaqus through LSF, run this command: | On Hornet Abaqus jobs are managed by LSF. To submit a job to Abaqus through LSF, run this command: | ||
| − | + | ''' abq6122 job=job-1 user=code.f cpus=2 que=standard:fslocal''' | |
where “abq6122” is the command to invoke Abaqus FEA 6.12, “job-1” is the file name of your input file (job-1.inp), “code.f” is the file name of the user subroutine, “cpus=2” will request two CPUs to run current job and “que=standard:fslocal” will allow Abaqus to run the simulation in a local file system. The simulation will most likely run on another compute node. The simulation result files will be copied back upon completion. To run ABAQUS in a shared file system, “que=strandard:fsshared” should be used instead. | where “abq6122” is the command to invoke Abaqus FEA 6.12, “job-1” is the file name of your input file (job-1.inp), “code.f” is the file name of the user subroutine, “cpus=2” will request two CPUs to run current job and “que=standard:fslocal” will allow Abaqus to run the simulation in a local file system. The simulation will most likely run on another compute node. The simulation result files will be copied back upon completion. To run ABAQUS in a shared file system, “que=strandard:fsshared” should be used instead. | ||
If Abaqus 6.11 was loaded and you want to run Abaqus 6.11 through LSF, use "abq6111" instead. | If Abaqus 6.11 was loaded and you want to run Abaqus 6.11 through LSF, use "abq6111" instead. | ||
| − | + | ''' abq6111 job=job-1 user=code.f cpus=2 que=standard:fslocal''' | |
===Checking the Status of Abaqus Jobs=== | ===Checking the Status of Abaqus Jobs=== | ||
If you want to check the status of running Abaqus jobs, run this command if you are using a shared file system: | If you want to check the status of running Abaqus jobs, run this command if you are using a shared file system: | ||
| − | + | '''tail -f job-1.sta''' | |
where "job-1.sta" is the name of the status file. If you are running your job in a local file system, then you have to change the directory the specific folder and specific node to check the status of your job. | where "job-1.sta" is the name of the status file. If you are running your job in a local file system, then you have to change the directory the specific folder and specific node to check the status of your job. | ||
Revision as of 14:10, 1 May 2013
Contents
Abaqus FEA
The Abaqus FEA (Simulia, Providence, RI) is a software suite for finite element analysis and computer-aided engineering, originally released in 1978. Abaqus FEA has been installed and configured on the School of Engineering HPC (code name: Hornet). Currently, Abaqus 6.12 and 6.11 are both available on Hornet.
Loading Abaqus Modules
To use Abaqus 6.12 on Hornet you will need first load the Abaqus module using this command: module load abaqus/6.12 To load Abaqus 6.11, use this command instead:
module load abaqus/6.11
Only one Abaqus version could be loaded in one session. For example, if Abaqus 6.11 has been loaded and you want to run Abaqus 6.12 command, at first you need to unload the Abaqus 6.11 module using this command: module unload abaqus/6.11 Then, load the Abaqus 6.12 module.
Loading FORTRAN Module
If you need to use FORTRAN subroutine with your simulation, load FORTRAN compiler as well: module load intelics/2012.0.032
Loading Modules on Log-in
If you wish Abaqus and FORTRAN modulus to be loaded every time you log in, To do this run: module initadd abaqus/6.12 module initadd intelics/2012.0.032 If you decide that you no longer want a specific module to be loaded every time, simply remove that line from your ~/.bashrc.
Running Abaqus with LSF
On Hornet Abaqus jobs are managed by LSF. To submit a job to Abaqus through LSF, run this command: abq6122 job=job-1 user=code.f cpus=2 que=standard:fslocal
where “abq6122” is the command to invoke Abaqus FEA 6.12, “job-1” is the file name of your input file (job-1.inp), “code.f” is the file name of the user subroutine, “cpus=2” will request two CPUs to run current job and “que=standard:fslocal” will allow Abaqus to run the simulation in a local file system. The simulation will most likely run on another compute node. The simulation result files will be copied back upon completion. To run ABAQUS in a shared file system, “que=strandard:fsshared” should be used instead.
If Abaqus 6.11 was loaded and you want to run Abaqus 6.11 through LSF, use "abq6111" instead. abq6111 job=job-1 user=code.f cpus=2 que=standard:fslocal
Checking the Status of Abaqus Jobs
If you want to check the status of running Abaqus jobs, run this command if you are using a shared file system: tail -f job-1.sta where "job-1.sta" is the name of the status file. If you are running your job in a local file system, then you have to change the directory the specific folder and specific node to check the status of your job.
Normally when the simulation is finished, the HPC will send you an email showing the simulation is completed successfully or exited with error.
Note
At this time, the Abaqus script written in C++ has not been tested.
