Question #404135 on Yade changed:
https://answers.launchpad.net/yade/+question/404135
Status: Open => Answered
Jérôme Duriez proposed the following answer:
1. The behavior you observed is normal. As the doc of
cohesiveTresholdIteration [1] says, Ip2_JCFpmMat_JCFpmMat_JCFpmPhys will
set as cohesive only the *new* contacts.
In fact, it is a general rule in YADE that any Ip2_* executes his job
(which is to define interaction properties) only once, where
interactions are created.
If you'd like to "apply" cohesion to a previously created packing, you
have to perform yourself Ip2_JCFpmMat_JCFpmMat_JCFpmPhys's corresponding
job, using Python loops:
for interaction in O.interactions:
interaction.phys.isCohesive = True
# define cohesive thresholds interaction.phys.FnMax [2] and
interaction.phys.FsMax [3] from material properties such as done in source code
[4]. See also corresponding equations e.g. in [Duriez2016] (listed among the
references of the doc)
2. Why are you expecting 13 as a coordination number ? The coordination number
you will eventually get for a given interaction radius highly depends on the
packing you're considering.
There is no unique relationship coordination number = f(interaction radius)
[1]
https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.Ip2_JCFpmMat_JCFpmMat_JCFpmPhys.cohesiveTresholdIteration
[2] https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.JCFpmPhys.FnMax
[3 ]https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.JCFpmPhys.FsMax
[4]
https://github.com/yade/trunk/blob/master/pkg/dem/JointedCohesiveFrictionalPM.cpp#L260
and line below
--
You received this question notification because your team yade-users is
an answer contact for Yade.
_______________________________________________
Mailing list: https://launchpad.net/~yade-users
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yade-users
More help : https://help.launchpad.net/ListHelp
