yade-dev team mailing list archive

[Bruno Chareyre <1300167@xxxxxxxxxxxxxxxxxx>]

>I could fix it
This engine has been introduced before effective integration of python.
Is it doing something that can't be done with python?

Your case with this bug was typical. You could:
1/ type a few python lines to do exactly what you want, or
2/ learn how to use an engine, try it, realize that it is not doing what you think it would do, find a bug, report, get feedback, start fixing
Coming soon: commit, push, get feedback again, etc.

If this engine is removed you will:
1/ type a few python lines to do exactly what you want
Less compilation time for us all, less maintainance, less noise on the mailing list.

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

Title:
  (Not) Defining velocities in UniaxialStrainer ?

Status in Yet Another Dynamic Engine:
  New

Bug description:
  Hi,

  I have the feeling that there is something "wrong" with
  UniaxialStrainer where the velocities of the "posIds" and "negIds"
  bodies are not defined, and I illustrate it with following examples
  (attached)

  It deals with 2 contacting spheres, with an oblic contact. One sphere is moved towards the 2d sphere, and here both normal and tangential relative displacements occur. 
  - In testUS.py the moving sphere is moved through UniaxialStrainer
  - Whereas in testUSb.py the movement comes from an initial value of velocity (and NewtonIntegrator)

  And, obviously, the two simulations are different (see e.g. the plot
  of fZ sustained by moving sphere). While I would tend to consider
  these two simulations as identical.

  What do you think ?

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