文件列表:

.dir-locals.el (252, 2023-11-15)
.dockerignore (98, 2023-11-15)
Dockerfile (433, 2023-11-15)
LICENSE (18092, 2023-11-15)
MANIFEST.in (288, 2023-11-15)
VERSION (5, 2023-11-15)
check_add_col_untyped_args.pyx (166, 2023-11-15)
check_get_solver_with_name.py (505, 2023-11-15)
check_license.py (749, 2023-11-15)
check_sage_testsuite.py (2017, 2023-11-15)
check_testsuite.py (680, 2023-11-15)
docker-setup.sh (697, 2023-11-15)
environment.yml (503, 2023-11-15)
patch_and_check.sh (342, 2023-11-15)
patch_into_sage_module.py (368, 2023-11-15)
requirements.txt (47, 2023-11-15)
sage_numerical_backends_gurobi/ (0, 2023-11-15)
sage_numerical_backends_gurobi/__init__.py (20, 2023-11-15)
sage_numerical_backends_gurobi/gurobi_backend.pxd (4467, 2023-11-15)
sage_numerical_backends_gurobi/gurobi_backend.pyx (45598, 2023-11-15)
setup.py (7657, 2023-11-15)
tox.ini (4346, 2023-11-15)

# sage-numerical-backends-gurobi: Gurobi mixed integer linear programming backend for SageMath [](https://pypi.org/project/sage-numerical-backends-gurobi/ "PyPI: sage-numerical-backends-gurobi") `GurobiBackend` has previously been available as part of the [SageMath](http://www.sagemath.org/) source tree, from which it is built as an "optional extension" if the proprietary Gurobi library and header files have been symlinked into `$SAGE_LOCAL` manually. Because of the proprietary nature of the Gurobi software, `GurobiBackend` is not available in any binary distributions of SageMath. The present standalone Python package `sage-numerical-backends-gurobi` has been created from the SageMath sources, version 9.0.beta10; the in-tree version of `GurobiBackend` has been removed in [Sage ticket #28175](https://trac.sagemath.org/ticket/28175). The present package can be installed on top of various Sage installations using `pip`, including older versions of Sage such as 8.1 (as shipped by Ubuntu bionic 18.04LTS). ## Installation of Gurobi Install Gurobi according to the instructions on the website, which includes obtaining a license key. - On a Linux system, after unpacking the Gurobi archive in the desired location, such as `/opt`, set the environment variable `GUROBI_HOME` to the directory containing the subdirectories `bin`, `lib`, ...: $ export GUROBI_HOME=/opt/gurobi900/linux64 Then adjust your `PATH` (or create symbolic links) so that the interactive Gurobi shell `gurobi.sh` can be found from your `PATH`: $ export PATH="$GUROBI_HOME/bin:$PATH" - On macOS, the Gurobi installer should make the interactive Gurobi shell ``gurobi.sh`` available in `/usr/local/bin` and therefore from your ``PATH``. Verify this by typing the shell command ``gurobi.sh``:: $ gurobi.sh Python 3.7.4 (default, Aug 27 2019, 11:27:39) ... Gurobi Interactive Shell (mac64), Version 9.0.0 Copyright (c) 2019, Gurobi Optimization, LLC Type "help()" for help gurobi> If this does not work, adjust your ``PATH`` (or create symbolic links) so that ``gurobi.sh`` is found. ## Installation of this package This package finds the Gurobi installation using the `GUROBI_HOME` environment variable. (On macOS, it suffices to have `gurobi.sh` in your ``PATH``.) An alternative method of build configuration is to set compiler/linker flags appropriately. In [SageMath 9.1 and newer](https://wiki.sagemath.org/ReleaseTours/sage-9.1#Easier_installation_of_optional_linear_and_mixed_integer_linear_optimization_backends), this package is available as an optional SPKG and can be installed using $ sage -i sage_numerical_backends_gurobi Alternatively, you can install this package from PyPI using $ sage -python -m pip install sage-numerical-backends-gurobi or from a checked out source tree using $ sage -python -m pip install . or from GitHub using $ sage -python -m pip install git+https://github.com/sagemath/sage-numerical-backends-gurobi (See [`build.yml` in the related package sage-numerical-backends-coin package](https://github.com/sagemath/sage-numerical-backends-coin/blob/master/.github/workflows/build.yml) for details about package prerequisites on various systems.) ## Using this package To obtain a solver (backend) instance: sage: from sage_numerical_backends_gurobi.gurobi_backend import GurobiBackend sage: GurobiBackend() Equivalently: sage: from sage_numerical_backends_gurobi.gurobi_backend import GurobiBackend sage: from sage.numerical.backends.generic_backend import get_solver sage: get_solver(solver=GurobiBackend) To use this solver (backend) with [`MixedIntegerLinearProgram`](http://doc.sagemath.org/html/en/reference/numerical/sage/numerical/mip.html): sage: from sage_numerical_backends_gurobi.gurobi_backend import GurobiBackend sage: M = MixedIntegerLinearProgram(solver=GurobiBackend) sage: M.get_backend() To make it available as the solver named `'Gurobi'`, we need to make the new module known as `sage.numerical.backends.gurobi_backend` (note dots, not underscores), using the following commands: sage: import sage_numerical_backends_gurobi.gurobi_backend as gurobi_backend, sage.numerical.backends as backends, sys sage: sys.modules['sage.numerical.backends.gurobi_backend'] = backends.gurobi_backend = gurobi_backend If these commands are executed in a Sage session before any `MixedIntegerLinearProgram` is created, then the new `'Gurobi'` solver wins over the `'GLPK'` solver in the selection of the default MIP backend. To select the `'Gurobi'` solver explicitly as the default MIP backend, additionally use the following command. sage: default_mip_solver('Gurobi') To make these settings permanent, add the above 2 + 1 commands to your `~/.sage/init.sage` file. Note that this setting will not affect doctesting (`sage -t`) because this file is ignored in doctesting mode. ## Running doctests To run the (limited) testsuite of this package, use: $ sage setup.py test If no Gurobi license is available, the testing is skipped without error. To run the Sage testsuite with the default MIP solver set to the backend provided by this package, use: $ sage setup.py check_sage_testsuite If no Gurobi license is available, the testing is skipped without error. ## Running tests with tox The doctests can also be invoked using `tox`: $ tox -e local $ tox -e local check_sage_testsuite.py Testing multiple installed Gurobi versions in parallel (see `tox.ini`): $ tox -p auto ## Overriding the default solver by patching the Sage installation Another method is to patch the module in permanently to the sage installation (at your own risk). This method will affect doctesting. $ sage -c 'import os; import sage.numerical.backends as dm; import sage_numerical_backends_gurobi.gurobi_backend as sm; s = sm.__file__; f = os.path.basename(s); d = os.path.join(dm.__path__[0], f); (os.path.exists(d) or os.path.lexists(d)) and os.remove(d); os.symlink(s, d);' Or use the script [`patch_into_sage_module.py`](patch_into_sage_module.py) in the source distribution that does the same: $ sage -c 'load("patch_into_sage_module.py")' Success: Patched in the module as sage.numerical.backends.gurobi_backend Verify with [`check_get_solver_with_name.py`](check_get_solver_with_name.py) that the patching script has worked: $ sage -c 'load("check_get_solver_with_name.py")' Success: get_solver(solver='gurobi') gives

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：