#include <Panzer_BlockedDOFManagerFactory.hpp>
|
static bool | requiresBlocking (const std::string &fieldorder) |
|
static void | buildBlocking (const std::string &fieldorder, std::vector< std::vector< std::string > > &blocks) |
|
◆ BlockedDOFManagerFactory()
panzer::BlockedDOFManagerFactory::BlockedDOFManagerFactory |
( |
| ) |
|
|
inline |
◆ ~BlockedDOFManagerFactory()
virtual panzer::BlockedDOFManagerFactory::~BlockedDOFManagerFactory |
( |
| ) |
|
|
inlinevirtual |
◆ requiresBlocking()
bool panzer::BlockedDOFManagerFactory::requiresBlocking |
( |
const std::string & |
fieldorder | ) |
|
|
static |
Does a fieldOrder string require blocking? A field order is basically stetup like this blocked: <field 0> <field 1> where two blocks will be created. To merge fields between blocks use a hyphen, i.e. blocked: <field 0> <field 1> - <field 2> - <field 3> This will create 2 blocks, the first contains only <field 0> and the second combines <field 1>, <field 2> and <field 3>. Note the spaces before and after the hyphen, these are important!
Definition at line 56 of file Panzer_BlockedDOFManagerFactory.cpp.
◆ buildBlocking()
void panzer::BlockedDOFManagerFactory::buildBlocking |
( |
const std::string & |
fieldorder, |
|
|
std::vector< std::vector< std::string > > & |
blocks |
|
) |
| |
|
static |
Does a fieldOrder string require blocking? A field order is basically stetup like this blocked: <field 0> <field 1> where two blocks will be created. To merge fields between blocks use a hyphen, i.e. blocked: <field 0> <field 1> - <field 2> - <field 3> This will create 2 blocks, the first contains only <field 0> and the second combines <field 1>, <field 2> and <field 3>. Note the spaces before and after the hyphen, these are important!
Definition at line 90 of file Panzer_BlockedDOFManagerFactory.cpp.
◆ buildGlobalIndexer()
Teuchos::RCP< panzer::GlobalIndexer > panzer::BlockedDOFManagerFactory::buildGlobalIndexer |
( |
const Teuchos::RCP< const Teuchos::OpaqueWrapper< MPI_Comm > > & |
mpiComm, |
|
|
const std::vector< Teuchos::RCP< panzer::PhysicsBlock > > & |
physicsBlocks, |
|
|
const Teuchos::RCP< ConnManager > & |
connMngr, |
|
|
const std::string & |
fieldOrder = "" |
|
) |
| const |
|
virtual |
Use the physics block to construct a unique global indexer object.
- Parameters
-
[in] | mpiComm | MPI communicator to use in the construction |
[in] | physicsBlocks | A vector of physics block objects that contain unknown field information. |
[in] | connMngr | Connection manager that contains the mesh topology |
[in] | fieldOrder | Specifies the local ordering of the degrees of freedom. This is relevant when degrees of freedom are shared on the same geometric entity. The default is an alphabetical ordering. |
[in] | buildGlobalUnknowns | Build the global unknowns before returning. The default value gives backwards-compatible behavior. Set this to false if the caller will initialize the DOF manager in additional ways before issuing the call to build the global unknowns itself. |
- Returns
- A GlobalIndexer object. If buildGlobalUnknowns is true, the object is fully constructed. If it is false, the caller must finalize it.
Implements panzer::GlobalIndexerFactory.
Definition at line 120 of file Panzer_BlockedDOFManagerFactory.cpp.
◆ setUseDOFManagerFEI()
void panzer::BlockedDOFManagerFactory::setUseDOFManagerFEI |
( |
bool |
flag | ) |
|
|
inline |
◆ getUseDOFManagerFEI()
bool panzer::BlockedDOFManagerFactory::getUseDOFManagerFEI |
( |
| ) |
const |
|
inline |
◆ setUseTieBreak()
void panzer::BlockedDOFManagerFactory::setUseTieBreak |
( |
bool |
flag | ) |
|
|
inline |
◆ getUseTieBreak()
bool panzer::BlockedDOFManagerFactory::getUseTieBreak |
( |
| ) |
|
|
inline |
◆ useDOFManagerFEI_
bool panzer::BlockedDOFManagerFactory::useDOFManagerFEI_ |
|
private |
◆ useTieBreak_
bool panzer::BlockedDOFManagerFactory::useTieBreak_ |
|
private |
The documentation for this class was generated from the following files: