system_management.h File Reference

#include <deal.II/base/parameter_handler.h>
#include <application_core/matrix_block.h>
#include <application_core/mesh_loop_info_objects.h>
#include <utils/logging.h>
#include <boost/algorithm/string/join.hpp>

Include dependency graph for system_management.h:

This graph shows which files directly or indirectly include this file:

Go to the source code of this file.

Classes
class	FuelCell::SystemManagement
	IMPORTANT: Add all new solution variables and equations here ! More...

Namespaces
	FuelCell
	This namespace contains data and methods that handle initial and boundary data of a problem at hand.
	FuelCell::ApplicationCore
	Namespace containing the basic application framework used to loop over cells and create objects passed to FuelCellShop::Equation objects.

Macros
#define	INSERT_ELEMENT(p)   VariableNames_strings[p] = #p

Typedefs
typedef std::map< std::string, std::map< std::string, DoFTools::Coupling > >	couplings_map
	The typedef for the map of cell or flux (DG FEM only) couplings stored in the actual equation classes. More...

Enumerations
enum	VariableNames {   nothing = 0, oxygen_molar_fraction, water_molar_fraction, hydrogen_molar_fraction,   nitrogen_molar_fraction, protonic_electrical_potential, electronic_electrical_potential, membrane_water_content,   temperature_of_solid_phase, temperature_of_fluid_phase, temperature_of_REV, liquid_water_saturation,   capillary_pressure, current_density, CL_effectiveness, OH_coverage,   O_coverage, oxygen_concentration, water_concentration, hydrogen_concentration,   nitrogen_concentration, proton_concentration, total_pressure, density_species_1,   velocity_species_1_X, velocity_species_1_Y, velocity_species_1_Z, density_species_2,   velocity_species_2_X, velocity_species_2_Y, velocity_species_2_Z, density_species_3,   velocity_species_3_X, velocity_species_3_Y, velocity_species_3_Z, density_species_4,   velocity_species_4_X, velocity_species_4_Y, velocity_species_4_Z, density_species_5,   velocity_species_5_X, velocity_species_5_Y, velocity_species_5_Z, single_fluid_pressure,   single_fluid_velocity_X, single_fluid_velocity_Y, single_fluid_velocity_Z }
	The enumeration containing the names of some of the available FCST solution variables and their derivatives to be used in kinetics, materials, and other related classes. More...
enum	FuelCell::ApplicationCore::SolverName {   FuelCell::ApplicationCore::noSolver = 0, FuelCell::ApplicationCore::LINEAR, FuelCell::ApplicationCore::NEWTON, FuelCell::ApplicationCore::PICARD,   FuelCell::ApplicationCore::PICARD }
enum	ReactionNames { noReaction = 0, ORR, HOR }

Macro Definition Documentation

#define INSERT_ELEMENT

(

p

)

VariableNames_strings[p] = #p

Referenced by FuelCell::SystemManagement::get_VariableNames().

Typedef Documentation

typedef std::map< std::string , std::map<std::string, DoFTools::Coupling> > couplings_map

The typedef for the map of cell or flux (DG FEM only) couplings stored in the actual equation classes.

The first std::string means the name of available FCST equation.

The second std::string means the name of available FCST solution variable.

Enumeration Type Documentation

enum ReactionNames

Theory

An enumeration used for expressing a type of reaction. Used by layers, equations and catalyst materials for specifying a type of reaction in a unified manner.

Usage

Simply create an instance of an enumeration, then use it in logical expressions.

* ReactionNames my_reaction = HOR;
*
* ...
*
* if (my_reaction == HOR)...
* 

By Default the enumeration will be created as noReaction, therefore you must explicitly set the reaction name. See unit tests in enumeration_test class.

Author

P. Wardlaw, 2014

Enumerator
noReaction
ORR
HOR

enum VariableNames

The enumeration containing the names of some of the available FCST solution variables and their derivatives to be used in kinetics, materials, and other related classes.

The enumeration is usually used in conjunction with FuelCellShop::SolutionVariable class. For example, if the only available FCST solution variable is electronic_electrical_potential then the respective piece of code will look like:

* FuelCellShop::SolutionVariable solution;
* (...)
* if( solution.get_variablename() == VariableNames::electronic_electrical_potential )
* {
* (...)
* }
* 

In this case, if solution is initialized such that it contains electronic_electrical_potential then the if statement will return TRUE.

Enumerator
nothing
oxygen_molar_fraction
water_molar_fraction
hydrogen_molar_fraction
nitrogen_molar_fraction
protonic_electrical_potential
electronic_electrical_potential
membrane_water_content
temperature_of_solid_phase
temperature_of_fluid_phase
temperature_of_REV
liquid_water_saturation
capillary_pressure
current_density
CL_effectiveness
OH_coverage
O_coverage
oxygen_concentration
water_concentration
hydrogen_concentration
nitrogen_concentration
proton_concentration
total_pressure
density_species_1
velocity_species_1_X
velocity_species_1_Y
velocity_species_1_Z
density_species_2
velocity_species_2_X
velocity_species_2_Y
velocity_species_2_Z
density_species_3
velocity_species_3_X
velocity_species_3_Y
velocity_species_3_Z
density_species_4
velocity_species_4_X
velocity_species_4_Y
velocity_species_4_Z
density_species_5
velocity_species_5_X
velocity_species_5_Y
velocity_species_5_Z
single_fluid_pressure
single_fluid_velocity_X
single_fluid_velocity_Y
single_fluid_velocity_Z