Skip to content

Allow Constraint.Infeasible to be used to disable a Disjunct #2918

Open
@sadavis1

Description

@sadavis1

Rationale

When generating indexed Disjuncts, it may be that some disjuncts contain constraints that are impossible due to the input data. The natural thing to do in that case is to return Constraint.Infeasible in a rule.

Description

Currently, this throws a ValueError at pyomo/core/base/constraint.py:539 . One alternative for the user is to fix the disjunct's indicator variable to False and deactivate it. It would be nice for Constraint.Infeasible to have the same effect when used on a Disjunct.

Additional information

There is a TODO mentioning that this would be good to have, but I figured I would make an issue anyways.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions