Hi,
Abaqus converts all names to upper case and removes all white signs.
In your case you need use:
if (cmname .eq. 'MATERIAL-1') then
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
...executable section starts after first executable line and after it you must not put any declaration lines.
Here is executable section line:
PI=2.*ASIN(1.D0)
and later you have declaration section line:
PARAMETER(DENSITY=1024D0,GRAVIATION=9.81D0,RADIUS=0.15D0,MINRADIUS=-0.15D0,RADIUS1=20)...
Hi
You defined AREA variable as parameter it means the variable never change value and always will be 0.0.
PARAMETER(RADIUS=0.15D0,AREA=0.D0)
but next you try to change AREA value
AREA=AREA+AREA1
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
Hi
You can define name and description for each state variable.
***DEPVAR
** number of variables
3
** variables list
1, outputKey1, outputDescription1
2, outputKey2, outputDescription2
3, outputKey3, outputDescription3
**
Bartosz
VIM filetype plugin for Abaqus...
Hi,
It you prefer to work directly with abaqus inputdecks in text editor the plugin make work easier.
However it is for VIM text editor so you have to know it.
Regards,
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
Hi,
You must not use more than one USDFLD subroutine.
You can test your material name with CMNAME variable to do different operation for each material in your model.
See following thread for more info:
http://www.eng-tips.com/viewthread.cfm?qid=314887
Regards,
Bartosz
VIM filetype plugin...
Hi,
I ran your model and I noticed FV1 vary between value of 145.0 and 375.0.
With your material definition it make sense only when FV1 vary from 1.0 to 2.0.
Abaqus use constant extrapolation outside field variable range so any value above 2.0 will use E=2e+09.
Please check your equation...
Hi,
Could you share your inputdeck and subroutine, please?
I will take a look for it.
Regards,
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
Hi,
It looks like your UMAT is wrong, to be more precise FORTRAN does not like line 14 "4 JSTEP(4)".
If you compare your UMAT arguments with documentation you will find a mistake. One before the last argumnent is JSTEP not KSTEP.
SUBROUTINE UMAT(STRESS,STATEV,DDSDDE,SSE,SPD,SCD,
1...
Hi Jungao
>>> Is it correct that we need to declare 'save' in the beginning, then they are saved as global variables
By default all variables used in subroutine are not controlled after call.
It means part of memory where your variable is stored can be overwrite by any other program or Abagus...
Hi Jungao,
I have never used URDFIL subroutine so I know nothing about it.
But as long you are ok with displacement and velocity of integration points you can evaluate them in DLOAD.
! keep values in memory
save rPrevCOORDx
save rPrevCOORDy
save rPrevCOORDz
save rPrevTIME
! disp =...
Hi Jungao
It is good to hear that it is starting to work as you expecting.
One advice from my side. You really should not depend on "187 offset" between user and internal ids.
It's probably true only for this one model, or maybe not. It is high likely with different Abaqus version/number of...
...it's actually looping in main function ABAQUS to define F for each element integration point
Yes.
>>> the size of the loop is (element number*integration number)
It always depend on element types used in DLOAD. I think in your case your are right (element number*integration number).
>>> If...
...numbering at pre-processor phase.
In other case we must know internal id for each user id.
What error? Did you add declaration statement "CHARACTER*80 CPNAME"
By the way following syntax is incorrect, my bad, sorry.
iUserId = GETPARTINFO(NOEL, 1, CPNAME, LOCNUM, JRCD)
It should be
call...
Hi Keith,
Make sense for me. You can check it in easy way with "WRITE(6,*) NOEL,NPT,JLTYP".
It transfers only elements with applied user load, so in your case all elements in LOADELEM elset.
If you are using flat inputdeck and still id of elements does not fit to inputdeck maybe...
...iUserId = GETPARTINFO(NOEL, 1, CPNAME, LOCNUM, JRCD)
! apply load elements in range 1:114
if (iUserId >= 1 .and. iUserId <=114)
F = 2.0 * iUserId
endif
endif
2. Flat inputdeck:
! apply load for specific load type only
if (JLTYP == 42) then
! apply load elements in range...
...So if you have first step which doesn't change your initial values you will get them also in second step.
Sounds good, you can use python to save external file and just use *INCLUDE to add it to your model.
Regards,
Bartosz
VIM filetype plugin for Abaqus
https://github.com/gradzikb/vim-abaqus
...but in documentation is information that values are read from output database so I understand from odb file.
Try to save FV outputs to odb (*NODE OUTPUT) and than use *INITIAL CONDITION, FILE=...
I have two ideas:
1. USDLD and 2 steps
I would create first step to just initialize FV in the...
Hi,
I do not think the problem is related to full integrated element type you are using.
Each integration point is treated separately in you example so it should not be a problem.
Is there any rule for initial distribution which can be describe with an equation?
One more point, are you sure...
