poli 🧪, a library for discrete objective functions
poli is a library of discrete objective functions for benchmarking optimization algorithms.
Black boxes
Features
- 🔲 isolation of black box function calls inside conda environments. Don't worry about clashes w. black box requirements, poli will create the relevant conda environments for you.
- 🗒️ logging each black box call using observers.
- A numpy interface. Inputs are
np.arrays of strings, outputs arenp.arrays of floats. SMILESandSELFIESsupport for small molecule manipulation.
Getting started
To install poli, we recommend creating a fresh conda environment
conda create -n poli-base python=3.9
conda activate poli-base
pip install git+https://github.com/MachineLearningLifeScience/poli.git@dev
To check if everything went well, you can run
$ python -c "from poli import create"
An example: dockstring
In this next example, we estimate the docking score of the example provided in dockstring:
import numpy as np
from poli import objective_factory
problem = objective_factory.create(
name="dockstring",
target_name="drd2"
)
f, x0 = problem.black_box, problem.x0
y0 = f(x0)
# x0: [['C' 'C' '1' '=' 'C' '(' 'C', ...]] (i.e. Risperidone's SMILES)
# y0: 11.9
print(x0, y0)
Cite us and other relevant work
If you use certain black boxes, we expect you to cite the relevant work. Check inside the documentation of each black box for the relevant references.
Where can I find the documentation?
The main documentation site is hosted as a GitHub page here: https://machinelearninglifescience.github.io/poli-docs/
Building the documentation locally
If you install the requirements-dev.txt via
pip install -r requirements-dev.txt
then you will have access to sphinx. You should be able to build the documentation by going to the docs folder and building it:
cd docs/
make html
Afterwards, you can enter the build folder and open index.html.
Metadata
Release files for poli-core 1.3.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 |
|---|---|---|---|---|
| poli-core-1.3.1.tar.gz | 4.7 MB | Without provenance | Details for poli-core-1.3.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| poli_core-1.3.1-py3-none-any.whl | Python 3 | none | any | Details for poli_core-1.3.1-py3-none-any.whl |
Total release size: 9.5 MB
Release files / poli-core-1.3.1.tar.gz
| Download URL | poli-core-1.3.1.tar.gz |
|---|---|
| Size | 4.7 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
754371b5f824f4db7996e4c0d7b72ef1e6340eeef365b1409dc1deb751b197c4
|
|
BLAKE2b-256 checksum How to use checksums |
57189fa1c579722e52f6b1fc60db927b5dbf307c40f2b43bbe654b4e16dc5681
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.22
|
Release files / poli_core-1.3.1-py3-none-any.whl
| Download URL | poli_core-1.3.1-py3-none-any.whl |
|---|---|
| Size | 4.8 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b8d19bf1a221f9d489feb8991342784bf24aa482c4c0fdba1ad111b01a16973f
|
|
BLAKE2b-256 checksum How to use checksums |
024c24f5598bf3620ae0dfad4107b2bbe9f179e5e510f530fd5f80d594e79bf0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.8.22
|
Security for poli-core 1.3.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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A 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.