Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • acc acc
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • hla
  • accacc
  • Issues
  • #17

Closed
Open
Created Feb 21, 2018 by Spencer Kiy@spencerkiy🥑Owner

useBIcurve in scale.py takes ~0.4 seconds to run for the tune ios-mws-sebt3a-tigress_ref

Scaling magnetic quads linearly with p/q for the same path takes 30 ms, when useBIcurve is enabled the scale takes 430 ms. This should be investigated and improved upon if possible.

With no BI fit:

(venv-py3) [spencerkiy@hlx lib]$ python scale.py ios-mws-sebt3a-tigress_ref 0.10306835174560547s (time to generate full tuneroot from path and tune files) 0.03018975257873535s (time to scale) 0.00475001335144043s (time to re-parse and print to file) 0.13800811767578125s (total run time)

with BI fit:

(venv-py3) [spencerkiy@hlx lib]$ python scale.py ios-mws-sebt3a-tigress_ref 0.10311174392700195s (time to generate full tuneroot from path and tune files) 0.4269981384277344s (time to scale) 0.0026226043701171875s (time to re-parse and print to file) 0.5327324867248535s (total run time)

Assignee
Assign to
Time tracking