Ticket #168 (accepted defect)

Opened 4 years ago

Last modified 17 months ago

How to expose contingency information

Reported by: KevinLai Owned by: KevinLai
Priority: high Milestone: 0.5.4 Stability/Security/Performance
Component: Auctioneer Version:
Severity: normal Keywords:
Cc:

Description

How should the contingency scheduler parameters be exposed for the Best Response algorithm?

Change History

Changed 3 years ago by KevinLai

  • priority changed from normal to high

Changed 17 months ago by KevinLai

  • status changed from new to accepted
  • milestone changed from 1.0.0 Unscheduled to 0.5.4 Stability/Security/Performance
Note: See TracTickets for help on using tickets.