yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #00709
Re: ContactLaw1
-
To:
yade-dev@xxxxxxxxxxxxxxxxxxx
-
From:
Václav Šmilauer <eudoxos@xxxxxxxx>
-
Date:
Tue, 07 Oct 2008 09:17:27 +0200
-
In-reply-to:
<20080927133734.6cb5f3a9@szpak>
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.17) Gecko/20080925 Lightning/0.8 Thunderbird/2.0.0.17 Mnenhy/0.7.5.666
>> If the constitutive law is simple as
>>
>> // loop over interactions etc
>> Fn=contactGeom->strainN()*crossSection*E;
>> Ft=contactGeom->strainT()*crossSection*G;
>> // apply forces here
>>
>> the code for computing strain being elsewhere, then that code is still
>> in one place (and can be fixed at one place) and the constitutive law is
>> not a mess of flags.
>>
Hi there, I implemented ElasticContactLaw2 (for ilustration) that
behaves like ElasticContactLaw (except that all contact are cohesive
(don't break) and there is no moment rotation law) and uses new
SpheresContactGeometry code; the code is about 15 lines.
This is the way I imagine all constitutive laws should eventually look
like: relationship from relative displacements (computed in the contact
geometry class) to forces, nothing else.
Vaclav
Follow ups
References