Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 86
    • Merge requests 86
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositoriesdumux-repositories
  • dumuxdumux
  • Issues
  • #431
Closed
Open
Issue created Dec 28, 2017 by Timo Koch@timokOwner

Grid shouldn't be a singleton

There is not just always one grid of a type, or one grid per typetag/problem. So the grid shouldn't be implemented as a singleton.

The gridcreator / gridwrapper needs to be available to problems (boundary conditions) and spatial params (params from dgf/msh) for parameters. We could pass a shared_ptr to the problem / spatialparams in the constructor.

All occurances of GridCreator::grid() should be replaced by either gridView.grid() or using a grid object directly (adaptive).

see also !185 (merged)

Edited Apr 03, 2018 by Dennis Gläser
Assignee
Assign to
Time tracking