yade-users team mailing list archive

[Anton Gladky <gladky.anton@xxxxxxxxx>]

Hi, some short notes,

I think it is better for you to create one more engine, like RotationEngine,
but it should accept 2 axises and 2 angular velocities.
Then you create 2 quaternions, multiplicate them and move SubscribedBodies.

Should work, probably.
Sorry, no time to check it.
______________________________
Anton Gladkyy


2010/7/16 Michael Jensen <jenmichael2000@xxxxxxxx>

> :-)
>
> from your responses, I gather that my scheme might work :-)
>
> question is, would it be efficient, in terms of time of computation
> required, and would it be beautiful, in terms of code.  for the latter, at
> least, I believe not.
>
> the beautiful thing to do would be (I think) to put in some code such that
> the axis of rotation and the zero point of rotation can be defined not only
> absolutely, as they seem to be now, but as being alligned with some existing
> vertex (line between two points), or an existing point, respectively.  that
> would make the whole thing automatic, meaning that no extra code would have
> to be added by the user to manually update the position.
>
> for example, perhaps a new rotation engine could be coded that would accept
> as input a named point and line in the simulation, so that variation of the
> position and orientation of this named point and line would be taken into
> account.  in this way, 'rotations' of arbitrary complexity could be modeled,
> one extra line of code simulating the resulting action of one rotating
> motor.  or linear motor, or any other actuator.
>
> does such functionality yet exist?  I suspect not?  it depends on how many
> ways the vector3r can be defined.
>
> -mike
>
>
> --- On *Fri, 7/16/10, Václav Šmilauer <eudoxos@xxxxxxxx>* wrote:
>
>
> From: Václav Šmilauer <eudoxos@xxxxxxxx>
> Subject: Re: [Yade-users] hello? -help with a spinning bucket!
> To: yade-users@xxxxxxxxxxxxxxxxxxx
> Received: Friday, July 16, 2010, 4:23 AM
>
>
> > If you want to launch only one iteration, O.run(1) is better, O.iter
> > will give you only the number of current iteration, in python :
> >
> https://www.yade-dem.org/sphinx/yade.wrapper.html#yade.wrapper.Omega.iter
>
> Watch out, though, O.run(1) might return _before_ the iteration finishes
> (it launches thecomputation in background)! O.step() will wait. Or use
> O.run(1,True).
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-users<https://launchpad.net/%7Eyade-users>
> Post to     : yade-users@xxxxxxxxxxxxxxxxxxx<http://mc/compose?to=yade-users@xxxxxxxxxxxxxxxxxxx>
> Unsubscribe : https://launchpad.net/~yade-users<https://launchpad.net/%7Eyade-users>
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-users<https://launchpad.net/%7Eyade-users>
> Post to     : yade-users@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-users<https://launchpad.net/%7Eyade-users>
> More help   : https://help.launchpad.net/ListHelp
>
>