Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 92
    • Merge requests 92
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositoriesdumux-repositories
  • dumuxdumux
  • Issues
  • #1045
Closed
Open
Issue created Jun 17, 2021 by Leopold Stadler@leopold.stadlerMaintainer

improve time information in TimeLoop

Feature request

There are two small issues about the output of time information in the class TimeLoop.

  1. The output format of wall clock time and other CPU times is in a low precision {:.2g}, so it is impossible to measure the time in detail.

  2. (Optional) The output shows Simulation took but Time loop took seams more consistent since only the time of the time loop is measured.

For parallel computations the start-up (partitioning etc.) may take a lot of time and this time belongs also to as simulation, but is not measured by TimeLoop.

What does this feature / why does DuMux need it:

  • Change the precision to {:.5g} for Wall clock time, Simulation took and the cumulative CPU time

  • (Optional) Rename Simulation took to Time loop took

DuMux needs a higher output precision for time related information to allow users to measure the time used by the time loop for performance studies, benchmarks and checking/plotting the convergence. Making a plot of **Wall clock time** and time or time step size only works if all variables are given in a sufficient precision.

Which issue does this feature fix (if any)

Anything else we need to know?:

This issue is related to #916 (closed) I'm not sure if the formulation Simulation took has been explicitly chosen instead of something like Time loop took.

Edited Jun 18, 2021 by Leopold Stadler
Assignee
Assign to
Time tracking