Peano
Loading...
Searching...
No Matches
exahype2.api.fv.actionsets.ProjectPatchOntoFaces.ProjectPatchOntoFaces Class Reference

Project a Finite Volume patch's data onto the overlap held on its surrounding faces, so the halo layers can be reconstructed from it later on -. More...

Inheritance diagram for exahype2.api.fv.actionsets.ProjectPatchOntoFaces.ProjectPatchOntoFaces:
Collaboration diagram for exahype2.api.fv.actionsets.ProjectPatchOntoFaces.ProjectPatchOntoFaces:

Public Member Functions

 __init__ (self, patch, patch_overlap_update, guard, includes)
 patch: peano4.api.datamodel.Patch The cell-associated patch to project onto its surrounding faces -
 
 get_action_set_name (self)
 

Detailed Description

Project a Finite Volume patch's data onto the overlap held on its surrounding faces, so the halo layers can be reconstructed from it later on -.

See also
toolbox.blockstructured.api.ReconstructPatchWithHalo.

Ported from the legacy python/exahype2/solvers/fv/actionsets/ProjectPatchOntoFaces.py, slimmed down: the legacy version additionally set the isUpdated()/ UpdatedTimeStamp() face metadata (read solver._face_label/solver._cell_label) so exahype2.solvers.fv.actionsets.RollOverUpdatedFace knew which half of a face had actually been written. The new exahype2.api's data structures (

See also
exahype2.api.fv.RusanovWithExplicitEuler) do not create a cell/face label yet, and RollOverUpdatedFace has not been ported either, so this version does purely what the base class toolbox.blockstructured.api.ProjectPatchOntoFaces already does: copy solver._patch's boundary layer into solver._patch_overlap_update. Once cell/face labels exist in the new API, the metadata-update behaviour can be reinstated here.

Definition at line 6 of file ProjectPatchOntoFaces.py.

Constructor & Destructor Documentation

◆ __init__()

exahype2.api.fv.actionsets.ProjectPatchOntoFaces.ProjectPatchOntoFaces.__init__ (   self,
  patch,
  patch_overlap_update,
  guard,
  includes 
)

patch: peano4.api.datamodel.Patch The cell-associated patch to project onto its surrounding faces -

See also
exahype2.api.fv.RusanovWithExplicitEuler.

patch_overlap_update: peano4.api.datamodel.Patch The face-associated overlap patch to project patch's boundary layer into -

See also
exahype2.api.fv.RusanovWithExplicitEuler.

guard: str C++ boolean expression, evaluated per cell in touchCellLastTime, guarding whether that cell's patch is projected onto its faces.

includes: str Additional includes this action set's generated code needs - callers typically pass solver._get_default_includes() + solver.user_solver_includes.

Definition at line 28 of file ProjectPatchOntoFaces.py.

References exahype2.api.fv.actionsets.ProjectPatchOntoFaces.ProjectPatchOntoFaces.__init__().

Referenced by exahype2.api.fv.actionsets.ProjectPatchOntoFaces.ProjectPatchOntoFaces.__init__().

Here is the call graph for this function:
Here is the caller graph for this function:

Member Function Documentation

◆ get_action_set_name()

exahype2.api.fv.actionsets.ProjectPatchOntoFaces.ProjectPatchOntoFaces.get_action_set_name (   self)

Definition at line 56 of file ProjectPatchOntoFaces.py.


The documentation for this class was generated from the following file: