Again, without attachments. Find them here:
http://beta.arcig.cz/~eudoxos/yade/shear-displacement.pdf and
http://beta.arcig.cz/~eudoxos/yade/shear-slip.pdf
===
> (A) - maxUn (and other extrema of the variables contained in IntGeom,
> including initial orientations) in IntPhysics is ok with me.
You can always derive from the geometry class and add your own data
members. But you still have access to inherited data members and
methods, should you need those. maxUn can (should) be stored in
InteractionPhysics, the same for cell volume, no?
(A) - maxUn (and other extrema of the variable
>> I don't use torsion and bending, but for the shear part,
>> I never got the incremental algo to match with what small-strain FEM
>> code computes for strains (production code, therefore assumed to be
>> correct).
> It is not the first time I read this but I must admit I never
> understodd w
Hi, it is probably question directed at me. Torsion, bending, but also
shear code is implemented as incremental computation from angular
velocities etc.
Only shear motion is defined in an incremental form. Torsion/bending is
relative to the initial positions.
I don't use torsion and bending
> * TODO: add torsion code, that will (if a flag is on) compute torsion
> angle on the contact axis.
> *
> * TODO: add bending code, that will compute bending angle of the
> contact axis
>
> The code for this is in CohesiveFrictionalContactLaw already, its been
> developped by Cosurgi.
Hi, it is p
Hi
I see an inflation in the amount of members in this class.
This class should be very simple, with no excess parameters for all
those using the traditional Cundall's contact law.
Which means, this class should have only rad1, rad2, penetrationDepth
and normal, nothing more (except perhaps Con
6 matches
Mail list logo
