yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #06216
Re: Combining engines prescribing movement (moved from yade-users)
-
To:
Yade Development Group <yade-dev@xxxxxxxxxxxxxxxxxxx>
-
From:
Václav Šmilauer <eu@xxxxxxxx>
-
Date:
Fri, 19 Nov 2010 13:49:26 +0100
-
In-reply-to:
<4CE6593E.3060007@doxos.eu>
-
Mail-followup-to:
Yade Development Group <yade-dev@xxxxxxxxxxxxxxxxxxx>
-
Mail-reply-to:
Václav Šmilauer <eu@xxxxxxxx>
-
User-agent:
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.19) Gecko/20090105 Lightning/0.8 Thunderbird/2.0.0.19 Mnenhy/0.7.6.666
I will remove displacements and rotations in ForceContainer, and
replace them by one-time velocity and angularVelocity: they will be
added to state->vel and state->angVel in NewtonIntegrator, but reset
by ForceResetter; and they can accumulate, just like forces do.
There is another problem with this approach, which is that those
transient velocities will be considered only in NewtonIntegrator, but
not elsewhere (think kineticEnergy, mutual velocity, ...).
The mess comes from the fact that we would like to have a part of
velocity (in state->vel) that is remembered only as long as an engine is
active, and then disappears; this is not possible (unless we invent very
ugly things).
Is someone smart enough to propose a solution that would satisfy the
following?
1. make state->vel always derivative of state->pos (even if multiple
translations/rotation/... engines are applied, there are interactions etc)
2. effects of kinematic engines are there only as long as the engines
are active
3. perhaps something else I forgot...
Cheers, v.
Follow ups