Select Git revision
DiamondDualConnectivityManager.hpp
-
Stéphane Del Pino authored
Rename `MeshToDiamondDualMeshDataMapper` as `ConnectivityToDiamondDualConnectivityDataMapper` which is correct This data mapper is now available through the DiamondDualConnectivityManager and is built when connectivity is constructed The construction of this mapper is still completely independent of the mesh construction itself which is bad since same assumptions are made twice... It should be actually constructed at the same time allowing for instance easy renumbering. This should be done soon... hopefully...
Stéphane Del Pino authoredRename `MeshToDiamondDualMeshDataMapper` as `ConnectivityToDiamondDualConnectivityDataMapper` which is correct This data mapper is now available through the DiamondDualConnectivityManager and is built when connectivity is constructed The construction of this mapper is still completely independent of the mesh construction itself which is bad since same assumptions are made twice... It should be actually constructed at the same time allowing for instance easy renumbering. This should be done soon... hopefully...
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