Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 98
    • Merge requests 98
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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-repositories
  • dumuxdumux
  • Issues
  • #541
Closed
Open
Created Jul 27, 2018 by Bernd Flemisch@berndOwner

Test restart functionality

With !1039 (merged), the possibility of reading an initial solution from a Vtk file has been introduced. This is implemented quite general, but a model-specific part remains that defines the primary variable names of the model that are expected to be found in the Vtk file. Since this is sensitive to changes of these names in the output routines, it should be tested thoroughly:

  • Adapt relevant main files such that the restart functionality will work again.
  • Add one restart test in the corresponding CMakeLists.txt.
  • Add more parallel tests in test/porousmediumflow/richards/implicit (depends on #535 (closed)).

Examples can be found in test/porousmediumflow/2p/implicit/incompressible, test/porousmediumflow/2p2c/implicit and test/freeflow/navierstokes.

Edited Jul 30, 2018 by Timo Koch
Assignee
Assign to
Time tracking