Select Git revision
DiamondDualConnectivityBuilder.hpp
-
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.
DiamondDualConnectivityBuilder.hpp 745 B
#ifndef DIAMOND_DUAL_CONNECTIVITY_BUILDER_HPP
#define DIAMOND_DUAL_CONNECTIVITY_BUILDER_HPP
#include <mesh/ConnectivityBuilderBase.hpp>
#include <memory>
template <size_t>
class Connectivity;
class ConnectivityDescriptor;
class DiamondDualConnectivityBuilder : public ConnectivityBuilderBase
{
private:
template <size_t Dimension>
void _buildDiamondConnectivityDescriptor(const Connectivity<Dimension>&, ConnectivityDescriptor&);
template <size_t Dimension>
void _buildDiamondConnectivityFrom(const IConnectivity&);
friend class DiamondDualConnectivityManager;
DiamondDualConnectivityBuilder(const IConnectivity&);
public:
~DiamondDualConnectivityBuilder() = default;
};
#endif // DIAMOND_DUAL_CONNECTIVITY_BUILDER_HPP