Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W waLBerla
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 51
    • Issues 51
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waLBerla
  • waLBerla
  • Merge requests
  • !271

Extract core functionality from mesh module into a new module

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Lukas Werner requested to merge yw25ynew/walberla:mesh_module_refactor into master May 13, 2020
  • Overview 2
  • Commits 3
  • Pipelines 3
  • Changes 57

This MR introduces a split of the mesh module into two separate modules, where "mesh_common" extracts some core functionality from "mesh". mesh_common contains the core functionality/coupling to OpenMesh (ie. general mesh computations, vtk). Its dependencies are strongly reduced to just core and vtk (+OpenMesh).

The mesh module is basically the old module minus the code extracted to mesh_common, depending on mesh_common. It has quite a set of dependencies and represents the addition of meshes to a multitude of modules in walberla.

This split allows us to introduce meshes to MESA-PD without dragging along all dependencies of the mesh module.

@eibl

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: mesh_module_refactor