yade-dev team mailing list archive

[Bruno Chareyre <bruno.chareyre@xxxxxxxxxxx>]

> I don't think it would work. The collider needs one value for wrapping
> coordinates between zero and that number (separately for each axis). I
> didn't check carefully, though.
>
>   
I'm still thinking it could work but didn't try.
I commited some code for arbitrary (proportional) deformations that you 
can test with a new py script.
It seems there is a growing offset between displayed cell and actual 
period (the second being the one used for interactions). No surprise, 
this is purely experimental.
I didn't touch AABBs and collider for now.

The only (small) change in the default behaviour is this :

NewtonIntegrator.cpp l.184

if(homotheticCellResize>=1) state->pos+=dPos;
   //update velocity for usage in rate dependant equations (e.g. 
viscous law) FIXME : it is not recommended to do that because it impacts 
the dynamics (this modified velocity will be used as reference in the 
next time-step)
   if(homotheticCellResize==2) state->vel+=dPos/dt;

Merry Christmas all! :)

Bruno

p.s. How can we do something like this? For now, it (apparently) runs in 
the background so that the second definition of velGrad is used for 
almost 2000 steps :

O.cell.velGrad=Matrix3(0,5,0,0,0,0, 0,0,-5)
O.run(1000)
O.cell.velGrad=Matrix3(1,0,0,0,0,0, 0,0,0)
O.run(1000)


> v
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help   : https://help.launchpad.net/ListHelp
>
>   


--

_______________
Chareyre Bruno
Maître de Conférences

Grenoble INP
Laboratoire 3SR - bureau E145
BP 53 - 38041, Grenoble cedex 9 - France
Tél : 33 4 56 52 86 21
Fax : 33 4 76 82 70 43
________________