For the record, I'm herein attaching a patch that would make aabbExtrema() back to a tuple, cancelling the effects of commits 1db13fb ( = [*] in the bug report) and 7c60d78 ( = more recent commit mentioned in #2)
As of now, I do not think this patch should be applied, see other comments regarding the (lack of) detected problems ** Patch added: "patch.diff" https://bugs.launchpad.net/yade/+bug/1804621/+attachment/5216535/+files/patch.diff -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1804621 Title: bodyNumInteractionsHistogram broken Status in Yade: New Bug description: See https://answers.launchpad.net/yade/+question/676284 and: ##################### O.bodies.append(sphere((0,0,0),1,dynamic=False)) O.bodies.append(sphere((0,0,1.9),1,dynamic=False)) O.step() print 'BodyNumInteractions Histogram', bodyNumInteractionsHistogram(aabbExtrema()) #################### which returns (with trunk version) : ArgumentError: Python argument types in yade._utils.bodyNumInteractionsHistogram(list) did not match C++ signature: bodyNumInteractionsHistogram(boost::python::tuple aabb, bool contactOnly=False) because my commit [*] changed the Python return type of aabbExtrema() from tuple to list. Possible (and easiest) fix would be to change all corresponding py::tuple aabb from py::list aabb. Agree ? Or do we want this function to deal with Python tuples and not lists ?.. Jérôme [*] https://github.com/yade/trunk/commit/1db13fb1183b9e294dc9761da76cfa4fc2791cc1 To manage notifications about this bug go to: https://bugs.launchpad.net/yade/+bug/1804621/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
