yade-dev team mailing list archive

[Václav Šmilauer <eu@xxxxxxxx>]

Hi, the code was always working, and still should be, in
NewtonIntegrator.pp:208 (and 2 other lines for rotations) I read

   if (scene->forces.getMoveRotUsed())
state->pos+=scene->forces.getMove(id);

It was supposed to impose displacement or rotation change directly, and
to do it in a way which is thread-safe; changing b.vel may affect other
computations going on in that timestep, plus it usually supposes that dt
does not change between steps (not always the case). But I see there is
only little use for it, and I would have to remember hard what was the
reason to introduce it back then. There must have been one :)

@Jan, do you have NewtonIntegrator in engines?

-- 
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1400075

Title:
  O.forces.addMove does not work

Status in Yet Another Dynamic Engine:
  New

Bug description:
  Hi,

  I tried O.forces.addMove to apply displacement to a particle, but the
  method seems not to work..

  b = sphere((0,0,0),1)
  O.bodies.append(b)
  O.forces.addMove(0,(1,0,0))
  print b.state.pos # (0,0,0)
  O.step()
  print b.state.pos # is (0,0,0) again...

  Is this behavior ok, do I do something wrong or is it a bug?

  I use Ubuntu 14.04 and yade  2014-11-08.git-d693417

  Thanks
  Jan

To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1400075/+subscriptions