Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
dumux
dumux
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 92
    • Issues 92
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 68
    • Merge Requests 68
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • dumux-repositories
  • dumuxdumux
  • Issues
  • #979

Closed
Open
Opened Dec 22, 2020 by Timo Koch@timokOwner

Newton has too many dependencies

The Newton solver has quite some requirements on the Assembler and LinearSolver types which makes it harder (though not impossible) to use in a generic setting. These dependencies are documented in test/nonlinear/newton/test_newton.cc where the minimal current interface requirements are implemented in Mock classes and a scalar nonlinear equation is solved.

This issue is here to remind us that these dependencies should be reduced to a minimum to decrease coupling in the code.

Ideas/issues towards this also involve #940 !2113 #978

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dumux-repositories/dumux#979