Skip to content
GitLab
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 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • 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
  • #869
Closed
Open
Issue created Apr 21, 2020 by Timo Koch@timokOwner

Discussion: Remove sequential on master

Maybe we can collect some pros and cons for deleting the old sequential models on master?

Pros:

  • Easier to maintain codebase (tests that need fixing, properties that have to be adapted)
  • Less deprecation warnings (could be probably also suppressed)

Cons:

  • If you want to use a sequential model you have to switch to Dumux releases/3.2 and Dune releases/2.7
  • Depending on how long it takes to reimplement the models in the new model scheme the code and tests might be harder to reproduce
Assignee
Assign to
Time tracking