The purpose of behaviour bricks is to hide (by default) part of the behaviour implementation. In other word, they are meant to create a context which simplifies the implementation of some specific behaviours’ classes.
The easiest way to introduce behaviour bricks is to shortly describe
the example of the StandardElasticity brick. This brick
applies to strain based mechanical behaviours. It assumes:
With those assumptions, the StandardElasticity brick can
automatically provide:
@Brick keywordThe @Brick keyword introduces a behaviour brick. It is
followed by the name of the brick. This name can be given as a
string.
@Brick "StandardElasticity"{
young_modulus: 150e9,
poisson_ratio: 0.3
};The following brick are available:
StandardElasticity brick, which has been described
in the introduction of this page. In practice, the evolution of
MFront and the development of the
StandardElastoViscplasticity brick, has made the
StandardElasticity brick a kind of special case of the
StandardElastoViscoplasticity where the stress potential is
limited to the Hooke’s one and no inelastic flow is allowed. As such,
most information concerning the StandardElasticity brick
can be found on the page dedicated to the Hooke stress potential. In
particular, all options passed to the StandardElasticity
brick are indeed forwarded to the underlying Hooke stress
potential.DDIF2 brickStandardElastoViscoplasticity
brickFiniteStrainSingleCrystal