Theses installation instructions apply to the Linux64 version of Abaqus.
For running a simulation after the installation, please refer to the Abaqus usage page
- operational Abaqus
- Intel Fortran compiler compatible with your Abaqus version.
- DAMASK/CONFIG reflecting your system settings (i.e. your Abaqus version)
- system variables set (done by calling
Copy Abaqus environment file
- Linux: Copy DAMASK/installation/mods_Abaqus/abaqus_v6.env into either your home directory or the model directory.
For more details on the use of this file, please refer to the Abaqus manual.
The following modifications are done to the abaqus_v6.env
cae_no_parts_input_file=ON since DAMASK relies on unique element numbers in the input file
- Intel Fortran compiler found in $PATH is used
- added compiler switches
| prevent linking, only generate object files |
| generate position-independent code |
| put local variables on the stack |
| include path |
| use free-format Fortran 90 syntax |
| optimization level |
| use Fortran preprocessor on source code |
| build with OpenMP support |
| flush underflow to zero |
| assume no implicit types (e.g., i, j, k, l for integer) |
- dropped compiler switches
| suppress messages about use of non-standard Fortran |
| turn a compile-time bounds check into a warning |
| unofficial compiler switch, proposed by Simulia but highly dubious |
Compilation into a library
You can compile DAMASK into a library to be used with abaqus, it saves you from compiling the subroutine for each job.
In this case you do not have to specify a usersubroutine file, however if you still do, the compiled version will override that in the library.
- create a library directory, e.g. abqlib, in your prefered location
- build the library replacing your_prefered_location/abqlib with the correct path to the directory created in step 1.
abaqus make library=DAMASK_abaqus_std.f -dir your_prefered_location/abqlib
- in the Abaqus environment file abaqus_v6.env uncomment the line
after replacing your_prefered_location/abqlib with the correct path to the directory created in step 1.