Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
openfoam
openfoam
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 333
    • Issues 333
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 6
    • Merge Requests 6
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • Development
  • openfoamopenfoam
  • Issues
  • #1779

Closed
Open
Opened Jul 21, 2020 by Mark Olesen@markMaintainer

additional handling of function object failure

As raised in EP1338, the change of sampled surfaces causes a different in later OpenFOAM versions.

In the earlier versions, if the surface was out-of-domain (wrong location, but most likely incorrect scaling), this would fail on construction which would emit a warning and discard the function object.

More recent updates for sampling are much "lazier" - they only construct the surface as required. This is particularly useful in cases of an iso-surface for a field that does not exist until later in the simulation. However, as a side-effect of this, the failure can now occur during execute() or write() of the functionObject, which means that even if the dry-run was successful, the job can crash because of the bad function object.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: Development/openfoam#1779