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
  • #978

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

Newton hard-codes BlockVector for solver

I had a case where I wrote a linear solver that works with DynamicVector and DynamicMatrix. I couldn't use this solver in the Newton because at some point the Newton copies everything to a BlockVector to support UMFPack. I think this should be more fine grained and only convert if necessary. And make sure it converts to the type that the solver expects. With !2113 it should be possible to know the type the solver expects.

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