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 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1672
Closed
Open
Issue created Apr 08, 2020 by Jaap Stolk@jwstolk

waveMaker MultiPaddleFlap crashes if the boundary normal is in the Y direction.

Summary

waveMaker MultiPaddleFlap crashes if the boundary normal is in the Y direction.

Steps to reproduce

in version v1912, copy the multiphase\interFoam\laminar\waves\waveMakerMultiPaddleFlap example.

  • I have swapped X and Y of verices in system/blockMeshDict (attached) and adjusted the vertex order to keep the hex () definition CCW.
  • I swapped the X and Y decomposition in system/decomposeParDict
  • in 0.orig/pointDisplacement, I changed the normal vector to: n (0 1 0)
  • then ran the case using the Allrun script.

Example case

place the attached system/blockMeshDict in the v1912 multiphase\interFoam\laminar\waves\waveMakerMultiPaddleFlap example, and make the 2 additional modifications mentioned above.

What is the current bug behaviour?

It results in a floatingpoint-error in Foam::waveMakerPointPatchVectorField::initialiseGeometry() without any other errors or warnings logged. (see attached log.interFoam)

What is the expected correct behavior?

The calculation should run as the original example, or produce an error message when the waveMaker normal vector is outside the supported range.

I tried to reproduce with minimal changes to an example case. In my original case I had the waveMaker boundary on the -Y side and swapping everything in my case in the x=y line resolved my crash, but now the postprocessing does not follow my other cases that have the waveMaker boundary on the -X side.

Relevant logs and/or images

blockMeshDict log.interFoam

Environment information

  • OpenFOAM version : v1912 (compiled from source)
  • Operating system : ubuntu
  • Hardware info : 2x Intel(R) Xeon(R) E5-2690 2.9 GHz
  • Hardware info : 1x AMD 1950X
  • Compiler : gcc
Assignee
Assign to
Time tracking