← Back to team overview

yade-dev team mailing list archive

Re: Combining engines prescribing movement (moved from yade-users)

 


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