Peano

Searching...

No Matches

Inheritance diagram for api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions:

[legend]

Collaboration diagram for api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions:

[legend]

Public Member Functions
	__init__ (self, solver)
	Yet to be written.

	get_body_of_operation (self, operation_name)
	Provide C++ code snippet for peano4.solversteps.ActionSet.OPERATION_TOUCH_VERTEX_FIRST_TIME Provide C++ code snippet for peano4.solversteps.ActionSet.OPERATION_TOUCH_CELL_FIRST_TIME

	get_action_set_name (self)
	Configure name of generated C++ action set.

	user_should_modify_template (self)
	The action set that Peano will generate that corresponds to this class should not be modified by users and can safely be overwritten every time we run the Python toolkit.

	get_includes (self)
	Consult petsc.Project for details.

	get_attributes (self)
	Return attributes as copied and pasted into the generated class.

	get_constructor_body (self)
	Define body of constructor.

Public Member Functions inherited from peano4.solversteps.ActionSet.ActionSet
	get_static_initialisations (self, full_qualified_classname)

	get_destructor_body (self)

	get_body_of_getGridControlEvents (self)

	get_body_of_prepareTraversal (self)

	get_body_of_unprepareTraversal (self)

Data Fields
	d

Data Fields inherited from peano4.solversteps.ActionSet.ActionSet
	descend_invocation_order

	parallel

Static Public Attributes
str	TemplateTouchCellFirstTime

Static Public Attributes inherited from peano4.solversteps.ActionSet.ActionSet
str	OPERATION_BEGIN_TRAVERSAL = "beginTraversal"

str	OPERATION_END_TRAVERSAL = "endTraversal"

str	OPERATION_CREATE_PERSISTENT_VERTEX = "createPersistentVertex"

str	OPERATION_DESTROY_PERSISTENT_VERTEX = "destroyPersistentVertex"

str	OPERATION_CREATE_HANGING_VERTEX = "createHangingVertex"

str	OPERATION_DESTROY_HANGING_VERTEX = "destroyHangingVertex"

str	OPERATION_CREATE_PERSISTENT_FACE = "createPersistentFace"

str	OPERATION_DESTROY_PERSISTENT_FACE = "destroyPersistentFace"

str	OPERATION_CREATE_HANGING_FACE = "createHangingFace"

str	OPERATION_DESTROY_HANGING_FACE = "destroyHangingFace"

str	OPERATION_CREATE_CELL = "createCell"

str	OPERATION_DESTROY_CELL = "destroyCell"

str	OPERATION_TOUCH_VERTEX_FIRST_TIME = "touchVertexFirstTime"

str	OPERATION_TOUCH_VERTEX_LAST_TIME = "touchVertexLastTime"

str	OPERATION_TOUCH_FACE_FIRST_TIME = "touchFaceFirstTime"

str	OPERATION_TOUCH_FACE_LAST_TIME = "touchFaceLastTime"

str	OPERATION_TOUCH_CELL_FIRST_TIME = "touchCellFirstTime"

str	OPERATION_TOUCH_CELL_LAST_TIME = "touchCellLastTime"

Detailed Description

Todo: This version is not yet implemented, and maybe we don't need it ever!

Add those contributions to matrix which impose the boundary conditions

Dirichlet (and really all boundary) faces do not hold any artificial or real degrees of freedom in our code. So the core assembly ignores these faces and we end up with a linear equation system which is not coupled to the PDE's boundary conditions. This additional action sets runs over the mesh and adds the missing coupling.

For every cell that we visit (and that is not outside the computational domain), we check its 2d faces, i.e. the left and right face along each axis. If this face is an interior, nothing is to be done. We only have to do something for boundary faces. In this action set, we assume that each face is a Dirichlet face.

If a face is a Dirichlet face, we loop over the nodes on the face. For this, we emply Peano's exclusive d-dimensional for (dfore), which is a d-dimensional for loop skipping one dimension. Per dof, we compute the dof's coordinate x and ask the user's solver what the value there should be. This gives us the right-hand side for the equation system row that imposes the condition.

Next, we use compute the projection of the solution to the boundary. This might be a different projection than used for the faces, even though the code is basically the same. For some solvers, we project solely the derivatives along the normal onto the face, for others, we

Todo

We need the projection matrix for the solution!

We have to add the corresponding matrix entries below, as well as the right-hand side

Definition at line 10 of file ImposeDirichletBoundaryConditions.py.

Constructor & Destructor Documentation

◆ init()

api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.__init__	(		self,
			solver )

Yet to be written.

Reimplemented from peano4.solversteps.ActionSet.ActionSet.

Definition at line 109 of file ImposeDirichletBoundaryConditions.py.

References api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.__init__().

Referenced by api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.__init__().

Here is the call graph for this function:

Here is the caller graph for this function:

Member Function Documentation

◆ get_action_set_name()

api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.get_action_set_name ( self )

Configure name of generated C++ action set.

This action set will end up in the directory observers with a name that reflects how the observer (initialisation) is mapped onto this action set. The name pattern is ObserverName2ActionSetIdentifier where this routine co-determines the ActionSetIdentifier. We make is reflect the Python class name.

Reimplemented from peano4.solversteps.ActionSet.ActionSet.

Definition at line 146 of file ImposeDirichletBoundaryConditions.py.

◆ get_attributes()

api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.get_attributes ( self )

Return attributes as copied and pasted into the generated class.

Please note that action sets are not persistent, i.e. there is one object creation per grid sweep per tree.

Reimplemented from peano4.solversteps.ActionSet.ActionSet.

Definition at line 184 of file ImposeDirichletBoundaryConditions.py.

◆ get_body_of_operation()

api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.get_body_of_operation	(		self,
			operation_name )

Provide C++ code snippet for peano4.solversteps.ActionSet.OPERATION_TOUCH_VERTEX_FIRST_TIME
Provide C++ code snippet for peano4.solversteps.ActionSet.OPERATION_TOUCH_CELL_FIRST_TIME

Only touchVertexFirstTime is an event where this action set actually does something: It inserts the template TemplateTouchVertexFirstTime and replaces it with entries from the dictionary. The latter is befilled in init().

We actually do something during touchVertexFirstTime and touchCellFirstTime. We insert the appropriate template into each.

Reimplemented from peano4.solversteps.ActionSet.ActionSet.

Definition at line 124 of file ImposeDirichletBoundaryConditions.py.

◆ get_constructor_body()

api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.get_constructor_body ( self )

Define body of constructor.

See also: get_attributes()

Reimplemented from peano4.solversteps.ActionSet.ActionSet.

Definition at line 193 of file ImposeDirichletBoundaryConditions.py.

◆ get_includes()

api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.get_includes ( self )

Consult petsc.Project for details.

Reimplemented from peano4.solversteps.ActionSet.ActionSet.

Definition at line 172 of file ImposeDirichletBoundaryConditions.py.

◆ user_should_modify_template()

api.actionsets.ImposeDirichletBoundaryConditions.ImposeDirichletBoundaryConditions.user_should_modify_template ( self )

The action set that Peano will generate that corresponds to this class should not be modified by users and can safely be overwritten every time we run the Python toolkit.

Reimplemented from peano4.solversteps.ActionSet.ActionSet.

Definition at line 161 of file ImposeDirichletBoundaryConditions.py.