Skip to content
Snippets Groups Projects
Select Git revision
  • fb8866f92f0a03983f584a0f383d571cec9939c6
  • develop default protected
  • 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
  • feature/escobar-smoother
  • feature/hypoelasticity-clean
  • feature/hypoelasticity
  • 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

pugs

Stephane Del Pino's avatar
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.
fb8866f9
History
Name Last commit Last update