Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • R rawquant
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 3
    • Issues 3
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Constantine Evans
  • rawquant
  • Issues
  • #3
Closed
Open
Issue created Apr 15, 2020 by Constantine Evans@cgeOwner

Check to see how ramp rate actually works

Currently, the code mostly does the following when temperatures change:

  1. The max across all the absolute values of the temperature differences between the previous step and the new step is taken.
  2. This is divided by the ramp rate of the new step to get the time to start of the new step's hold_time.

It's possible that this could work in other ways. It's also possible that it isn't actually implemented consistently throughout.

Assignee
Assign to
Time tracking