In our case, we have elastic-plastic interaction at contacts only, while
the capillary model apply even between distant particles, with a max
distance depending on many things (grains size, succion, assumption on
wetting or drying path,...). So, the natural choice was to never erase
interactions in the elasto-plastic law, and let the capillary law delete
interactions when fluid forces disapear.
Bruno
.
chiara modenese a écrit :
In reply to a question from Vaclav (a comment somewhere in a
file...), capillaryLaw is THE reason to disable requestErase in
the contact law.
Actually, we have somehow two constitutive laws each interaction
here, so we have to make sure one is not deleting the interaction
when the other still needs it.
Hi Bruno,
I am interested in this (see above). I need something similar for my
contact law (although I still have to start implementing it). In which
part of the code would you erase the interaction if not in the contact
law?
Chiara
_______________________________________________
Mailing list: https://launchpad.net/~yade-dev
<https://launchpad.net/%7Eyade-dev>
Post to : [email protected]
<mailto:[email protected]>
Unsubscribe : https://launchpad.net/~yade-dev
<https://launchpad.net/%7Eyade-dev>
More help : https://help.launchpad.net/ListHelp
------------------------------------------------------------------------
_______________________________________________
Mailing list: https://launchpad.net/~yade-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp
--
______________
Chareyre Bruno
Maitre de Conferences
Grenoble INP
Laboratoire 3SR - bureau E145
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
________________
_______________________________________________
Mailing list: https://launchpad.net/~yade-dev
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp
