1 New TFEL/Math features

1.1 tiny matrices product

The product of two tiny matrices has been implemented:

const auto m1 = tmatrix<2u, 2u, int>{0, 1,  //
                                     2, 3};
const auto m2 = tmatrix<2u, 2u, int>{4, -1,  //
                                     5, 2};
const auto m3 = m1 * m2;

1.2 Symmetric tensor eigen values and eigen vectors

• New eigen solvers have been introduced.

1.2.1 New eigen solvers

New eigen solver based on Harari analytical solution have been introduced for symmetric tensors. The computation of eigen values is done with Harari’s algorithm [1] and the computation of eigen vectors is done with the default eigen solver for symmetric tensors of TFEL. Such computations are more efficient and more accurate than the default TFEL algorithm.

Those algorithms are available in 3D. For 2D symmetric tensors, we fall back to some default algorithm as described below.

The various eigen solvers available are enumerated in Table 1.

The eigen solver is passed as a template argument of the computeEigenValues or the computeEigenVectors methods as illustrated in the code below:

tmatrix<3u,3u,real> m2;
tvector<3u,real>    vp2;
std::tie(vp,m)=s.computeEigenVectors<stensor::HARARIEIGENSOLVER>();

1.2.1.1 Some benchmarks

We have compared the available algorithm on \(10^{6}\) random symmetric tensors whose components are in \([-1:1]\).

For a given symmetric tensor, we consider that the computation of the eigenvalues and eigenvectors failed if: \[ \Delta_{\infty}=\max_{i\in[1,2,3]}\left\|\tenseur{s}\,\cdot\,\vec{v}_{i}-\lambda_{i}\,\vec{v}_{i}\right\|>10\,\varepsilon \] where \(\varepsilon\) is the accuracy of the floatting point considered.

The results of those tests are reported on Tables 2, 3 and 4. The Harari eigen solver offers a better compromise between accuracy and numerical efficiency than the default TFEL solver.

2 MFront

2.1 Improvements to the MaterialProperty DSL

2.1.1 The @Data keyword

The @Data keyword allow the definition of a material properties using the interpolation of a set of values.

The @Data keyword is followed by a set of options defining:

• the interpolation option,
• the set of values,
• the extrapolation option.

The precise syntax depends on the number of inputs of the material property.

2.1.1.1 Material properties without input

The only option accepted is value.

2.1.1.2 Material properties with only one input

The values option is required. It must be a map associating values of the input and values of the output.

The interpolation option is optional. It must be a string. The values linear and cubic_spline are accepted.

The extrapolation option is optional. It must be a boolean or a string:

• The boolean value true means that a linear extrapolation will be performed.
• The boolean value false or the string value bound_to_last_value or the string value constant means that a constant value will be used for extrapolation.

2.1.1.3 Example of usage

@DSL MaterialProperty;
@Law LinearDataInterpolation;

@UseQt true;
@UnitSystem SI;

@Output stress E;
E.setGlossaryName("YoungModulus");

@StateVariable temperature T;
T.setGlossaryName("Temperature");

@Data {
  values: { 293.15 : 240e9, 693.15 : 180e9, 893.15 : 170e9 },
  interpolation : "linear"
}

2.2 generic interface improvements

2.2.1 The @SelectedModellingHypothesis and @SelectedModellingHypotheses keywords

The @SelectedModellingHypothesis and @SelectedModellingHypotheses keywords allows to select which modelling hypotheses will be generated.

Their syntaxes are similar to the keywords @ModellingHypothesis and @ModellingHypotheses, respectively.

The selected modelling hypotheses must be a sub-set of the modelling hypotheses supported by the behaviour.

2.2.1.1 Example of usage

$ mfront --obuild --interface=generic --@SelectedModellingHypothesis=PlaneStrain Plasticity.mfront
Treating target : all
The following library has been built :
- libBehaviour.so :  Plasticity_PlaneStrain

3 Documentation

The page Libaries usage in C++ describe how to use the TFEL libraries in C++ projects, using either the tfel-config utility or cmake packages.

4 Issues fixed

4.1 Issue 582: [cast3m interface] add explicit names and 4-letter mapping of internal variables to the castem file

Adds the correspondence between variable names and the 4-letter names used in castem to the example .dgibi file, generated by MFront with castem interfaces. The mapping is written in the file as a comment, for example in the form :

** List of material properties:
**
** - YOUN: YoungModulus
** - NU: PoissonRatio
** - RHO: MassDensity
** - H: HardeningSlope
** - SO: Yield strength

For more details, see https://github.com/thelfer/tfel/issues/582

4.2 Issue 585: mfront Allow to override inputs in material properties

$ mfront-query --state-variables Inconel600_YoungModulus.mfront 
- Temperature (TK): the temperature
$ mfront-query --parameters Inconel600_YoungModulus.mfront

$ mfront-query --state-variables --dsl-option='overriding_parameters:{"TK": 400}}' Inconel600_YoungModulus.mfront
$ mfront-query --parameters --dsl-option='overriding_parameters:{"TK": 400}}' Inconel600_YoungModulus.mfront
- Temperature (TK): the temperature

For more details, see https://github.com/thelfer/tfel/issues/585

4.3 Issue 567: MTestCurrentState.copy() produces a shallow copy in python bindings

This behaviour is consistent with the copy constructor of the StudyCurrentState class.

To make a deep copy of this object, the makeDeepCopy method has been introduced.

For more details, see https://github.com/thelfer/tfel/issues/567

4.4 Issue 557: [mfront] allow to specify dsl options in MFrontBase::getDSL

For more details, see https://github.com/thelfer/tfel/issues/557

4.5 Issue 556: [cmake] export compile flags in dedicated variables

For more details, see https://github.com/thelfer/tfel/issues/556

4.6 Issue 555: [cmake] better handling of dependencies in exported cmake files

For more details, see https://github.com/thelfer/tfel/issues/556

4.7 Issue 526: The @UseQt keyword is not mentioned in the MaterialLaw’s keywords help page

For more details, see https://github.com/thelfer/tfel/issues/526

4.8 Issue 476: [generic interface] Add support for arrays of thermodynamic forces

For more details, see https://github.com/thelfer/tfel/issues/476