Skip to content
Snippets Groups Projects

Improve flexiblity of GeometricBoundaryField evaluate

Merged Mark OLESEN requested to merge update-GeometricBoundaryField-evaluate into develop

The primary change is to expose the communication type is exposed as a parameter to allow for more tuning and better reuse independent of any defaultCommsType value. However, provide as the default parameter of defaultCommsType so there is no change in behaviour for any existing code.

The new evaluate_if() method supports a general selection predicate, which will help us avoid writing/rewriting specialized evaluation methods in the future (can just use a lambda).

In addition to the boundary field handling, also cleanup some of the DimensionedField and GeometricField I/O and replace demand-driven-data in GeometricField with unique_ptr.

Merge request reports

Loading
Loading

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
Please register or sign in to reply
Loading