Dear users/devs, who is working with clumps,
I have done a tiny modification in NewtonIntegrator [1], which
should fix numerical instability with clumps in a rare cases.
Subject: [PATCH] Do not use
Hi Anton,
Two problems I suspect:
1/ It needs speed benchmarking. This little change may have a huge
impact on parallel performance, because - if I don't miss something -
each addForce/addTorque trigger the synchronization of the whole
force/torque containers [1], which is not small thing as you
Hi all,
sorry for the noise. This change is reverted.
Anton
2014-05-16 11:48 GMT+02:00 Anton Gladky gladky.an...@gmail.com:
Dear users/devs, who is working with clumps,
I have done a tiny modification in NewtonIntegrator [1], which
should fix numerical instability with clumps in a rare
I left mask parameter for the purpose of slecting bodies to calm and
modified documentation of the function (the original version mentioned,
that the function calms all bodies, which was the source of my confusion).
Thanks for discussion
Jan
2014-05-12 12:06 GMT+02:00 Jan Stránský
revno: 3958
committer: Jan Stransky jan.stran...@fsv.cvut.cz
timestamp: Fri 2014-05-16 14:22:07 +0200
message:
modification of utils.calm function (bug 1318513)
modified:
pkg/dem/Shop_02.cpp
py/_utils.cpp
--
lp:yade
revno: 3956
committer: Anton Gladky gladky.an...@gmail.com
timestamp: Fri 2014-05-16 13:48:12 +0200
message:
Revert last change in Newtonintegrator.
modified:
pkg/dem/NewtonIntegrator.cpp
--
lp:yade
revno: 3955
committer: Anton Gladky gladky.an...@gmail.com
timestamp: Fri 2014-05-16 11:46:02 +0200
message:
Make addForceTorqueFromMembers more readable.
modified:
core/Clump.cpp
--
lp:yade
revno: 3954
committer: Anton Gladky gladky.an...@gmail.com
timestamp: Fri 2014-05-16 11:46:02 +0200
message:
Do not use getTorqueUnsynced and forces.getForceUnsynced in clumps
It seems both of these commands are unsafe. It causes
revno: 3957
committer: Jan Stransky jan.stran...@fsv.cvut.cz
timestamp: Fri 2014-05-16 13:58:59 +0200
message:
Polyhedra implementation improvement (Contributed by Jan Elias)
modified:
pkg/dem/Polyhedra.cpp
pkg/dem/Polyhedra.hpp
Did you change your mind Anton? Or git-mistake? :)
B
On 16/05/14 14:38, nore...@launchpad.net wrote:
revno: 3954
committer: Anton Gladky gladky.an...@gmail.com
timestamp: Fri 2014-05-16 11:46:02 +0200
message:
Do not use
2014-05-16 14:56 GMT+02:00 Bruno Chareyre bruno.chare...@hmg.inpg.fr:
Did you change your mind Anton? Or git-mistake? :)
I tested wrong binary, which worked fine (clang, without OpenMP).
OpenMP+GCC throws obviously runtime_error
ForceContainer not thread-synchronized; call sync() first!.
Thanks
Did you change your mind Anton? Or git-mistake? :)
Sorry for this message, I had the impression that you introduced the
change again in rev3954 after reverting it.
Just a weird sequence of emails maybe, on github it looks ok.
Good to know that compilation with openMP also showed the problem.
I pushed a fix (3b09fb5) but I could not test it. Can you confirm?
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1314736
Title:
Segfault possibly in new parallel collider
Status in Yet Another
revno: 3961
committer: Christian Jakob ja...@ifgt.tu-freiberg.de
timestamp: Fri 2014-05-16 17:26:12 +0200
message:
remove typenames from Polyhedra.cpp (fixes compiler error)
modified:
pkg/dem/Polyhedra.cpp
--
lp:yade
revno: 3963
committer: Christian Jakob ja...@ifgt.tu-freiberg.de
timestamp: Fri 2014-05-16 19:03:55 +0200
message:
fix some indents
modified:
py/wrapper/yadeWrapper.cpp
--
lp:yade
https://code.launchpad.net/~yade-pkg/yade/git-trunk
revno: 3960
committer: Bruno Chareyre bruno.chare...@hmg.inpg.fr
timestamp: Fri 2014-05-16 16:41:07 +0200
message:
switch to 1-thread colliding when problem detected in parallel run (fix
https://bugs.launchpad.net/yade/+bug/1314736)
16 matches
Mail list logo
