#include <dof_map.h>
Inherits std::map< unsigned int, PeriodicBoundary >.
PeriodicBoundary * boundary (unsigned int id)
PeriodicBoundaries ()
~PeriodicBoundaries ()
const Elem * neighbor (unsigned int boundary_id, const MeshBase &mesh, const Elem *e, unsigned int side)
The constraint matrix storage format. We're using a class instead of a typedef to allow forward declarations and future flexibility. Is there some issue with deriving from standard containers, i.e. don't do it because they don't have virtual destructors?
Definition at line 210 of file dof_map.h.
Definition at line 215 of file dof_map.h.
{}
Definition at line 1325 of file dof_map_constraints.C.
{
}
Definition at line 995 of file dof_map.h.
Referenced by FEBase::compute_periodic_constraints(), and neighbor().
{
iterator i = this->find(id);
if (i == this->end())
return NULL;
return &i->second;
}
Definition at line 1329 of file dof_map_constraints.C.
References boundary(), Elem::build_side(), MeshBase::point_locator(), and PeriodicBoundary::translation_vector.
Referenced by FEBase::compute_periodic_constraints().
{
// Find a point on that side (and only that side)
Point p = e->build_side(side)->centroid();
PeriodicBoundary *b = this->boundary(boundary_id);
libmesh_assert (b);
p += b->translation_vector;
return mesh.point_locator().operator()(p);
}
Generated automatically by Doxygen for libMesh from the source code.