Not clear to me what you need. postLoad is called after you instantiate
the object from python (not from c++), when all attributes are already
set.
Instantiating the object (chainedState) is not enough to define all the info
needed in
that case.
The object must be placed in a chain first
revno: 2589
committer: Bruno Chareyre bruno.chare...@hmg.inpg.fr
branch nick: yade
timestamp: Mon 2010-12-06 12:54:38 +0100
message:
- PeriTriax : remove the constant-distance approximation in stress
definition, using wrapped
Hi,
For info : there is a small fix of stress definition in periodic BCs in
revision 2589 that
slightly modify energy results.
- Before fix, the (normalized) diff between total energy and boundary work was
around 5e-3
(0.5%) for a compression εyy=0.1 (~60k iterations), as in attachment of
- There used to be some physical parameters (cohesion and others) in
Ip2_2xCohFrictMat_CohFrictPhys, but I recently moved them all to FrictMat.
If you have a
moment, could you please do the same for alphas and etaRoll (and probably
harmonic-average
them in the functor)? Only flags should be
Ok, Bruno. So I will wait for your suggestions.
Thanks for letting me know,
Chiara
On 6 December 2010 16:46, Bruno Chareyre bruno.chare...@hmg.inpg.fr wrote:
Chiara,
There is something ringing in my head now that ktwist!=kroll. There is
something I need to
double-check in the rotations
can I use the MatchMaker to get the harm average of alphas parameter?
I am not sure to understand how it works.
Cheers, Chiara
Hi, yes you can... You will turn (if we speak about
Ip2_2xCohFrictMat_CohFrictPhys) alphaKr, alphaKts into MatchMaker
objects, which will by default return constant
06.12.2010 21:05, Václav Šmilauer пишет:
I was looking at the State class, and it seems to me some attributes
(below) are not needed.
Any reason to not get rid of them?
I don't think we need accel and angAccel (grep the code to make sure,
however), so you can go ahead I think. For refPos and
For accel and angAccel see NewtonIntegrator.
Yes, but they are computed and consumed within one loop, so they could
be stored in local vars (though it would need some care to not break
what is there now).
___
Mailing list:
For refPos and refOri, they are
used in the rendering code and some other functions. While you are
cleaning up, there is also superfluous FrictPhys.frictionAngle (only the
tangent is needed in computations I would think). v.
Ok, I see. It is for scaling displacements (otherwise useless I
On 06/12/10 19:59, Bruno Chareyre wrote:
For refPos and refOri, they are
used in the rendering code and some other functions. While you are
cleaning up, there is also superfluous FrictPhys.frictionAngle (only the
tangent is needed in computations I would think). v.
Ok, I see. It is for
Assuming I'll reach such a low level in the todo list (unlikely), ok to move
refPos/Ori
between some #ifdef YADE_OPENGL guards?
I recall now there are also some post-processing functions (in post2d)
that use reference positions... Let's perhaps discuss that again if you
get that far on you
revno: 2590
committer: Bruno Chareyre bruno.chare...@hmg.inpg.fr
branch nick: yade
timestamp: Mon 2010-12-06 20:24:20 +0100
message:
- Cylinders : handle cylinder-sphere contacts with a fictious state
representing interpolated motion
I've been commiting a lot of empty lines lately, I don't know why. Sorry for
that.
I wish I could identify the reason (I've not been doing any sort of
auto-formating in e.g.
utils.py).
B.
On 06/12/10 20:26, nore...@launchpad.net wrote:
revno: 2591
committer: Václav Šmilauer e...@doxos.eu
branch nick: yade
timestamp: Mon 2010-12-06 21:05:12 +0100
message:
1. Add MatchMaker(Real) ctor
2. Adjust timing report format for batch (precision)
modified:
- Get back standalone energy tracing in ECL.
Out of interest: what was the reason for that?
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-dev
More help :
The less rational reason is I knew my scripts conserve energy, while
everything else I see
on yade lists seem to eat energy somehow. I was a bit afraid to change my
usual
practice...
Bruno, what is this usual practice? Sorry but I am interested in since I
spent so much time on it and could
It is probably easy to create a proxy function, but I don't know how honestly
+ checking
that equations are the same, yes I could have... But when the initial objective
is to fix
one line in PeriTriax, it means work time is multiplied by 10 at least.
As for cpu time being no big deal... it is
The less rational reason is I knew my scripts conserve energy, while
everything else I see
on yade lists seem to eat energy somehow. I was a bit afraid to
change my usual
practice...
Bruno, what is this usual practice? Sorry but I am interested in since I
spent so
On Tue, Dec 7, 2010 at 12:00 AM, nore...@launchpad.net wrote:
revno: 2592
...
2. Add scripts/test/beam-l6geom.py to demonstrate L6Geom
3. Fix LawTester so that ti works with all 6 dofs reliably now
...
Cool!
19 matches
Mail list logo
