chiara modenese said: (by the date of Thu, 26 Aug 2010 16:27:50 +0100)
On 26 August 2010 13:25, Bruno Chareyre bruno.chare...@hmg.inpg.fr wrote:
I bet on contact law returning nan value (division by 0, or something like
that).
Then velocity is NaN when this force is integrated.
Interesting. Also remember that you can advance line by line and inspect
values with the debugger, with various conditional breakpoints.
I do that with kdevelop but I guess it can as well be done with other
gdb frontends or with gdb alone.
Oh yes, of course. This is just much much easier.
Hello Chiara,
I have no precise remark but you are indeed not the first one having
problems with Nan velocities : see
http://www.mail-archive.com/yade-dev@lists.launchpad.net/msg04519.html
and
http://www.mail-archive.com/yade-dev@lists.launchpad.net/msg04766.html
(at least).
Jerome
I bet on contact law returning nan value (division by 0, or something
like that).
Then velocity is NaN when this force is integrated.
Cheers.
Bruno
On 25/08/10 20:12, chiara modenese wrote:
Hi all,
what are the reasons for which one should get the following message
from a simulation?
On 26 August 2010 13:25, Bruno Chareyre bruno.chare...@hmg.inpg.fr wrote:
I bet on contact law returning nan value (division by 0, or something like
that).
Then velocity is NaN when this force is integrated.
You win the bet, sorry. After a day of debugging, I realized I was returning
a
Hi all,
what are the reasons for which one should get the following message from a
simulation?
9088 FATAL yade.ThreadRunner
/home/chia/Documents/yade-r2394-psd2/core/ThreadRunner.cpp:31 run: Exception
occured:
Body #5653 has velocity==NaN!
In my case it happens right after I launch a triaxial
6 matches
Mail list logo
