Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D dune-istl
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Core Modules
  • dune-istl
  • Issues
  • #86
Closed
Open
Created Jan 22, 2020 by Markus Blatt@markus.blattOwner

Inconsistent naming of parameters for solver factory

While writing an adapter for the solver factory, I stumbled over the rather inconsistent naming of the parameters used for the solver factory. It is a pity that nobody looked at this before merging and that this is now part of a stable release.

We might want to change this ASAP as otherwise this might last forever.

It seems like the parameter names taken are just the names of the constructor parameters. Depending on who wrote the code, these are a bit too different or rather unexplicit:

  • "verbose" is used for the solver, while the AMG uses "verbosity" (these should be the same to avoid confusion)
  • "mmax" for the number of vectors stored in FCG is not very explicit
  • "n" for the order of the ILU decomposition might still be ok, but order seems better

My questions would be:

  • Shouldn't we settle on either verbose or verbosity?
  • Shouldn't we use expressive parameter names (maxOrthogonalizationVectors instead of mmax
  • Should we prefix preconditioner specific parameters with the the preconditioner "n"-> "iluN" or "iluOrder"?
Edited Jan 22, 2020 by Markus Blatt
Assignee
Assign to
Time tracking