Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 426
    • Issues 426
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1269
Closed
Open
Issue created Apr 03, 2019 by Mark OLESEN@markMaintainer

possible regression in uniformFixedValuePointPatch?

In tutorials/basic/overLaplacianDyMFoam/heatTransfer I'm getting some very odd output which I think could be related to this commit: 0987898f5c1678

I initially thought it might be related to the generic point patches since reconstructPar was failing when fill-nan is set. The values it reconstructs for the pointDisplacement right1 boundary are scalars, not vectors.

Backtracking some more, it seems that the original decomposed fields are a bit odd.

In 1812: processor0/0/pointDisplacement.right1

right1
{
    type            uniformFixedValue;
    value           nonuniform 0();
    uniformValue    constant (0 0 0);
}

In develop: processor0/0/pointDisplacement.right1

right1
{
    type            uniformFixedValue;
    uniformValue    ( 0 0 0 );
}

At later times this looks different again. Eg, processor0/0.5/pointDisplacement.right1

1812:

right1
{
    type            uniformFixedValue;
    value           nonuniform 0();
    uniformValue    constant (0 0 0);
}

develop:

right1
{
    type            uniformFixedValue;
    value           nonuniform 0();
    uniformValue    nonuniform 0();
}

When this is reconstructed, the generic point patch process the entries quite badly. Even the output for value does not look correct.

@Prashant

Assignee
Assign to
Time tracking