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 415
    • Issues 415
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #107
Closed
Open
Issue created Apr 28, 2016 by Prashant Sonakar@PrashantDeveloper

BUG: Erroneous output/crash for forceCoeffs and forceCoeffBins using *Mean values

When averaging of the field is activated at later time in simulation, using them for forces FO can lead to failure.

  • using evaluateControl is one solution

But when no information is provided, it produces

  • erroneous output for forceCoeffs
  • crash when using forceCoeffsBin

motorBike_forceCoeff-withMeanValues.tgz

Assignee
Assign to
Time tracking