Skip to content

Handling errors in reported lower-bounds #35

@dharabor

Description

@dharabor

It is possible for a reported lower-bound to be proven incorrect, by a subsequently reported plan which has smaller cost. We need a policy for how to handle these situations.

Suggest the following:

  1. Remove all lower-bounds from the same batch as the erroneous instance (we no longer trust any of them)
  2. Revert the claim to the previous best-known value. Note that this requires we keep a history of lower-bound claims for each instance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions