Skip to content
GitLab
  • Menu
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 381
    • Issues 381
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1681
Closed
Open
Created Apr 15, 2020 by Prashant Sonakar@PrashantDeveloper

SPDP : time precision

Functionality to add/problem to solve

The time is stored as scalar, which can accumulate truncation errors. This can show problems with follow-on applications e.g. noise

Proposal

  • Change storage of time as e.g. solveScalar and adjust API accordingly.
  • look at interpolating times e.g. temporalInterpolate

What does success look like, and how can we measure that?

  • damBreak tutorial example with changes in controlDict writeControl = runTime, adjustableTimeStep=false
  • run in SPDP or SP mode.
  • till 0.3 folders are good, but later have fractions e.g. 0.349999

@andy @Mattijs

Edited Apr 15, 2020 by Prashant Sonakar
Assignee
Assign to
Time tracking