Fields

Fields serve as loose wrappers around AbstractArray subtypes such that the size of array slices are known at compile time. Although this introduces a type-instability, the idea is to do this at the top most level (mainly at setup time of a FEM simulation). By introducing this type instability, we can gain information about the field type that is used in methods downstream to construct StaticArrays of views of field types.

All fields are subtypes of the abstract type AbstractField

julia> using FiniteElementContainers
julia> FiniteElementContainers.AbstractFieldFiniteElementContainers.AbstractField

Example - H1Field a.k.a. NodalField

We can set up a H1Field in one of two ways. The simplest constructor form can be used as follows

julia> using FiniteElementContainers
julia> field = H1Field(rand(2, 10))2×10 H1Field{Float64, Vector{Float64}, 2}:
 0.789222  0.111092  0.86737  0.032524  …  0.874654  0.563272  0.367348
 0.345447  0.514574  0.5717   0.745391     0.7002    0.837897  0.88648

This is stored in a vectorized way as can be seen above

julia> field.data20-element Vector{Float64}:
 0.7892222888404637
 0.3454467261182895
 0.11109169277113562
 0.5145736652052763
 0.8673695744972477
 0.5716998877539061
 0.03252399942416129
 0.7453905848764862
 0.018307059153824135
 0.4384428659255363
 0.7231743422050269
 0.6319646845416022
 0.9598294052158112
 0.7474769290043471
 0.8746543865907138
 0.7001999876242507
 0.5632718217727674
 0.8378966413703612
 0.3673479877490372
 0.8864795707347821

Fields can be indexed like regular arrays, e.g.

julia> field[1, 1]0.7892222888404637

julia> field[1, :]10-element Vector{Float64}:
 0.7892222888404637
 0.11109169277113562
 0.8673695744972477
 0.03252399942416129
 0.018307059153824135
 0.7231743422050269
 0.9598294052158112
 0.8746543865907138
 0.5632718217727674
 0.3673479877490372

etc.

Abstract type

The base type for fields is the AbstractField abstract type.

abstract type AbstractField{T, N, D<:AbstractArray{T, 1}, NF} <: AbstractArray{T, N}

Any new field added to FiniteElementContainers should be a subtype of this type.

Methods for AbstractField

fill!(
    field::FiniteElementContainers.AbstractField{T, N, D, NF},
    v
) -> Any

num_fields(
    _::FiniteElementContainers.AbstractField{T, N, D, NF}
) -> Any

get_backend(
    field::FiniteElementContainers.AbstractField
) -> Any

Implementations

The existing direct subtypes of AbstractField are the following

Connectivity

The connectivity type is a simple alias for L2ElementField defined below

struct L2ElementField{T, D, NF} <: FiniteElementContainers.AbstractField{T, 2, D, NF}

connectivity(
    conn::L2ElementField,
    e::Int64
) -> SubArray{T, 1} where T

connectivity(conn::L2ElementField) -> Any

H1 field

struct H1Field{T, D, NF} <: FiniteElementContainers.AbstractField{T, 2, D, NF}

H1Field(data::AbstractMatrix) -> H1Field

num_nodes(field::H1Field{T, D, NF}) -> Any

L2Element field

struct L2ElementField{T, D, NF} <: FiniteElementContainers.AbstractField{T, 2, D, NF}

L2ElementField(data::AbstractMatrix) -> L2ElementField

num_elements(field::L2ElementField{T, D, NF}) -> Any

num_nodes_per_element(field::L2ElementField) -> Any

L2Quadrature field

struct L2QuadratureField{T, D, NF, NQ} <: FiniteElementContainers.AbstractField{T, 3, D, NF}

There are plans to add HcurlField and HdivField types as well