I am using SANISAND to simulate a triaxial compression test under monotonic loading. But every time my simulations break and give the same message “Abaqus/Implicit Packager exited with an error – Please see the status file for possible error messages if the file exists.” There is no message file to look for the specific problem.
Is it has to do anything with the new Intel one API software? Recently, I have been upgraded to ABAQUS 2019. But previously, when tried with the Abaqus 2014 version, the program ran successfully. I am not sure whether it has anything to do with the software configuration.
Can anyone please suggest a solution? I really appreciate any help you can provide.
Related Articles
-
Hypo-sand UMAT problem
Dear community I have 4 Question in implementation of Hypo-sand Umat in ABAQUS could someone kindly explain? 1. I checked the Umat file from (https://soilmodels.com/download/plaxis-umat-hypoplas-zip/) and i understand this subroutine […] -
Triaxial compression test using Mohr-Coulomb model in Abaqus
Hello, everyone. I have encountered an issue during the simulation of triaxial compression of rocks using the perfectly elasto-plastic Mohr-Coulomb model in Abaqus. In my simulation, the stress-strain curve consists […] -
CONSTUTUTIVE MODELLING
Can SANISAND version given in soil model work well for cyclic simple shear test ? -
Shear Stiffness Calculation for Hypoplastic Model
Hi David, I have reproduced some single elements test on ABAQUS using the UMAT to compare with Triax Hypoplasticity. So far, my stiffness curve (q vs ea) and my stress […] -
Oedometric Test Soil Test Plaxis
Hi community, I am trying to simulate a oedometer test in soil test of plaxis but i am not reaching the expected results. In the Bentley manual available at the […] -
How to implement this Hypoplastic Interface Model into ABAQUS combined with the existing hypoplastic model subroutine
Hello: I’m a post-doc at the University of Nottingham, and I’m using the hypoplastic model to simulate the centrifuge tests we did. The research area is related to soil-pile interaction. […] -
Oedometer test simulation with “Sand Hypoplasticity Model” in Plaxis
Hi, I just came across some problems with the implementation of the “Sand Hypoplasticity Model” in Plaxis. I wanted to to perform a simulation of an oedometer test on a […] -
Abaqus RITSS methon for LDFE analysis with hypoplastic
Hello everyone, I am using the ‘remeshing and interpolation technique with small strain’ (RITSS) method with hypoplastic, but I cannot continue the calculation after mapping. There is a warning in […]
Supporting Organisations
Recent posts
-
Abaqus RITSS methon for LDFE analysis with hypoplastic 17.3.2025
-
Request for VUMAT Implementation of Mohr-Coulomb, Drucker-Prager, or Drucker-Prager Cap 28.2.2025
-
Suggestions for an Advanced Constitutive Model in FEM-Based Dynamic Slope Stability Analysis 12.2.2025
-
Hardening Soil or Hardening Soil-Small umat in Abaqus 2.1.2025
-
hypoplastic interface 11.12.2024
-
Triaxial Test Driver SANISAND 30.10.2024
-
REQUEST FOR EXPRESSIONS OF INTEREST (REOI) FOR PROJECT IN CONSTITUTIVE MODELLING 23.10.2024
-
Programme of the ALERT Olek Zienkiewicz school on Constitutive Modelling of Geomaterials, February 3 to 7, 2025, Prague, Czech Republic 11.10.2024
-
Connecting remote sensors to the Plaxis FEM 3D using python 26.7.2024
-
Intergranular Strain Extensions 16.7.2024
-
Abaqus Hypoplasticity Primary Variable Is Not Available 1.7.2024
-
Vumat to calculate excess pore in Coupled Eulerian-Lagrangian ABAQUS 1.7.2024
Dear sudipta,
I am actually encountering the same issue with hypoplasticity for sand model, the program compiles but then stops without any error file and I was thinking about posting here too.
Let me know if you can figure out something. I will also post here if I can find any solution.
Thank you.
You have upgraded the Abaqus version. The same batch file of Abq14 will not work for Abq16. You just check and change the batch file.
I am using Abaqus 19 with intel one API. Can you please tell me the procedure for changing the batch file? Thank you.
for me oneAPI only works when I add next compiler command
!DEC$ ATTRIBUTES ALIAS:”umat”::UMAT
subroutine umat(………
If you use more subroutines you have to modify them too.
Thank you for your comment. Can you share the screenshot of the command file? I never use the command window before to RUN the UMAT file.
i have sent you a link that explains how to add this line
you do it for the stvarini subroutine also ?
no, only for standard abaqus subroutines like umat , usdfld ect
Hello,
I tried what you suggested but still facing the same problem. I have the same error message. Do you have any other suggestions.
Thanks in advance.
Hi Arie, thanks for your comment, this does not solve my provlem though, the code is compiling, but the analysis is aborted.
Hi all, small update, the problem seems to be the latest fortran compiler oneAPI, the umat works fine using the known parallel studio. this is actually a known issue with the latest released compiler, researchers are complaining on a daily basis on the intel website.
Are you able to find out where the problem is?
Hi, same problem here. I have Intel OneAPI, VS 2019 and Abaqus 2020 installed on my computer.
Abaqus command shows the compiler is present, when I query *abaqus info=system*
Same for *abaqus verify -user_std*, the check reports “pass”.
Then, when I run an attempt for a subroutine, the job aborts and no message file is available.
Dear Riccardo.. I am facing the same problem, the fortran subroutine codes works well with intel parallel compiler, but “Abaqus/Standards existed with an error” message appears whene using Abaqus 2021 with OneAPI Compiler.
@Kassem, be sure you are correctly initialising the state variables in your UMAT. I think the problem I was facing might be related to this incorrect initialisation process.
For example, the SANISAND Abaqus package available here on soilmodels.com contains a “StVarIni.for” file that initialises the 36 state variables that the UMAT requires to run the model. You can either copy the “StVarIni” code and paste it to the UMAT file, right after the first commented lines; or you can create a new fortran file that “calls” StVarIni and then the UMAT and link this last fortran file to the abaqus run.
@Sudipta Bhowmick were you able to solve the issue?
Dear Ricardo, were you able to run using the process described by you? Can you please explain in a little more detail as to where I should paste it?
To be honest, this kind of error messages could also be caused by some wrong settings in Abaqus. For example, wrong pre-difined field or wrong material parameters. Because you happened to invoke the user material subroutine, the simulation aborted, and you thought the abortion was caused by the user subroutine.