[Yade-users] Combining engines prescribing movement

Hello, is it possible to combine more engines prescribing movement? for example (I know there is HelixEngine implemented, but suppose for a while it is not :-) if I want to combine translation and rotation to create a helix, can I somehow combine them, or for every such combination would I

Re: [Yade-users] can I have the supported documents?

Hi Liqing, something about strain softening (I hope is has the same meaning as strength softening :-) you can find under links below. If it is not what you are looking for, then sorry for sapmming :-) Jan http://mech.fsv.cvut.cz/~milan/papers/alert-course-3.pdf

Re: [Yade-users] To Liqing and Jan (and all users in general)

Ok, sorry for that, I thought that mails are sorted according to the subject, the next time I know how to begin a new topic :-) Thanks for advice and correction cheers Jan __ Od: Václav Šmilauer e...@doxos.eu Komu: Yade Users Group

Re: [Yade-users] Combining engines prescribing movement

Hi (Anton), actually this question came to my mind after reading about the new engine :-) My idea was if there is something similar to predicates, like O.engines = [ , TranslationEngine(...) + RotationEngine(...), ... ] or another solution could be O.engines = [ ... ,

Re: [Yade-users] Combining engines prescribing movement

is it possible to combine more engines prescribing movement? for example (I know there is HelixEngine implemented, but suppose for a while it is not :-) if I want to combine translation and rotation to create a helix, can I somehow combine them, or for every such combination would I need to

Re: [Yade-users] To Liqing and Jan (and all users in general)

Oh, sorry. :) I will do my best to avoid this in future. Thank you for this reminder. Cheers Liqing At 2010-11-19 18:21:32，Jan Stránský _hon...@centrum.cz wrote: Ok, sorry for that, I thought that mails are sorted according to the subject, the next time I know how to begin a new topic :-)

Re: [Yade-users] Combining engines prescribing movement

What if if do so in Translation/Rotation engines?: if (!b-isDynamic())b-state-pos+=dt*velocity; Anton 2010/11/19 Václav Šmilauer e...@doxos.eu OK, after some thinking and skyping w/ Chiara: I will remove displacements and rotations in ForceContainer, and replace them by one-time

Re: [Yade-users] can I have the supported documents?

Hi Jan, Thank you for your warm help! :) Cheers Liqing At 2010-11-19 17:42:04，Jan Stránský _hon...@centrum.cz wrote: Hi Liqing, something about strain softening (I hope is has the same meaning as strength softening :-) you can find under links below. If it is not what you are looking

Re: [Yade-users] Combining engines prescribing movement

I mean just for now. Ah, sorry. But I plan to do those changes in next few hours/days. v. ___ Mailing list: https://launchpad.net/~yade-users Post to : yade-users@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-users More help :

Re: [Yade-users] Combining engines prescribing movement

In many cases (perhaps not yours) the simpler way is to prescribe velocity on non-dynamic bodies. That way, you don't need engines, and you are sure you are not breaking any of the constitutive laws. Eh? This exactly will not work: NewtonIntegrator.cpp:109 says if(!b-isDynamic()) continue;

Re: [Yade-users] Combining engines prescribing movement

vel=(P_axis-Pos).cross(spin*axis) rotVel=spin*axis I thought the point was that the integrator would do it for you (which it can, for translation). Of course this is what RotationEngine does. ___ Mailing list: https://launchpad.net/~yade-users