pyoframe 0.2.0__py3-none-any.whl → 1.0.0__py3-none-any.whl

pyoframe/_constants.py

@@ -0,0 +1,463 @@
+"""Contains shared constants which are used across the package."""
+
+from __future__ import annotations
+
+import typing
+from dataclasses import dataclass, field
+from enum import Enum
+from typing import Literal
+
+import polars as pl
+import pyoptinterface as poi
+
+COEF_KEY = "__coeff"
+VAR_KEY = "__variable_id"
+QUAD_VAR_KEY = "__quadratic_variable_id"
+CONSTRAINT_KEY = "__constraint_id"
+SOLUTION_KEY = "solution"
+DUAL_KEY = "dual"
+
+
+@dataclass
+class _Solver:
+    name: SUPPORTED_SOLVER_TYPES
+    supports_integer_variables: bool = True
+    supports_quadratic_constraints: bool = True
+    supports_non_convex: bool = True
+    supports_duals: bool = True
+    supports_objective_sense: bool = True
+    supports_write: bool = True
+    accelerate_with_repeat_names: bool = False
+    """
+    If True, Pyoframe sets all the variable and constraint names to 'V'
+    and 'C', respectively, which, for some solvers, was found to improve
+    performance. This setting should only be enabled for a given solver after
+    testing that a) it actually improves performance, and b) the solver can
+    handle conflicting variable and constraint names.
+    So far, only Gurobi has been tested.
+    Note, that when enabled, Model.write() is not supported
+    (unless solver_uses_variable_names=True) because the outputted files would
+    be meaningless as all variables/constraints would have identical names.
+    """
+
+    def __post_init__(self):
+        if self.supports_non_convex:
+            assert self.supports_quadratic_constraints, (
+                "Non-convex solvers typically support quadratic constraints. Are you sure this is correct?"
+            )
+
+    def __repr__(self):
+        return self.name
+
+
+SUPPORTED_SOLVERS = [
+    _Solver("gurobi", accelerate_with_repeat_names=True),
+    _Solver(
+        "highs",
+        supports_quadratic_constraints=False,
+        supports_non_convex=False,
+        supports_duals=False,
+    ),
+    _Solver(
+        "ipopt",
+        supports_integer_variables=False,
+        supports_objective_sense=False,
+        supports_write=False,
+    ),
+    _Solver("copt", supports_non_convex=False),
+]
+
+
+# Variable ID for constant terms. This variable ID is reserved.
+CONST_TERM = 0
+
+RESERVED_COL_KEYS = (
+    COEF_KEY,
+    VAR_KEY,
+    QUAD_VAR_KEY,
+    CONSTRAINT_KEY,
+    SOLUTION_KEY,
+    DUAL_KEY,
+)
+
+
+@dataclass
+class ConfigDefaults:
+    default_solver: SUPPORTED_SOLVER_TYPES | _Solver | Literal["raise", "auto"] = "auto"
+    disable_extras_checks: bool = False
+    enable_is_duplicated_expression_safety_check: bool = False
+    integer_tolerance: float = 1e-8
+    float_to_str_precision: int | None = 5
+    print_polars_config: pl.Config = field(
+        default_factory=lambda: pl.Config(
+            tbl_hide_column_data_types=True,
+            tbl_hide_dataframe_shape=True,
+            fmt_str_lengths=100,  # Set to a large value to avoid truncation (within reason)
+            apply_on_context_enter=True,
+        )
+    )
+    print_max_terms: int = 5
+    maintain_order: bool = True
+    id_dtype = pl.UInt32
+
+
+class _Config:
+    """General settings for Pyoframe (for advanced users).
+
+    Accessible via `pf.Config` (see examples below).
+    """
+
+    def __init__(self):
+        self._settings = ConfigDefaults()
+
+    @property
+    def default_solver(
+        self,
+    ) -> SUPPORTED_SOLVER_TYPES | _Solver | Literal["raise", "auto"]:
+        """The solver to use when [Model][pyoframe.Model] is instantiated without specifying a solver.
+
+        If `auto`, Pyoframe will try to use whichever solver is installed.
+        If `raise`, an exception will be raised when [Model][pyoframe.Model] is instantiated without specifying a solver.
+
+        We recommend that users specify their solver when instantiating [Model][pyoframe.Model] rather than relying on this option.
+        """
+        return self._settings.default_solver
+
+    @default_solver.setter
+    def default_solver(self, value):
+        self._settings.default_solver = value
+
+    @property
+    def disable_extras_checks(self) -> bool:
+        """When `True`, improves performance by skipping checks for extra values (not recommended).
+
+        When `True`, checks for extra values are disabled which effectively means that all expressions
+        are treated as if they contained [`.keep_extras()`][pyoframe.Expression.keep_extras]
+        (unless [`.drop_extras()`][pyoframe.Expression.drop_extras] was applied).
+
+        !!! warning
+            This might improve performance, but it will suppress the errors that alert you of unexpected
+            behaviors ([learn more](../../learn/concepts/addition.md)).
+            Only consider enabling after you have thoroughly tested your code.
+
+        Examples:
+            >>> import polars as pl
+            >>> population = pl.DataFrame(
+            ...     {
+            ...         "city": ["Toronto", "Vancouver", "Montreal"],
+            ...         "pop": [2_731_571, 631_486, 1_704_694],
+            ...     }
+            ... ).to_expr()
+            >>> population_influx = pl.DataFrame(
+            ...     {
+            ...         "city": ["Toronto", "Vancouver", "Montreal"],
+            ...         "influx": [100_000, 50_000, None],
+            ...     }
+            ... ).to_expr()
+
+            Normally, an error warns users that the two expressions have conflicting labels:
+            >>> population + population_influx
+            Traceback (most recent call last):
+            ...
+            pyoframe._constants.PyoframeError: Cannot add the two expressions below because expression 1 has extra labels.
+            Expression 1:   pop
+            Expression 2:   influx
+            Extra labels in expression 1:
+            ┌──────────┐
+            │ city     │
+            ╞══════════╡
+            │ Montreal │
+            └──────────┘
+            Use .drop_extras() or .keep_extras() to indicate how the extra labels should be handled. Learn more at
+                https://bravos-power.github.io/pyoframe/latest/learn/concepts/addition
+
+            But if `Config.disable_extras_checks = True`, the error is suppressed and the sum is considered to be `population.keep_extras() + population_influx.keep_extras()`:
+            >>> pf.Config.disable_extras_checks = True
+            >>> population + population_influx
+            <Expression height=3 terms=3 type=constant>
+            ┌───────────┬────────────┐
+            │ city      ┆ expression │
+            │ (3)       ┆            │
+            ╞═══════════╪════════════╡
+            │ Toronto   ┆ 2831571    │
+            │ Vancouver ┆ 681486     │
+            │ Montreal  ┆ 1704694    │
+            └───────────┴────────────┘
+        """
+        return self._settings.disable_extras_checks
+
+    @disable_extras_checks.setter
+    def disable_extras_checks(self, value: bool):
+        self._settings.disable_extras_checks = value
+
+    @property
+    def enable_is_duplicated_expression_safety_check(self) -> bool:
+        """Setting for internal testing purposes only.
+
+        When `True`, pyoframe checks that there are no bugs leading to duplicated terms in expressions.
+        """
+        return self._settings.enable_is_duplicated_expression_safety_check
+
+    @enable_is_duplicated_expression_safety_check.setter
+    def enable_is_duplicated_expression_safety_check(self, value: bool):
+        self._settings.enable_is_duplicated_expression_safety_check = value
+
+    @property
+    def integer_tolerance(self) -> float:
+        """Tolerance for checking if a floating point value is an integer.
+
+        !!! info
+            For convenience, Pyoframe returns the solution of integer and binary variables as integers not floating point values.
+            To do so, Pyoframe must convert the solver-provided floating point values to integers. To avoid unexpected rounding errors,
+            Pyoframe uses this tolerance to check that the floating point result is an integer as expected. Overly tight tolerances can trigger
+            unexpected errors. Setting the tolerance to zero disables the check.
+        """
+        return self._settings.integer_tolerance
+
+    @integer_tolerance.setter
+    def integer_tolerance(self, value: float):
+        self._settings.integer_tolerance = value
+
+    @property
+    def float_to_str_precision(self) -> int | None:
+        """Number of decimal places to use when displaying mathematical expressions.
+
+        Examples:
+            >>> pf.Config.float_to_str_precision = 3
+            >>> m = pf.Model()
+            >>> m.X = pf.Variable()
+            >>> expr = 100.752038759 * m.X
+            >>> expr
+            <Expression terms=1 type=linear>
+            100.752 X
+            >>> pf.Config.float_to_str_precision = None
+            >>> expr
+            <Expression terms=1 type=linear>
+            100.752038759 X
+        """
+        return self._settings.float_to_str_precision
+
+    @float_to_str_precision.setter
+    def float_to_str_precision(self, value: int | None):
+        self._settings.float_to_str_precision = value
+
+    @property
+    def print_polars_config(self) -> pl.Config:
+        """[`polars.Config`](https://docs.pola.rs/api/python/stable/reference/config.html) object to use when printing dimensioned Pyoframe objects.
+
+        Examples:
+            For example, to limit the number of rows printed in a table, use `set_tbl_rows`:
+            >>> pf.Config.print_polars_config.set_tbl_rows(5)
+            <class 'polars.config.Config'>
+            >>> m = pf.Model()
+            >>> m.X = pf.Variable(pf.Set(x=range(100)))
+            >>> m.X
+            <Variable 'X' height=100>
+            ┌───────┬──────────┐
+            │ x     ┆ variable │
+            │ (100) ┆          │
+            ╞═══════╪══════════╡
+            │ 0     ┆ X[0]     │
+            │ 1     ┆ X[1]     │
+            │ 2     ┆ X[2]     │
+            │ …     ┆ …        │
+            │ 98    ┆ X[98]    │
+            │ 99    ┆ X[99]    │
+            └───────┴──────────┘
+        """
+        return self._settings.print_polars_config
+
+    @print_polars_config.setter
+    def print_polars_config(self, value: pl.Config):
+        self._settings.print_polars_config = value
+
+    @property
+    def print_max_terms(self) -> int:
+        """Maximum number of terms to print in an expression before truncating it.
+
+        Examples:
+            >>> pf.Config.print_max_terms = 3
+            >>> m = pf.Model()
+            >>> m.X = pf.Variable(pf.Set(x=range(100)), pf.Set(y=range(100)))
+            >>> m.X.sum("y")
+            <Expression height=100 terms=10000 type=linear>
+            ┌───────┬───────────────────────────────┐
+            │ x     ┆ expression                    │
+            │ (100) ┆                               │
+            ╞═══════╪═══════════════════════════════╡
+            │ 0     ┆ X[0,0] + X[0,1] + X[0,2] …    │
+            │ 1     ┆ X[1,0] + X[1,1] + X[1,2] …    │
+            │ 2     ┆ X[2,0] + X[2,1] + X[2,2] …    │
+            │ 3     ┆ X[3,0] + X[3,1] + X[3,2] …    │
+            │ 4     ┆ X[4,0] + X[4,1] + X[4,2] …    │
+            │ …     ┆ …                             │
+            │ 95    ┆ X[95,0] + X[95,1] + X[95,2] … │
+            │ 96    ┆ X[96,0] + X[96,1] + X[96,2] … │
+            │ 97    ┆ X[97,0] + X[97,1] + X[97,2] … │
+            │ 98    ┆ X[98,0] + X[98,1] + X[98,2] … │
+            │ 99    ┆ X[99,0] + X[99,1] + X[99,2] … │
+            └───────┴───────────────────────────────┘
+            >>> m.X.sum()
+            <Expression terms=10000 type=linear>
+            X[0,0] + X[0,1] + X[0,2] …
+        """
+        return self._settings.print_max_terms
+
+    @print_max_terms.setter
+    def print_max_terms(self, value: int):
+        self._settings.print_max_terms = value
+
+    @property
+    def maintain_order(self) -> bool:
+        """Whether the order of variables, constraints, and mathematical terms is to be identical across runs.
+
+        If `False`, performance is improved, but your results may vary every so slightly across runs
+        since numerical errors can accumulate differently when the order of operations changes.
+        """
+        return self._settings.maintain_order
+
+    @maintain_order.setter
+    def maintain_order(self, value: bool):
+        self._settings.maintain_order = value
+
+    @property
+    def id_dtype(self):
+        """The Polars data type to use for variable and constraint IDs.
+
+        Defaults to `pl.UInt32` which should be ideal for most users.
+
+        Users with more than 4 billion variables or constraints can change this to `pl.UInt64`.
+
+        Users concerned with memory usage and with fewer than 65k variables or constraints can change this to `pl.UInt16`.
+
+        !!! warning
+            Changing this setting after creating a model will lead to errors.
+            You should only change this setting before creating any models.
+
+        Examples:
+            An error is automatically raised if the number of variables or constraints exceeds the chosen data type:
+            >>> pf.Config.id_dtype = pl.UInt8
+            >>> m = pf.Model()
+            >>> big_set = pf.Set(x=range(2**8 + 1))
+            >>> m.X = pf.Variable()
+            >>> m.constraint = m.X.over("x") <= big_set
+            Traceback (most recent call last):
+            ...
+            TypeError: Number of constraints exceeds the current data type (UInt8). Consider increasing the data type by changing Config.id_dtype.
+            >>> m.X_large = pf.Variable(big_set)
+            Traceback (most recent call last):
+            ...
+            TypeError: Number of variables exceeds the current data type (UInt8). Consider increasing the data type by changing Config.id_dtype.
+        """
+        return self._settings.id_dtype
+
+    @id_dtype.setter
+    def id_dtype(self, value):
+        self._settings.id_dtype = value
+
+    def reset_defaults(self):
+        """Resets all configuration options to their default values.
+
+        Examples:
+            >>> pf.Config.disable_extras_checks
+            False
+            >>> pf.Config.disable_extras_checks = True
+            >>> pf.Config.disable_extras_checks
+            True
+            >>> pf.Config.reset_defaults()
+            >>> pf.Config.disable_extras_checks
+            False
+        """
+        self._settings = ConfigDefaults()
+
+
+Config = _Config()
+
+
+class ConstraintSense(Enum):
+    LE = "<="
+    GE = ">="
+    EQ = "="
+
+    def _to_poi(self):
+        """Converts the constraint sense to its pyoptinterface equivalent."""
+        if self == ConstraintSense.LE:
+            return poi.ConstraintSense.LessEqual
+        elif self == ConstraintSense.EQ:
+            return poi.ConstraintSense.Equal
+        elif self == ConstraintSense.GE:
+            return poi.ConstraintSense.GreaterEqual
+        else:
+            raise ValueError(f"Invalid constraint type: {self}")  # pragma: no cover
+
+
+class ObjSense(Enum):
+    MIN = "min"
+    MAX = "max"
+
+    def _to_poi(self):
+        """Converts the objective sense to its pyoptinterface equivalent."""
+        if self == ObjSense.MIN:
+            return poi.ObjectiveSense.Minimize
+        elif self == ObjSense.MAX:
+            return poi.ObjectiveSense.Maximize
+        else:
+            raise ValueError(f"Invalid objective sense: {self}")  # pragma: no cover
+
+
+class VType(Enum):
+    """An [Enum](https://realpython.com/python-enum/) that can be used to specify the variable type.
+
+    Examples:
+        >>> m = pf.Model()
+        >>> m.X = pf.Variable(vtype=VType.BINARY)
+
+        The enum's string values can also be used directly although this is prone to typos:
+
+        >>> m.Y = pf.Variable(vtype="binary")
+    """
+
+    CONTINUOUS = "continuous"
+    """Variables that can be any real value."""
+    BINARY = "binary"
+    """Variables that must be either 0 or 1."""
+    INTEGER = "integer"
+    """Variables that must be integer values."""
+
+    def _to_poi(self):
+        """Convert the Variable type to its pyoptinterface equivalent."""
+        if self == VType.CONTINUOUS:
+            return poi.VariableDomain.Continuous
+        elif self == VType.BINARY:
+            return poi.VariableDomain.Binary
+        elif self == VType.INTEGER:
+            return poi.VariableDomain.Integer
+        else:
+            raise ValueError(f"Invalid variable type: {self}")  # pragma: no cover
+
+
+class ExtrasStrategy(Enum):
+    """An enum to specify how to handle extra values in expressions."""
+
+    UNSET = "not_set"
+    DROP = "drop"
+    KEEP = "keep"
+
+
+# This is a hack to get the Literal type for VType
+# See: https://stackoverflow.com/questions/67292470/type-hinting-enum-member-value-in-python
+ObjSenseValue = Literal["min", "max"]
+VTypeValue = Literal["continuous", "binary", "integer"]
+for enum, type in [(ObjSense, ObjSenseValue), (VType, VTypeValue)]:
+    assert set(typing.get_args(type)) == {vtype.value for vtype in enum}
+
+SUPPORTED_SOLVER_TYPES = Literal["gurobi", "highs", "ipopt", "copt"]
+assert set(typing.get_args(SUPPORTED_SOLVER_TYPES)) == {
+    s.name for s in SUPPORTED_SOLVERS
+}
+
+
+class PyoframeError(Exception):
+    """Class for all Pyoframe-specific errors, typically errors arising from improper arithmetic operations."""
+
+    pass