Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 455
    • Issues 455
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 15
    • Merge requests 15
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #2468
Closed
Open
Issue created May 12, 2022 by Aaron Endres@ae

potentialFoam creates unphysical velocity field in motorBike tutorial

Summary

In OpenFOAM v2112, potentialFoam creates an unphysical velocity field.

This ultimately leads to the crash of the simulation.

In OpenFOAM v2012, this issue was not present.

Tested in serial as well as in parallel execution, on different Linux versions and on different hardware.

Steps to reproduce

Copy the motorBike tutorial case, execute the Allrun script, look at the 0/U field in paraview.

Example case

motorBike tutorial

What is the current bug behaviour?

in v2112: OFv2112

What is the expected correct behavior?

in v2012: OFv2012

Relevant logs and/or images

Environment information

  • OpenFOAM version : v2112: latest stable release and dev version 'patch = 220310, build = f8dc1929-20220507'
  • Operating system : ArchLinux and OpenSUSE Tumbleweed
  • Hardware info : AMD EPYC 7452 and Intel Xeon CPU E5-2650
  • Compiler : gcc

Possible fixes

Assignee
Assign to
Time tracking