Peano
coupling.actionsets.AbstractLimiterActionSet.AbstractLimiterActionSet Class Reference
Inheritance diagram for coupling.actionsets.AbstractLimiterActionSet.AbstractLimiterActionSet:
Collaboration diagram for coupling.actionsets.AbstractLimiterActionSet.AbstractLimiterActionSet:

Public Member Functions

def __init__ (self, solver)
 
def get_action_set_name (self)
 
def user_should_modify_template (self)
 
def get_includes (self)
 

Private Attributes

 _solver
 

Detailed Description

Definition at line 9 of file AbstractLimiterActionSet.py.

Constructor & Destructor Documentation

◆ __init__()

def coupling.actionsets.AbstractLimiterActionSet.AbstractLimiterActionSet.__init__ (   self,
  solver 
)
solver: Ader-DG
  Reference to creating class 

Definition at line 10 of file AbstractLimiterActionSet.py.

Member Function Documentation

◆ get_action_set_name()

def coupling.actionsets.AbstractLimiterActionSet.AbstractLimiterActionSet.get_action_set_name (   self)
 You should replicate this function in each subclass, so you get 
 meaningful action set names (otherwise, it will be 
 AbstractFVActionSet0,1,2,...).

Reimplemented in coupling.actionsets.VerifyTroubledness.VerifyTroubledness, coupling.actionsets.SpreadLimiterStatus.SpreadLimiterStatus, and coupling.actionsets.SolveRiemannProblem.SolveRiemannProblem.

Definition at line 21 of file AbstractLimiterActionSet.py.

◆ get_includes()

◆ user_should_modify_template()

def coupling.actionsets.AbstractLimiterActionSet.AbstractLimiterActionSet.user_should_modify_template (   self)

Definition at line 32 of file AbstractLimiterActionSet.py.

Field Documentation

◆ _solver


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