Search results for query: *

I have attached the UMAT as "Job.for".

here is the inphttp://files.engineering.com/getfile.aspx?folder=9f5fb7ba-c5c5-42bb-a6a5-025f39d9f61e&file=Job.inp

I have uploaded the new inp and umat file in the following post.http://files.engineering.com/getfile.aspx?folder=d7a24a97-0227-459f-9150-b42596daa92c&file=Job.for

It is write to the .msg file.

you can add it to the UMAT IF (NOEL.EQ.1901 .AND. NPT.EQ.1) THEN WRITE(7,4) STATEV(3*NTENS+2),KINC,KSTEP 4 FORMAT(1X,F15.8,I4,I4) END IF I also attach it.http://files.engineering.com/getfile.aspx?folder=0dc5e098-998e-4028-b478-a59315e32f56&file=Job.for

If you output the sdv19 by EI Print, it is indeed always zero. But if you output it by write(6,*) at the end of the UMAT, it is not always zero, and the updated sdv did pass in the new increment. That is reason I asked. Output by EI PRINT in input File and UMAT should be the same and not always...

Attached is the umat file.http://files.engineering.com/getfile.aspx?folder=efb1cff1-7ddc-4834-a203-7a80db76b454&file=Job.for

Hi, The sdv19 are not zero by checking the file written at the end of umat. There are far from zero. I enclosed the Umat file and inp file. Could you run and check, and find why sdv19 in odb file are always zero? Thanks...

For the *DEPVAR in the inp file, I defined it with a number, for example *DEPVAR 19,

Dear all, I have questions about writing sdv in Umat to odb file. According to a lot of sayings in internet, the statev could write to odb by the following inp: *Output, field *Element Output S,E,SDV I have my Umat at the beginning CALL ROTSIG(STATEV( 1),DROT,EELAS,2,NDI,NSHR) CALL...