SpECTRE  v2026.04.01
Loading...
Searching...
No Matches
elliptic::dg::MortarData< TemporalId, PrimalFields, PrimalFluxes > Struct Template Reference

Boundary data on both sides of a mortar. More...

#include <DgOperator.hpp>

Additional Inherited Members

Public Member Functions inherited from dg::SimpleMortarData< TemporalId, BoundaryData< PrimalFields, PrimalFluxes >, BoundaryData< PrimalFields, PrimalFluxes > >
SimpleMortarDataoperator= (const SimpleMortarData &)=default
std::pair< BoundaryData< PrimalFields, PrimalFluxes >, BoundaryData< PrimalFields, PrimalFluxes > > extract ()
 Return the inserted data and reset the state to empty.
void pup (PUP::er &p)
const BoundaryData< PrimalFields, PrimalFluxes > & local_data (const TemporalId &temporal_id) const
 Retrieve the local data at temporal_id
const BoundaryData< PrimalFields, PrimalFluxes > & remote_data (const TemporalId &temporal_id) const
 Retrieve the remote data at temporal_id
size_t integration_order () const
 These functions do nothing. They exist for compatibility with BoundaryHistory.
void local_insert (TemporalId temporal_id, BoundaryData< PrimalFields, PrimalFluxes > vars)
 Add a value. This function must be called once between calls to extract.
void remote_insert (TemporalId temporal_id, BoundaryData< PrimalFields, PrimalFluxes > vars)
 Add a value. This function must be called once between calls to extract.

Detailed Description

template<typename TemporalId, typename PrimalFields, typename PrimalFluxes>
struct elliptic::dg::MortarData< TemporalId, PrimalFields, PrimalFluxes >

Boundary data on both sides of a mortar.

Note
This is a struct (as opposed to a type alias) so it can be used to deduce the template parameters

The documentation for this struct was generated from the following file:
  • src/Elliptic/DiscontinuousGalerkin/DgOperator.hpp