Skip to content
Snippets Groups Projects
Select Git revision
  • a34db2949c30bfa1f7167a4d8e3370e1de9cc8a9
  • develop default protected
  • feature/gmsh-reader
  • save_clemence
  • origin/stage/bouguettaia
  • feature/kinetic-schemes
  • feature/reconstruction
  • feature/local-dt-fsi
  • feature/composite-scheme-sources
  • feature/composite-scheme-other-fluxes
  • feature/serraille
  • feature/variational-hydro
  • feature/composite-scheme
  • hyperplastic
  • feature/polynomials
  • feature/gks
  • feature/implicit-solver-o2
  • feature/coupling_module
  • feature/implicit-solver
  • feature/merge-local-dt-fsi
  • master protected
  • v0.5.0 protected
  • v0.4.1 protected
  • v0.4.0 protected
  • v0.3.0 protected
  • v0.2.0 protected
  • v0.1.0 protected
  • Kidder
  • v0.0.4 protected
  • v0.0.3 protected
  • v0.0.2 protected
  • v0 protected
  • v0.0.1 protected
33 results

DiamondDualMeshBuilder.cpp

  • Stéphane Del Pino's avatar
    a34db294
    Cleanup data mapper · a34db294
    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...
    a34db294
    History
    Cleanup data mapper
    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...