Difference between revisions of "Abaqus Guide"
|Line 1:||Line 1:|
Abaqus is currently not usable on the cluster with our new SLURM scheduler. Before we can fix this, we are renegotiating our contract with 3ds / Abaqus and will remedy once when we are back in contract.
- BECAT Support 2015-08-17
- BECAT Support 2015-08-17
Revision as of 22:11, 7 September 2015
- 1 Introduction to Abaqus FEA
- 2 Loading Modules
- 3 Running Abaqus on LSF System
- 4 Notes
Introduction to Abaqus FEA
The Abaqus FEA (Dassault Systèmes 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 with LSF on Hornet. Currently, Abaqus 6.13, 6.12 and 6.11 are available on Hornet.
Loading Abaqus Modules
To use Abaqus 6.13 on Hornet you will need first load the Abaqus module using this command:
module load abaqus/6.13
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.13, at first you need to unload the Abaqus 6.11 module by using this command:
module unload abaqus/6.11
Then, load the Abaqus 6.13 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 6.13 and FORTRAN modulus to be loaded every time you log in, to do this, run:
module initadd abaqus/6.13 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 file.
Running Abaqus on LSF System
On Hornet Abaqus jobs are managed by LSF. To submit a job to Abaqus through LSF, transfer your model input file to Hornet and run this command:
abq6132 job=job-1 que=standard:fslocal
where “abq6132” is the command (case sensitivity) to invoke Abaqus FEA 6.13, “job-1” is the file name of your input file (job-1.inp) 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 que=standard:fslocal
Running Abaqus Analysis with User's Subroutine
If a user's subroutine is adopted in the Abaqus model, run the command with "user" option.
abq6132 job=job-1 user=code.f que=standard:fslocal
where ““code.f” is the file name of the user subroutine written in FORTRAN.
Running a Parallel Abaqus Analysis
If parallel computing is needed, run the command with "cpus" option.
abq6132 job=job-1 cpus=5 que=standard:fslocal
where “cpus=5” will request five CPUs to run the job. More CPUs will require more Abaqus license tokens to run.
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.
Terminating an Abaqus Analysis
If an analysis job needs to be terminated before completion, find the Job ID with this command.
which will list all the jobs are running. Then run this command to kill a specific job.
bkill (Job ID)
where “(Job ID)” is the ID number of the job you want to kill.
At this time, the Abaqus script written in C++ has not been tested.