yade-users team mailing list archive

[Bruno Chareyre <question657677@xxxxxxxxxxxxxxxxxxxxx>]

Question #657677 on Yade changed:
https://answers.launchpad.net/yade/+question/657677

Bruno Chareyre proposed the following answer:
Hi,
Comment #3 is not very clear to me, but the error message is rather clear about how to fix the issue: "consider setting a positive verletDist in your script".

Further, Yade's documentation has a search box which can help. If you search verletDist you find [1]:
 verletDist(=-.5, Automatically initialized)
    Length by which to enlarge particle bounds, to avoid running collider at every step. Stride disabled if zero. Negative value will trigger automatic computation, so that the real value will be verletDist × minimum spherical particle radius; if there are no spherical particles, it will be disabled.

You have no spherical particles, hence the problem when auto-configuring the collider. Set collider's verletDist to a fraction of the polyhedra minimum size and it should be fine.
This is absolutely not related to import/export. Yet if you choose to import/export this verletDist setting will have to be repeated when reloading, which you can easily avoid by not splitting the task in two different scripts (as suggested in #2).
I hope it helps.
Bruno

p.s. This being said, not setting verletDist should raise a warning
(sub-optimality), not an error. I just changed that in the sources
(commit 949a2d9bd62).

[1] https://yade-
dem.org/doc/yade.wrapper.html?highlight=verletdist#yade.wrapper.InsertionSortCollider.verletDist

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.