Hi guys,
After getting lots of help from the support, we figured it out.
In my environmental file I had some settings which allowed me to compile f90 files in runtime (the support hadn't seen this before). The subroutines were treated as object files. I was always compiling standalone the...
Hi Bartosz,
Thanks a lot for your answer! It really helped me a lot to clarify these things.
I was always using "implicit none" on my codes because I'm used to that (from before I started with User Subroutines) and that's why I was declaring variables. Anyway, your explanation of Abaqus'...
Thanks! I contacted the guy from abaqus support I usually contact but he's out of office until Thursday.
Could you plese give a direct link to a forum in the "community"? I'm already registered in 3ds.com but somehow I can't find a forum like this to post. Thanks a lot once again!
Hi IceBreaker, thanks for your reply!
Sorry if I wasn't very clear. What I meant is that if I declare my variables as double precision in my VUMAT (for example, DOUBLE PRECISION props(nprops)) the values I set in the abaqus input file do not match those stored in the array 'props' (I'm printing...
Hi all,
Can anybody help me out running a VUMAT with double precision?
If I define my variables in VUMAT as double precision and run "abaqus user=... job=..." the values do not match those in the inp file.
On the other hand, if I run "abaqus double user=... job=... " I get the following...
Hi,
I'm writing an UMAT and I need to have simultaneously the coordinates of my 4 integration points so I can compute the "shear angle". The problem is that (maybe I'm wrong with this) UMAT is called again for each integration point at each iteration so the variable COORD is updated to the...
Hi Geokim,
Probably it's already too late but I was trying to do the same and here is the solution I found. It worked for me!
import odbAccess
odb=odbAccess.openOdb(path=myPath,readInternalSets=True)
