The STATEV that get stored at the end of the iteration are getting carried forward. But after rotating by DROT, I printed to see the value of STATEV. They become zero after rotation. I have used the following command for rotation.
CALL ROTSIG(STATEV( 1), DROT, STATEV(1), 2, NDI, NSHR)
I have rotated the STATEV variable array and stored it back at the same place.
My doubt
After rotation is it right that the STATEV become zero?
Is the syntax that I have used above correct?
I have also attached my UMAT file.
Hi,
I am not sure about your problem. but I think you are trying to rotate a variable( that is just a number) while you have to rotate a higher rank tensor with this function such as stress or strain.
Just a little more clarification about what your state variables stand for might be useful to understand your problem.
@Ali Xajezade
The STATEV variable I am trying to rotate is a strain tensor internal variable of a Shape memory polymer.
STATEV becoming zero after rotation was a misunderstanding. But what actually happening is, the STATEV after rotation are giving incorrect and too large values.
Even after turning NLGEOM off, the rotation shouldn't affect the STATEV, but the Rotation is making STATEV wrong.
Dear Amique,
you should try to make a 'buffer variable' (STRANOLD/STRESSOLD in code) and not to change your STATEV directly. The example is in following code:
GET OLD DATA AND ROTATE TO CURRENT ORIENTATION OF THE MATERIAL:
CALL ROTSIG(STATEV( 1), DROT, STRANOLD, 2, NDI, NSHR)
CALL ROTSIG(STATEV( NTENS+1), DROT, STRESSOLD, 1, NDI, NSHR)
Please let me know if it works,
Robert
Dear Amique,
I am also facing the same problem. Could you able to fix the problem. If you were able to fix out this issue. please help in.
thank you
murty
- Badges
- Science topic