The Buildbot has detected a failed build of yade-full on Yade.
Full details are available at:
http://yade-dem.org/buildbot/builders/yade-full/builds/639
Buildbot URL: http://yade-dem.org/buildbot/
Buildslave for this Build: r0calcul10
Build Reason: The Nightly scheduler named 'nightly' triggere
The build server has about 478 MB RAM. Yade requires minimum 1.5GB.
It is not related to this bug, but I think it cannot be built on ARM for the
moment.
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to yade in Ubuntu.
https://bugs.launchpa
Remi, could you please, have a look, what is wrong with --check?
Try to start the command on server.
Last 2 commits give an error:
process killed by signal 11
program finished with exit code -1
elapsedTime=1.776973
I do not think it is connected with checkGravity script.
Thanks
Anton
On T
The Buildbot has detected a failed build of yade-full on Yade.
Full details are available at:
http://yade-dem.org/buildbot/builders/yade-full/builds/638
Buildbot URL: http://yade-dem.org/buildbot/
Buildslave for this Build: r0calcul10
Build Reason:
Build Source Stamp: 2884
Blamelist: Anton Gla
Christian,
I found your mistake. It is not in the way you define _hn or _hs (they are
correct, we just use to define the effective radius in a different way but
then there is a factor of 2 in your -actually PFC manual's - final equation
so that we get the same number) BUT it is in your python scri
revno: 2884
committer: Anton Gladky
branch nick: yade
timestamp: Thu 2011-07-14 18:09:34 +0200
message:
Change the number of steps for checkGravity.py
modified:
scripts/test/checks/checkGravity.py
--
lp:yade
https://code.launchpad.
The Buildbot has detected a failed build of yade-full on Yade.
Full details are available at:
http://yade-dem.org/buildbot/builders/yade-full/builds/637
Buildbot URL: http://yade-dem.org/buildbot/
Buildslave for this Build: r0calcul10
Build Reason:
Build Source Stamp: 2883
Blamelist: Anton Gla
You (not PFC at this point) are defining the effective radius in the wrong
way. And well, to my opinion _hn (and _hs) should NOT be user defined as
their values are well established by Hertz (and Mindlin) theory itself.
Please input the same constant coefficients that you find in Yade if you
still
Hi, Jerome,
I have got a crash with --check option in this script.
checkTestNormalInelasticity.py
I cannot give a log-file. Could you, please, start "--check" several times?
Thanks
Anton
___
Mailing list: https://launchpad.net/~yade-dev
Post to :
revno: 2883
committer: Anton Gladky
branch nick: yade
timestamp: Thu 2011-07-14 17:34:01 +0200
message:
Add one more --check scripts to check GravityEngine and NewtonIntegrator
added:
scripts/test/checks/checkGravity.py
--
lp:yade
Good to hear!
Please, close the bug.
Anton
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/806944
Title:
different behavoir of Hertz model while comparing PFC and YADE
Status in Yet Another D
Thank you for the hint, Anton.
I divided kn with the mass of the balls and the result is the same as in pfc.
results yade:
step normal force
1.00e+00 -5.00e-06
2.00e+00 -9.902892e-06
3.00e+00 -1.461345e-05
4.00e+00 -1.904020e-05
5.00e+00 -2.309715e-
> While comparing linear models, I get difference factors of about 2e12
> ... 3e12 !!!
>
> Can someone please check my script, I think in this case I did a mistake
> (see attachment).
Hi, sorry, I do not have an opportunity for the moment to check your
script in details.
But in ViscElMat all param
In the udm_hertz the user has to modify contacts manually, as you can
see here:
def modify_cp
bp1 = c_ball1(cp)
;ball pointers
bp2 = c_ball2(cp)
c_model(cp) = 'udm_hertz'
_fricset = friction_coeff
if pointer_type(bp2) = 100 ; Ball-Ball contact
_meff =
b_realmass(bp1)*b_realma
There is NO bug here and no shear force (it is numerically zero). It is
clear to me that PFC computes contact stiffness in a different way. Do you
know how it is computed in PFC then? Do you know which formula they actually
implement? In Yade you can easily check it yourself in the code
(seeIp_Fric
While comparing linear models, I get difference factors of about 2e12
... 3e12 !!!
Can someone please check my script, I think in this case I did a mistake
(see attachment).
** Attachment added: "viscoelastic-test-step-by-step-linear.tar.gz"
https://bugs.launchpad.net/yade/+bug/806944/+attach
I found out, that values for normal forces differs with a constant
factor of exactly 2.5 !
hope it helps...
--
You received this bug notification because you are a member of Yade
developers, which is the registrant for Yade.
https://bugs.launchpad.net/bugs/806944
Title:
different behavoir of
Ok, so this bug (?!) seems to be more important, than I thought...
I compared the first 10 steps of the previous model and created 2 output files
(force-disp-pfc.txt and force-disp-yade.txt) and 2 force-displacement plot
files (force-disp-pfc.bmp and force-disp-yade.png).
Note, that coordinate s
18 matches
Mail list logo
