Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • mHM mHM
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 52
    • Issues 52
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Model experiments
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • mhmmhm
  • mHMmHM
  • Issues
  • #10
Closed
Open
Issue created Aug 14, 2018 by Oldrich Rakovec@rakovecOwner

Muskingum: mRM initialization takes much more time in release 5.9 than in release 5.8 (measurable only for large domains)

Dear all,

Given some inputs from an external user and also confirmed by Pallav, there seems to be a non-negligible time difference between mRM initialization for routing case 1 (=Muskingum) between release 5.8 and 5.9.

I have checked recently myself on one EDgE basin (~120000km2), 30years of simulations, compiled with intel18.

mHM release 5.8: total runtime 13minutes mHM release 5.9: total runtime 22minutes (~11minutes MPR initialization)

Same I did for a smaller basin (~25000km2), the differences were smaller, but also appeared.

Does someone of you have a clue?

Lastly, these are no differences in runtime for the adaptive time stepping (routing case #2 (closed))

Thanks!

Olda

Assignee
Assign to
Time tracking