Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 86
    • Merge requests 86
  • 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
  • #750
Closed
Open
Issue created Aug 05, 2019 by Timo Koch@timokOwner

Tabularization out-of-range warning too aggressive

For access out-of-range of the table we currently print something like

FORWARD METHOD CALL liquidDensity(573.15, 6.24561e+06) OF COMPONENT 'H2O'. TABULATION TOO SMALL?
Subcritical values: Be aware to use Tables with sufficient resolution! 

I find caps rather aggressive here, also it is not immediately clear that the fall-back is just a call to the respective function and nothing severely wrong. I think the message should clearly state

  • how the value was out of range
  • that a fall-back is called and how
  • that we just warn because of a runtime overhead (resulting from possibly wrong values for the tabulation bounds) and not from some physical error
Assignee
Assign to
Time tracking