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
  • #1445

Closed
Open
Created Sep 23, 2019 by Admin@OpenFOAM-adminMaintainer

courant number calculation and setDeltaT before mesh.update() in solvers

In several dynamic mesh enabled solvers, Courant number calculation and setDeltaT happen before mesh.update().

It doesn't make sense to me, specially in adaptive mesh refinement (AMR) cases. In such cases, after mesh.update(), the pre-calculated courant number is invalidated.

In my experience, every AMR case have failed due to sudden increase of courant number. I had to move mesh.update() prior to "include CourantNo.H" for the case to successfully run

## Reattaching the author to the issue ticket: @maksjood ##

Edited Dec 11, 2019 by Kutalmis Bercin
Assignee
Assign to
Time tracking