> > I also hope that such generic interactions will reduce code duplication > > (for instance, there is unbalancedForce computation in Triaxial, but now > > it can use this function). > > > Very good. I get it you modified the class hierarchy, or NormalShearI > has been here for a while and I didn't notice?
No, that is quite a recent addition, mainly because of SDECLinkPhysics vs. other very similar classes; I also hope it will accelerate getting rid of persistentInteractions and consolidate some other code. > Agreed. Two main reasons for current situation : > 1. I tried to comply with Yade design - in a stupid way maybe. > 2. Global stiffness is (probably more "could" or "should", in fact...) > also used to control the stress on walls. So the stiffness data is a bit > more general than just timestep computing. > > One more reason to merge : if somebody makes the mistake of setting > different intervals in counter and timestepper, it could result in a > strange behaviour, perhaps uninitialized values, etc. Go ahead with that, I think that will be much friendlier, indeed. Vaclav _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
