Hello,
I am creating a user-defined material model (user,2) which needs to store 10 history variables. I set n1=10 in UMATI2, then wrote the main code in UMATL2.
I presumed that n1 is the size of hn() and the size of h1() (i.e., for n1=10, hn and h1 are assigned 10 components each).
While running some simple analysis, I noticed that one of the history parameters spuriously changes during computation (meaning that, while it is stored with the proper value in the correct location of h1, when it is called in subsequent steps of the computation by using the appropriate component of hn its value has become zero).
More strangely, by changing the value of n1 to 20, the computation proceeds normally and I do not see any problem with the history variables.
I would be grateful if you could provide me with any ideas on what may be causing the issue. I am running a single-element analysis (plane stress conditions)
and the only user-defined component is the material model (I am not using user-defined elements which could be spuriously accessing and changing history terms)...