I’m trying to model surface adhesion and sliding contact between anatomical organs for aeva. These contacts relate side sets on 2 organs (e.g., femur and ACL) to each other. At the point in the workflow where users provide information on adhesion and contact,
- surface and volume components will have an attribute representing the organ they correspond to (e.g., femur, ACL, tibia) associated to them.
- side sets (additional components related to the surface and volume components by virtue of belonging to the same parent model) will have been created; they have an integer property marking them as side/node sets.
- an attribute for the adhesion or contact will already exist (the template file will be pre-populated with the contacts/adhesions to be modeled).
Is there a way to mark the adhesion/contact attribute-definition association rule so that
- only side sets tagged with a particular organ are shown in the user interface? At this point, I understand that there is no way to say “any component that has the side-set property and whose model contains a primary-geometry component associated with organ X.” That means users will have to associate the side set with the organ directly, but this should be simple. What I am asking is whether the association rules allow property checks (i.e., is the “side-set” property present?) and prerequisites (i.e., is the component already associated with organ X?) simultaneously.
- 1 or more side sets from each of the organs involved must be associated to be valid (i.e., associating 2 femur side sets is invalid, 2 ACL side sets is invalid, but 1 of each is valid as is 2 of each)?