ABAQUS CAE 2020

Activating license
C > SolidSQUAD_License_servers>install_or_update.bat
Deactivating license
C > SolidSQUAD_License_servers>uninstall.bat

ABAQUS CAE 2020

Activating license
C > SolidSQUAD_License_servers>install_or_update.bat
Deactivating license
C > SolidSQUAD_License_servers>uninstall.bat

ABAQUS CAE 2020

Activating license
C > SolidSQUAD_License_servers>install_or_update.bat
Deactivating license
C > SolidSQUAD_License_servers>uninstall.bat
---------------------------------------------------------------------------------------------------------------------
PROBLEM
Forum
LNK4210 error
https://community.intel.com/t5/Intel-Fortran-Compiler/Fortran-Compiler-for-Abaqus/m-p/
1240199#M153488

Newest forum
https://community.intel.com/t5/Intel-Fortran-Compiler/How-to-Use-Intel-s-Fortran-Compiler-
with-Abaqus/m-p/1359606#M160026
POSSIBLE SOLUTION
https://learn.microsoft.com/en-us/cpp/error-messages/tool-errors/linker-tools-warning-lnk4210?
view=msvc-170

https://simulation-blog.technia.com/simulation/free-fortran-compiler-on-windows-for-abaqus-
material-modeling

HIGHLIGHTED COMMENT
Another developer suggests:

I had trouble running Abaqus with a “user subroutine” that I had built using oneAPI (on
Windows in this case). The simulation would start and then abruptly end without any error
message.

The root cause was as follows. I had (incorrectly) used a Fortran “stop” statement in my Abaqus
user subroutine instead of the vendor-recommended XIT() procedure (I should have used “call
XIT()”).

In oneAPI versions of ifort, the “stop” statement is linking to a for_stop_quiet() procedure in the
runtime libs. Apparently, older compilers called for_stop() and it seems for_stop_quiet() is new
to oneAPI versions so the new procedure does not exist in older ifort runtime libs.

The problem is that recent versions of Abaqus are still distributed with older (pre-oneAPI)
versions of the ifort runtime which do not contain the needed for_stop_quiet() procedure. As a
result, if you compile your user subroutine with oneAPI but then do not make sure the oneAPI
runtime libs are first in the Abaqus path, the dll will try to link to the older ifort runtime that is
missing the needed for_stop_quiet() procedure so the code just aborts.

I believe the newest versions of Abaqus finally have a oneAPI version of the ifort runtime libs.

The forum user may be able to resolve their issue by eliminating any “stop” or “error stop”
statements and replacing with “call XIT()”. Alternatively, they could also make sure that the
oneAPI “setvars” is properly integrated into the Abaqus environment.
---------------------------------------------------------------------------------------------------------------------
MESH SENSITIVITY ANALYSIS

Our analysis:
1. The number of Mesh was focused on the corner

---------------------------------------------------------------------------------------------------------------------
The aim of our sensitivity analysis is the computation of relative condition numbers κi
describing the propagation of relative errors from measurements.
Source: Mesh refinement and numerical sensitivity analysis
---------------------------------------------------------------------------------------------------------------------

Source: Mesh Sensitivity assessment on 2D and 3D elastic finite element

---------------------------------------------------------------------------------------------------------------------