[Yade-dev] [svn] r1668 - in trunk: examples/dynamic_simulation_tests gui/py

2009-02-17 Thread sega at BerliOS
Author: sega Date: 2009-02-17 10:10:50 +0100 (Tue, 17 Feb 2009) New Revision: 1668 Modified: trunk/examples/dynamic_simulation_tests/ringSimpleViscoelastic.py trunk/gui/py/utils.py Log: Merging utils.*_v2 functions with their first analogs. Modified:

Re: [Yade-dev] shared_ptrPhysicalAction

2009-02-17 Thread Janek Kozicki
Václav Šmilauer said: (by the date of Tue, 17 Feb 2009 08:38:07 +0100) Hi there, any reason PhysicalActionContainer contains shared_ptr's? Wouldn't it be better to contain just array of PhysicalActions? It would allow for very fast resetting with memset(action[0],0,sizeof(thisAction)) and

Re: [Yade-dev] shared_ptrPhysicalAction

2009-02-17 Thread Janek Kozicki
Václav Šmilauer said: (by the date of Tue, 17 Feb 2009 13:48:55 +0100) memset(action[0],0,sizeof(thisAction)) and perhaps would save some shared_ptr overhead we have currently. V. feel free to experiment. you could try memset(.get(),0,sizeof(thisAction));

Re: [Yade-dev] Question about parameters in SpheresContactGeometry

2009-02-17 Thread Bruno Chareyre
Hi, it is probably question directed at me. Torsion, bending, but also shear code is implemented as incremental computation from angular velocities etc. Only shear motion is defined in an incremental form. Torsion/bending is relative to the initial positions. I don't use torsion and

Re: [Yade-dev] shared_ptrPhysicalAction

2009-02-17 Thread Bruno Chareyre
Václav Šmilauer a écrit : Hi there, any reason PhysicalActionContainer contains shared_ptr's? Wouldn't it be better to contain just array of PhysicalActions? It would allow for very fast resetting with memset(action[0],0,sizeof(thisAction)) and perhaps would save some shared_ptr overhead we have

[Yade-dev] [svn] r1670 - trunk/pkg/common/Engine/StandAloneEngine

2009-02-17 Thread eudoxos at BerliOS
Author: eudoxos Date: 2009-02-17 21:49:02 +0100 (Tue, 17 Feb 2009) New Revision: 1670 Modified: trunk/pkg/common/Engine/StandAloneEngine/PersistentSAPCollider.cpp Log: collider mistake hotfix Modified: trunk/pkg/common/Engine/StandAloneEngine/PersistentSAPCollider.cpp

Re: [Yade-dev] Question about parameters in SpheresContactGeometry

2009-02-17 Thread Bruno Chareyre
You can always derive from the geometry class and add your own data members. But you still have access to inherited data members and methods, should you need those. maxUn can (should) be stored in InteractionPhysics, the same for cell volume, no? (A) - maxUn (and other extrema of the