This release is a pre-release and may not be stable for production use.
omnibias-discrete
A decision needs more than rounding. Represent a relaxation, decode a candidate, then measure its gap.
Static poster · Narrow-screen animation · How this visual is computed
A discrete problem, relaxation schedule and candidate enter a shared optimization interface. Relaxed values, a decoded assignment and an independently justified optimality gap leave. Front-ends supply the objective and feasible-set meaning.
The animation uses computed outputs to explain this package. Frame transitions are illustrative unless a training step is explicitly identified; it is not a performance comparison.
API reference · Source · Tests · Talk to Derivon
The mathematical connection
Temperature collapse provides a route from continuous relaxation toward discrete candidates. Finite β does not guarantee an integral or globally optimal result; decoding and lower bounds remain separate stages, including at ties. Bias-collapse backends may differentiate a smooth objective, but the problem/anneal/decode/certify contract is the package’s distinctive role.
Run this README
The examples use omnibias-discrete on Python >=3.10. Their installed-wheel
profile selects runtime features, not an editable workspace. Install the prepared
prerelease from PyPI:
python -m pip install --pre "omnibias-discrete==0.1.0a2"
For local development before publication, build and test the coordinated wheelhouse using the release guide. The package's wheel profile executes the examples below outside the source checkout.
Existing published consumers may need historical primitive versions; see the compatibility policy.
Why this package exists
Discrete applications often repeat the same infrastructure: represent an energy, relax binary variables, sharpen a temperature schedule, round a candidate and compare it with a bound. Discrete gives those steps explicit interfaces, so consumers can specialize a problem without copying its optimization plumbing.
What you can build
- DiscreteProblem and DiscreteSolution interfaces.
- Annealed Torch/JAX relaxation and reusable proposers.
- Rounding, local descent, bounded brute-force oracles and optimality-gap certificates.
Use this primitive under QUBO, routing, logic or other discrete frontends. A feasible candidate and a lower bound are independently useful outputs: the candidate supplies an actionable decision, while the bound quantifies what remains unproven about its quality.
A working example
import numpy as np
from omnibias.discrete import AnnealSchedule, round_relaxed
schedule = AnnealSchedule(beta0=0.5, beta_growth=2.0, stages=4)
assert schedule.betas() == [0.5, 1.0, 2.0, 4.0]
probabilities = np.array([0.1, 0.8, 0.3])
candidate = round_relaxed(probabilities)
assert np.array_equal(candidate, [0., 1., 0.])
# Rounding creates a candidate; certify_gap needs a separately justified bound.
Choose the right contract
Temperature hardening does not make a difficult discrete search globally optimal. Keep feasibility, objective value, bound provenance and certificate status separate. Brute-force enumeration is only a small-instance oracle. Optional SOS or convex backends provide specific bounds under their own assumptions.
Explore and validate
The API guide contains the generated module/export inventory. Use it to find the focused implementation rather than guessing a symbol from another package. The capability map connects the primitives to larger scientific workflows.
From the main repository, run the package’s regression suite:
uv run pytest packages/omnibias-discrete/tests -q
License
AGPL-3.0-or-later or commercial. See LICENSE and the licensing policy. Comply with the AGPL terms or obtain a signed commercial grant; commercial use alone does not require payment. Commercial terms describe the alternative. Previously distributed Apache editions, where applicable, retain their original grants.
Metadata
Release files for omnibias-discrete 0.1.0a2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| omnibias_discrete-0.1.0a2.tar.gz | 44.1 kB | With provenance | Details for omnibias_discrete-0.1.0a2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| omnibias_discrete-0.1.0a2-py3-none-any.whl | Python 3 | none | any | Details for omnibias_discrete-0.1.0a2-py3-none-any.whl |
Total release size: 87.3 kB
Release files / omnibias_discrete-0.1.0a2.tar.gz
| Download URL | omnibias_discrete-0.1.0a2.tar.gz |
|---|---|
| Size | 44.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
9b767844604767dae9c32f2b49690b2670748204cd39c880506c1ae5cca21253
|
|
BLAKE2b-256 checksum How to use checksums |
c1c25bf29956526f02d397c382dc0a6308c53afa6f81b080deda12dd3a1131a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logRelease files / omnibias_discrete-0.1.0a2-py3-none-any.whl
| Download URL | omnibias_discrete-0.1.0a2-py3-none-any.whl |
|---|---|
| Size | 43.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
198677cdd4f5affbe6f7f7dd35e00673ed727bf609545712ee68e59e7fcfe81e
|
|
BLAKE2b-256 checksum How to use checksums |
e38a6db9a7935d4ffc2e4fed99324decb3fe2beab3ea1c6d6d176c78a8fde0d9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logSecurity for omnibias-discrete 0.1.0a2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for omnibias_discrete-0.1.0a2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 4, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.