Emily Boudreaux
6b57738330
Note for now much of the docs is LLM written. This was done to save time and focus on code development. The docs have been LOOSLEY reviewed. However, the code itself has been either fully written by hand or fully reviewed. Therefore, the docs should at the moment be seen as a loose resource rather than authoratiative (and this is on top of the general ability for docs to drift)
26 lines
1.1 KiB
Groff
26 lines
1.1 KiB
Groff
.TH "serif::discretization::backend::mfem::BoundaryTraceTerm" 3 "Version v0.0.1a" "SERiF" \" -*- nroff -*-
|
|
.ad l
|
|
.nh
|
|
.SH NAME
|
|
serif::discretization::backend::mfem::BoundaryTraceTerm \- Concept Limiting the input term to either a global scalar term or a spatial term of rank 0 in the H1 family\&. Outside of H1, the trace is a vector (e\&.g\&. the normal trace for a H(div) field or the tangential trace for a H(curl) field)\&. Further, for higher rank H1 fields the trace is a tensor\&.
|
|
|
|
.SH SYNOPSIS
|
|
.br
|
|
.PP
|
|
.PP
|
|
\fR#include <boundary_trace\&.hpp>\fP
|
|
.SH "Concept definition"
|
|
.PP
|
|
|
|
.nf
|
|
template<typename TermT>
|
|
concept serif::discretization::backend::mfem::BoundaryTraceTerm = blocks::ScalarTraceTerm<TermT>
|
|
.PP
|
|
.fi
|
|
.SH "Detailed Description"
|
|
.PP
|
|
Concept Limiting the input term to either a global scalar term or a spatial term of rank 0 in the H1 family\&. Outside of H1, the trace is a vector (e\&.g\&. the normal trace for a H(div) field or the tangential trace for a H(curl) field)\&. Further, for higher rank H1 fields the trace is a tensor\&.
|
|
.SH "Author"
|
|
.PP
|
|
Generated automatically by Doxygen for SERiF from the source code\&.
|