- Member basix::FiniteElement::FiniteElement (element::family family, cell::type cell_type, int degree, const std::vector< std::size_t > &value_shape, const xt::xtensor< double, 3 > &coeffs, const std::vector< xt::xtensor< double, 2 >> &entity_transformations, const std::array< std::vector< xt::xtensor< double, 2 >>, 4 > &x, const std::array< std::vector< xt::xtensor< double, 3 >>, 4 > &M, maps::type map_type=maps::type::identity)
- Document A finite element
- Member basix::FiniteElement::map_pull_back_m (const xt::xtensor< T, 3 > &u, const xt::xtensor< double, 3 > &J, const tcb::span< const double > &detJ, const xt::xtensor< double, 3 > &K, E &&U) const
- Weirdly, the u and U Map function values from a physical cell to the reference
- Member basix::moments::make_dot_integral_moments (const FiniteElement &V, cell::type celltype, std::size_t value_size, int q_deg)
- Clarify what happens value size of the moment space is less than
value_size
.
- Member basix::polyset::tabulate (cell::type celltype, int d, int n, const xt::xarray< double > &x)
- Does the order for the third index need to be documented?
- Namespace basix::quadrature
- - pyramid