yade-dev team mailing list archive

[Jérôme Duriez <jerome.duriez@xxxxxxxxxxx>]

Ok, I will take care of it, sooner or later. Moreover the sign,
behaviour of TriaxialStressController.strain is a bit akward to
understand (at least before this issue is understood) ... See the
attached (minimal) script, that illustrate two following questions :

- would it not be usefull to initialize strain as Vector3::Zero in constructor ?
- is this behaviour (because of the &TriaxialStressController::strain in the code ?) of "strain" python attribute really desirable ? 

** Changed in: yade
     Assignee: (unassigned) => Jérôme Duriez (jduriez)

-- 
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1381282

Title:
  Sign convention in TriaxialStressController not consistent ?

Status in Yet Another Dynamic Engine:
  New

Bug description:
  Hi,

  When used as stress or strain rates, sign convention of "goal1/2/3"
  attributes of TriaxialStressController engine seem to me as not
  consistent.

  Positive values for stress goals correspond indeed to compression, whereas positive values for goal strain rates involve extension.
  Which is itself not consistent with TriaxialStressController.strain variable (in the end, to obtain positive TriaxialStressController.strain, you need to set negative strain rates goal variables).

  Not difficult to fix, but maybe require a common decision. (I vote
  myself for geomechanics convention)

To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1381282/+subscriptions