yade-dev team mailing list archive

[chareyre <bruno.chareyre@xxxxxxxxxxx>]

Ok for material vs. body state. As long at it doesn't prevent one 
from defining N different material parameters for N bodies (it will 
happen sooner than never, imagine a random distribution of elastic 
properties of particles).


>Note for Vincent: interactions will still have all their properties
>inside them (like stiffness, frictionAngle etc computed from materials).

>There is probably not much to do about it -- except for deriving those
>constant parameters that depend only on material beforehand and can be
>shared between interactions, for all possible (/requested) combinations
>of materials, perhaps using something like GroupRelationData. In that
>case InteractionPhysics (interactionState??) would hold something like
>interactionParametersId, with container of a few shared "cross-section"
>characteristics (rigidity, frictionAngle etc).

I confirm that there is not much to do about it. The only parameter 
that is common to all sphere-sphere interactions in my simulations 
is the friction angle (and still, I am not sure I will not decide 
one day that a fraction of them should have a different value). Stiffness 
are all different (because they depend on particles diameters, and 
I don't want to recompute them at each step).

Actually, one of the most annoying feature when I was using PFC was 
that you couldn't define interactions properties for individual contacts,
precisely because contact b1-b2 stiffness was always a function 
of stiffnesses of b1 and b2. In Yade, we have more versatility, precisely 
because we have parameters defined per interaction. We don't want 
to loose this.
Bruno





===================================================================
EASY and FREE access to your email anywhere: http://Mailreader.com/
===================================================================