Continue to Site

Eng-Tips is the largest engineering community on the Internet

Intelligent Work Forums for Engineering Professionals

  • Congratulations waross on being selected by the Eng-Tips community for having the most helpful posts in the forums last week. Way to Go!

Abaqus UMAT query: Issues with NaN

Status
Not open for further replies.

sc267

Mechanical
Dec 11, 2014
2
Hello, I have a written a UMAT for a hyperfoam type material in Abaqus. To validate it I am comparing my UMAT results with that from a *HYPERFOAM material definition. I am facing a particular problem:

Under a displacement load on the boundary the UMAT results are comparable to that of the *HYPERFOAM results. I compare displacement U, nodal forces TF, deformation gradient DG and total strain energy and work done. For total strain energy and work done the first few significant digits match and the difference between the two results increase slightly with increase in increment, but still the accuracy is acceptable and hence I conclude that my UMAT is probably working correctly.

Next I apply a different set of displacement BC (of lower magnitudes) on the same set of boundary nodes where I had prescribed BC in the above case. I observe that the solution from UMAT gives me NaN values for all fields from increment 3 onwards, whereas with *HYPERFOAM case no such problem occurs.

On further investigation I find that in the UMAT Abaqus passes in NaN values for DFGRD1 and STRESS during the initial iterations (while searching for an equilibrium solution) in increment 3. I also verify that in the previous 2 increments there is no NaN or 1/0 (inifinity) type values returned from UMAT.

Can anyone please suggest what can be a plausible reason for this problem ?

Thank you for your time and advice.

--
Sourish
 
Replies continue below

Recommended for you

@IceBreakerSours, thanks for your reply. All the relevant real valued variables and parameters are set as double precision in my Fortran Umat.

Also, thanks for the making me aware of the forum etiquettes. It seems I am guilty of a few of the "don'ts" in the etiquette list. I'll be conscious of these henceforth.
--
Sourish
 
When I write code, I punch in lines that are useful for debugging purposes or spit out messages if 'something' isn't what it is supposed to be. When it comes to Fortran code for use with Abaqus, it also helps to have a Mathematica script to have a 'gold standard' to compare against. For all you know, however unlikely it may be, it is possible that the implementation in Abaqus has bugs in it.

Are you new to this forum? If so, please read these FAQ:

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor