> > 1. I used neverErase flag, because something goes wrong when > interaction breaks. So do not delete it, but only reset Fn=0 and Fs=0. >
> > [Law2_ScGeom_FrictPhys_Basic(label='dry',traceEnergy=True,neverErase=True)] > Good Janek, so you agree there something unexpected is happening once calling the function requestErase(). Potential interactions seem somehow not deleted and I do not know if this can have any consequence somehow. We should definitely check that function which almost every contact law is using, most importantly. > > the neverErase flasg shouldn't change anything in the resulting > graphs of total energy. But evidently it helps! So this is a BUG #1 here. > > plasticDissipation += > (-shearDisp - > (1/currentContactPhysics->ks)*(trialForce-shearForce))//plastic disp. > .dot(shearForce);//active force > This is weird because as I already said to me plasticDissipation code looks right as it is. I would not be able to prove on paper why the addition of shearDispl increment. > > _______________________________________________ > Mailing list: > https://launchpad.net/~yade-users<https://launchpad.net/%7Eyade-users> > Post to : [email protected] > Unsubscribe : > https://launchpad.net/~yade-users<https://launchpad.net/%7Eyade-users> > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~yade-users Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
