HETVAL subroutine: FLUX(2)
HETVAL subroutine: FLUX(2)
(OP)
How should FLUX(2) in the HETVAL subroutine be defined? The Abaqus user subroutine reference manual did not seem to help.
Thanks,
Emily
Thanks,
Emily
INTELLIGENT WORK FORUMS
FOR ENGINEERING PROFESSIONALS Come Join Us!Are you an
Engineering professional? Join Eng-Tips Forums!
*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail. Posting GuidelinesJobs |
HETVAL subroutine: FLUX(2)
|
RE: HETVAL subroutine: FLUX(2)
It just helps the solver along, I don't think it is required for Abaqus/Standard, in fact I think I usually just write FLUX(2)=0.
However, if you are using Abaqus Explicit then it may be much more important for convergence rates.
Haven't checked HETVAL vs. DFLUX, but if they are anything alike this analogy should apply.
What I would do to test this theory is try FLUX(2)=0 and FLUX(2)=100 in your analysis and check the difference.
Just off the top of my head, anyway.
RE: HETVAL subroutine: FLUX(2)
Do you know how to determine if I am using Abaqus standard or Explicit?
RE: HETVAL subroutine: FLUX(2)
Any thoughts?
RE: HETVAL subroutine: FLUX(2)
I was trying to say that a simple test like trying 1, and 0 may answer your question.
When your solver licenses are checked out, are you using standard or explicit?
For example, when you run your job through DOS just type in "abaqus licensing lmstat -f" while your job is running and see what is checked out.
Another way is to check your step definition in the input file,
i.e. something like "*Dynamic, Explicit, adiabatic" may be the line you are looking for.
RE: HETVAL subroutine: FLUX(2)
RE: HETVAL subroutine: FLUX(2)
RE: HETVAL subroutine: FLUX(2)
FLUX(1)=(cp*density*(tref-REAL(TEMP(1))))/DTIME/10
FLUX(2)=0.0
It seems to be working just fine. Do you think FLUX(2) is okay being equal to zero in my case?