intelloptim
Distributed black-box optimization built on Optuna's ask/tell API. Evaluators on any infrastructure (HPC, cloud, on-prem) collaborate on a single study through a coordinating server, and the sampler layer treats classical and quantum samplers uniformly.
This package is the client SDK and the sampler layer. It talks to an intelloptim server over HTTP; the server itself is not part of this package. Full documentation: intelloptim.readthedocs.io.
Where it comes from
intelloptim is the evolution of Hopaas, Hyperparameter OPtimization As A
Service (Barbetti & Anderlini, arXiv:2301.05522).
Hopaas was built to coordinate many trainings of a machine-learning model on
opportunistic resources from different providers, which share nothing but a
network connection to a server that holds the study. It tuned the generative
models behind the LHCb ultra-fast simulation, with studies fed by more than
twenty concurrent nodes.
intelloptim keeps that philosophy and generalizes it to any
small-to-moderate-dimensional black-box problem (system calibration, model
tuning, ...), with more robustness and security:
- bearer-token authentication (the token never appears in a URL or in a study's identity) and a client that refuses unsafe token files;
- studies identified by their content and scoped to a user or group, so independent processes join the same study, and a mismatching configuration is refused instead of silently mixed;
- more samplers (Optuna, built-in and quantum policy samplers) behind one API, with background rebuilds for the ones that refit;
enqueue,stop, call quotas and a worker for SLURM.
Installation
pip install intelloptim
Samplers with heavier requirements are optional extras:
| Extra | Adds | For |
|---|---|---|
gp |
torch, scipy |
the Gaussian-process sampler |
qmc |
scipy |
the quasi-Monte Carlo sampler |
quantum |
qiskit |
the simulated quantum samplers |
quantum-ibm |
qiskit-ibm-runtime |
quantum samplers on IBM hardware |
samplers |
gp, qmc, quantum |
everything a server needs to resolve any sampler |
Python 3.11 or newer is required. You also need the URL of a server and an API token.
An Optuna wrapper, with a server
If you know Optuna's ask/tell API, you know the model: a study, trials, a sampler and a pruner, with the study living on a server so that many machines can contribute to it.
import intelloptim as intopt
with intopt.client.Client(url="https://intelloptim.example.org") as client:
study = client.create_study(
study_name="pump-cal-2026-Q2",
direction="minimize",
sampler_spec=intopt.samplers.TPESamplerSpec(seed=42),
parameters=[
intopt.params.Float("k_friction", 1e-3, 1.0, log=True),
intopt.params.Float("bypass_ratio", 0.0, 0.3),
],
)
def objective(trial: intopt.client.Trial) -> float:
k = trial.sampled_float("k_friction")
b = trial.sampled_float("bypass_ratio")
return rms_error_against_telemetry(k, b)
study.optimize(objective, n_trials=200)
print(study.best_trial)
Coming from Optuna? The search space is declared once, in create_study,
and not inside the objective with suggest_*. The objective reads the sampled
values by name (sampled_float, sampled_int, sampled_categorical).
More
-
ask / tell:
optimizeruns the loop;study.ask()andstudy.tell()give you control of it.create_studyis idempotent, so any process that declares the same study joins it. More -
enqueue:
study.enqueue({...})queues a point to evaluate next, andstudy.enqueue({...}, value=...)records one that was evaluated elsewhere. -
prune: report intermediate values and let the study's pruner stop a hopeless trial; it does not count against your call quota. More
def objective(trial: intopt.client.Trial) -> float: for epoch in range(20): loss = train_one_epoch(trial.sampled_float("lr")) trial.report(loss, epoch) if trial.should_prune(): raise intopt.client.errors.TrialPruned return loss
-
samplers: three families behind
sampler_spec=: Optuna (Random, QMC, TPE, GP, NSGA-II), built-in (simulated annealingSA, objective-weighted GaussianOWG) and quantum policy samplers, simulated or on hardware. More
Authentication
Every request carries an API token. The client takes it from the token=
argument, then from the INTELLOPTIM_TOKEN environment variable, then from
~/.config/intelloptim/token, which it only reads if it is a regular file
owned by you with no group or other permissions. Treat the token as a password:
never put it in code, command lines, study specifications or logs, and use
HTTPS for any non-local server.
More
Running on a cluster
intelloptim-worker runs an objective on a batch system without a driver
script. Each task of a SLURM array job imports the objective, joins the study
and runs its trials; worker and site ids come from the SLURM environment.
intelloptim-worker evaluator \
--server https://intelloptim.example.org \
--import objective.py:my_objective \
--n-trials 50
More, with a complete array-job script.
Status
Early development (alpha): the API may still change between minor versions. See CHANGELOG.md for what changed in each release and CONTRIBUTING.md to get involved.
License
Apache-2.0, see LICENSE.
Citation
If you use intelloptim in academic work, please cite the Hopaas paper:
M. Barbetti and L. Anderlini, Hyperparameter Optimization as a Service on INFN
Cloud, arXiv:2301.05522.
Metadata
Release files for intelloptim 0.1.1
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 |
|---|---|---|---|---|
| intelloptim-0.1.1.tar.gz | 180.9 kB | With provenance | Details for intelloptim-0.1.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| intelloptim-0.1.1-py3-none-any.whl | Python 3 | none | any | Details for intelloptim-0.1.1-py3-none-any.whl |
Total release size: 313.9 kB
Release files / intelloptim-0.1.1.tar.gz
| Download URL | intelloptim-0.1.1.tar.gz |
|---|---|
| Size | 180.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40d8156b71bc5c8881d38cf340b374ac505ba9a03028dcd3331e3f3386faeb7f
|
|
BLAKE2b-256 checksum How to use checksums |
9310ad5cc96af3f564aee33bef32f59b627e604b33e45945e588917f57356a45
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logRelease files / intelloptim-0.1.1-py3-none-any.whl
| Download URL | intelloptim-0.1.1-py3-none-any.whl |
|---|---|
| Size | 133.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa2557914092e37d9e6c47c8fa58422409380092a750d883c51b0d2cab6e3a97
|
|
BLAKE2b-256 checksum How to use checksums |
7f0379b5deda36acad90b449ba28e28eda11ecdbadda2f4f75e95daa8f8cf159
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 2, 2026.
Transparency logSecurity for intelloptim 0.1.1
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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for intelloptim-0.1.1.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 Nov 2, 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.