I realized the change when my scripts crashed. I have many scripts using this and no time to learn and convert all of them to the type of energy tracing you implemented. This is one reason.
Cpu time is another reason (else I would have keep this change in local). It seems that track energy will compute all types of energy at each iterations while I need only a few of them and not at each iteration. I also got the impression that comparing strings in energy->add(dissip,"plastDissip",...), and calling those python functions is a lot more expensive than a single plasticE+=. Not sure. Also, I didn't know : do track energy work in parallel? 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... Did you validate this new energy tracking? Cheers. Bruno > >> - 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 : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
