Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • T Trilinos
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 936
    • Issues 936
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 22
    • Merge requests 22
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • James Willenbring
  • Trilinos
  • Issues
  • #4836

Closed
Open
Created Apr 09, 2019 by James Willenbring@jmwilleMaintainer

Tempus: Improve Interval Output Setup

Created by: ccober6

In the output interval and the screen output interval, all the intervals are placed in a vector along with the specified output times or indices, and then sorted. This allowed all the output times and indices to be in one vector and searched. However when the number of time steps reaches millions, the sort is far too expensive. This will rework the interval specification so that it is not part of the vector or sorting.

@trilinos/tempus

Expectations

Work the same as previously but without the costly sorting.

Assignee
Assign to
Time tracking