Question #682755 on Yade changed: https://answers.launchpad.net/yade/+question/682755
Jérôme Duriez proposed the following answer: Hi, It seems the YADE variables you spoke about can be accessed by users in a read-write manner, then: 1- b.state = JCFpmState() # will assign a JCFpmState instance with default attributes to any body b. This being said, the expected workflow, from a user point of view, is more to assign JCFpmMat materials to your bodies, call the appropriate engines to apply JCF contact law, then just rely on those engines for JCFpmState to appear in your simulation, without any further action. 3- i.phys.jointNormal = (1,0,0) # will modify the jointNormal attribute of an existing JCF interaction "i" However, this is again not really expected in general. What attributes of JCFpmPhys (and why) would you like to change ? As for 2- Introducing a joint into one sphere does not make sense in YADE JCFpm logic. You need to have interactions (2 spheres at least) to speak about joint. You have (two ! gravityLoading.py is using an external description of the joint in stl format, gravityBis.py defines within YADE, with gts module, the joint) examples about defining joint geometries in folder [1] in Luc's answer #1. -- You received this question notification because your team yade-users is an answer contact for Yade. _______________________________________________ Mailing list: https://launchpad.net/~yade-users Post to : [email protected] Unsubscribe : https://launchpad.net/~yade-users More help : https://help.launchpad.net/ListHelp
