Work in progress

This page is a work in progress.

It was published in this state to make existing content available to users and highlight missing parts to contributors.

Contributors: please see Documentation Contribution Guide to contribute to the documentation.

Users: the content of this page has been verified and is correct. Please return later for more content!

This block can be used to define one or more …

They can be accessed from within <type>Curve</type> or <type>CurveScaled</type> parameters (more details on curves and curves scaled).

Following variables are accessible from CurveScaled:

  • spatial: x, y, z
  • temporal: t


Curves can be defined using the following block:

            x_1 x_2 ... x_n
            y(x_1) y(x_2) ... y(x_n)

and can be called in “Properties” and “Parameters” inside “Expression”: CurveName(evaluation_value)

where evaluation_value is always exactly one value and refers to values provided inside <coords> </coords>. In the <expression>s using curves, time $t$ and global coordinate $x$, $y$, and $z$ can be used, and passed as curve’s argument for example:

    <expression>2000 - CurveName(x^2 + y^2) * TimeDependentCurve(t)</expression>

Curves can be useful to include information on variation of time dependent parameters. Those values can be called from the ’equation’ tag in ‘parameter’ if ’type’ ‘formula’ is selected.


Curve represents a piece-wise linear function – the values between coordinates are interpolated linearly though. Outside of the curve’s range of definition the curve becomes a constant using the first value on the left and last value on the right.

This article was written by Feliks Kiszkurno. If you are missing something or you find an error please let us know.
Generated with Hugo 0.122.0 in CI job 437561 | Last revision: April 3, 2024
Commit: [PL/CT] Pass shape matrix cache to local assemblers of ComponentTransport 845cbb1  | Edit this page on