Skip to content

Sensitive to COMMODITY_BALANCE_EPSILON_FOR_CANDIDATES #1397

Description

@tsmbland

Introduced in #1387, I've found that this parameter only really works as intended over a less than 2-orders of magnitude range:

  • too small and it has not impact
  • too big and candidate assets cannot meet the demand

If this is reliable, then maybe that's ok, but I've only tested this with the limited example models in the repo. I also haven't investigate the relationship with the related candidate_asset_capacity parameter. I imagine the relative value of this is important, so it may be better to define the epsilon parameter relative to this, or just hardcode them both.

I also suggested an alternative idea here, which would avoid having to do the dispatch with candidates all together.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    Status
    📋 Backlog

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions