← Back to team overview

yade-dev team mailing list archive

Re: velgrad

 

> (2) can work, but the risk is to integrate the deformation many times in 
> only one step (imagine I set velGrad). Something like (3) would be 
> enough for me, with explicit warnings in files documentation. It is the 
> job of users to understand how engines interact with each other. Trying 
> to make the code foolproof is just making things more complex and less 
> versatile, sometimes.
I will separate the cache update and integration, that's easy and solve
that.

v




References