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 102
    • Issues 102
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 90
    • Merge requests 90
  • 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
  • #590
Closed
Open
Issue created Nov 09, 2018 by Bernd Flemisch@berndOwner

TabulatedComponent::init() may be called only once

If it's called twice, for example from two coupled subproblems, only the values are reset to zero, but not the flags that are responsible for eventually recalculating the values. Therefore, these values stay zero.

I'm not so sure what to do. We could

  1. Forbid a second init call by throwing an exception.
  2. Check if the parameters to init are the same as before. If yes, nothing needs to be done. If no, we could issue a warning and recalculate (by also setting the flags back to false).

Opinions?

Assignee
Assign to
Time tracking