Hi Bruno I think in terms of performance it might be better to keep MatchMaker in IP2 rather to add some in the Law functor. Further I think maybe we could get rid of includeMoment=True/False in the Law functor.
My suggestion is MatchMaker for eta, krot and ktwist. This makes as well more sense if looking at the use of various materials. includeMoment can then be set by the Ip2 functor (it can be an internal variable of the Ip2) by checking if krot or ktwist are defined. What do you think about this suggestion? If you are happy I would try it? Cheers Klaus On Wednesday 28 August 2013 16:41:37 Bruno Chareyre wrote: > > BTW, don't you think it would make sense to make MatchMakers for most of > > the parameters in the IP2 functors? It would give more flexibility when > > working with different materials. > > It would surely make sense. > It has not done because it is tedious work to put them everywhere. So, > they have been included on a case by case basis when someone needed such > flexibility for a non-trivial situation. > Another question is performance. I don't know if the impact is > completely negligeable. > > Bruno > > > _______________________________________________ > Mailing list: https://launchpad.net/~yade-dev > Post to : [email protected] > Unsubscribe : https://launchpad.net/~yade-dev > More help : https://help.launchpad.net/ListHelp -- Dr. Klaus Thoeni - Centre for Geotechnical and Materials Modelling Civil, Surveying and Environmental Engineering - Engineering Building EA The University of Newcastle, Callaghan, NSW 2308, Australia web: http://www.newcastle.edu.au/research-centre/cgmm phone: +61 (0)2 4921 5735 _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
