Select Git revision
DiamondDualMeshBuilder.cpp
-
Stéphane Del Pino authored
These mechanisms are designed to manage diamond meshes/connectivities The main idea is that the diamond mesh is stored as long as its primary mesh lives, and can be retrieved easily. The same mechanism is defined for diamond mesh connectivities. Thus in a moving grid context, the only required calculations will be the definition of the diamond mesh's vertices coordinates. Recall that diamond meshes are just meshes so all meshes' functionality apply to them.
Stéphane Del Pino authoredThese mechanisms are designed to manage diamond meshes/connectivities The main idea is that the diamond mesh is stored as long as its primary mesh lives, and can be retrieved easily. The same mechanism is defined for diamond mesh connectivities. Thus in a moving grid context, the only required calculations will be the definition of the diamond mesh's vertices coordinates. Recall that diamond meshes are just meshes so all meshes' functionality apply to them.
IBoundaryConditionDescriptor.hpp 785 B
#ifndef I_BOUNDARY_CONDITION_DESCRIPTOR_HPP
#define I_BOUNDARY_CONDITION_DESCRIPTOR_HPP
#include <iostream>
class IBoundaryConditionDescriptor
{
public:
enum class Type
{
symmetry
};
protected:
virtual std::ostream& _write(std::ostream& os) const = 0;
public:
friend std::ostream&
operator<<(std::ostream& os, const IBoundaryConditionDescriptor& bcd)
{
return bcd._write(os);
}
virtual Type type() const = 0;
IBoundaryConditionDescriptor() = default;
IBoundaryConditionDescriptor(const IBoundaryConditionDescriptor&) = delete;
IBoundaryConditionDescriptor(IBoundaryConditionDescriptor&&) = delete;
virtual ~IBoundaryConditionDescriptor() = default;
};
#endif // I_BOUNDARY_CONDITION_DESCRIPTOR_HPP