Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
pygwinc
pygwinc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 30
    • Issues 30
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 2
    • Merge Requests 2
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • gwinc
  • pygwincpygwinc
  • Issues
  • #83

Closed
Open
Opened Dec 22, 2020 by Christopher Wipf@christopher.wipfOwner

Sub-budgets at run time

The way pygwinc works now, all noises must be predefined in the budget before it is run. This can be unwieldy, for example when noises are very numerous (e.g. suspensions), or when the relevant noises are not definitely known until runtime (e.g. quantum losses). So it would be useful to have a way of defining sub-budgets at run time.

Edited Dec 22, 2020 by Christopher Wipf
Assignee
Assign to
0.3 release
Milestone
0.3 release
Assign milestone
Time tracking
None
Due date
None
Reference: gwinc/pygwinc#83