Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 381
    • Issues 381
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #2144

Closed
Open
Created Jun 30, 2021 by Mark Olesen@markMaintainer

catching fails with bad input (fluxSummary)

As raised on EP1510, using errors handling in fluxSummary does not work. With an empty or missing surface, it still tries a lookupObject for the phi field. Within objectRegistry this lookup failure triggers an abort(FatalError), which cannot be caught.

Possible fixes:

  • downgrade abort() to exit()? ... maybe not good
  • check for field iff the surface actually has faces
  • use cfind instead of lookup within fluxSummary
  • a second template parameter on lookupObject: template <class Type, bool Abort=true> lookupObject( ... )

Related to #1779 (closed)

Edited Jun 30, 2021 by Mark Olesen
Assignee
Assign to
Time tracking