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 390
    • Issues 390
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1858

Closed
Open
Created Sep 24, 2020 by Mark Olesen@markMaintainer

a missing fractionExpr should not always automatically equal 1

mixed expression bcs are defined with up to three expressions:

  • valueExpr
  • gradientExpr
  • fractionExpr

Missing values:

  • missing valueExpr treated as zero
  • missing gradientExpr treated as zero
  • missing fractionExpr treated as one

Treating a missing fractionExpr like "1" makes sense for handling value expressions (when gradientExpr is missing), but does not really make sense when valueExpr itself is missing. For example,

{
    gradientExpr  " .... ";
}

The user would rightly expect that the gradient expression should be used, not ignored.

Assignee
Assign to
Time tracking