yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #03622
[Bug 493102] Re: NormalShearInteraction::{normalForce, shearForce} has undefined orientation
Discussed in this thread: http://www.mail-archive.com/yade-
users@xxxxxxxxxxxxxxxxxxx/msg01285.html
--
NormalShearInteraction::{normalForce,shearForce} has undefined orientation
https://bugs.launchpad.net/bugs/493102
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
Status in Yet Another Dynamic Engine: Confirmed
Bug description:
NormalShearInteraction::{normalForce,shearForce} should contain forces on the interaction, which can be used for various purposes by other functions. However, different functors use them with different sign
ef2_Spheres_Elastic_ElasticLaw (a.k.a. ElasticContactLaw):
applyForceAtContactPoint(-currentContactPhysics->normalForce-shearForce, ... )
Law2_Dem3DofGeom_CpmPhys_Cpm:
applyForceAtContactPoint(BC->normalForce+BC->shearForce, ...)
This is a convention issue, but must be fixed. Should normalForce and shearForce be oriented as it applies on id1 (first case) or id2 (second case)? 2nd case is nicer WRT applyForceAtContactPoint syntax, but that one is arbitrary as well.
References