Functions
AbstractFunctions are used to represent elements of FunctionSpaces.
API
FiniteElementContainers.AbstractFunction — Type
abstract type AbstractFunction{F, NF}FiniteElementContainers.AbstractScalarFunction — Type
abstract type AbstractScalarFunction{F} <: FiniteElementContainers.AbstractFunction{F, 1}FiniteElementContainers.ScalarFunction — Type
struct ScalarFunction{F} <: FiniteElementContainers.AbstractScalarFunction{F}fspace::Anynames::Tuple{String}
FiniteElementContainers.SymmetricTensorFunction — Type
struct SymmetricTensorFunction{F, NF} <: FiniteElementContainers.AbstractFunction{F, NF}fspace::Anynames::Tuple{Vararg{String, NF}} where NF
FiniteElementContainers.SymmetricTensorFunction — Method
SymmetricTensorFunction(
fspace::FunctionSpace,
sym::String;
use_spatial_dimension
) -> SymmetricTensorFunction
Uses numbering consistent with exodus output, is this the right thing to do? Should it be consistent with Tensors.jl
FiniteElementContainers.TensorFunction — Type
struct TensorFunction{F, NF} <: FiniteElementContainers.AbstractFunction{F, NF}fspace::Anynames::Tuple{Vararg{String, NF}} where NF
FiniteElementContainers.TensorFunction — Method
TensorFunction(
fspace::FunctionSpace,
sym::String;
use_spatial_dimension
) -> TensorFunction
FiniteElementContainers.VectorFunction — Type
struct VectorFunction{F, NF} <: FiniteElementContainers.AbstractFunction{F, NF}fspace::Anynames::Tuple{Vararg{String, NF}} where NF
Base.length — Method
length(
func::FiniteElementContainers.AbstractFunction
) -> Any
Base.names — Method
names(func::FiniteElementContainers.AbstractFunction) -> Any