Liquid Engine
Liquid Engine - Accelerating Bioimage Analysis with dynamic selection of algorithm variations
Liquid Engine
The Liquid Engine is a high-performance, adaptive framework designed to optimize computational workflows for bioimage analysis. It dynamically generates optimized CPU and GPU-based code variations and selects the fastest combination based on input parameters and device performance, significantly enhancing computational speed. The Liquid Engine employs a machine learning-based Agent to predict the optimal combination of implementations, adaptively responding to delays and performance variations.
Key features include:
- Multiple Implementations: Utilizes various acceleration strategies such as PyOpenCL, CUDA, Cython, Numba, Transonic, and Dask to deliver optimal performance.
- Machine Learning Agent: Predicts the best-performing implementation combinations and adapts dynamically to ensure maximum efficiency.
- Automatic Benchmarking: Continuously benchmarks different implementations to maintain a historical record of runtimes and improve performance over time.
- Seamless Integration: Can easily be integrated into any existing workflow with no extra work for end users.
The Liquid Engine's adaptability and optimization capabilities make it a powerful tool for researchers handling extensive microscopy datasets and requiring high computational efficiency.
if you found this work useful, please cite: preprint and
Instalation
Liquid Engine is compatible and tested with Python 3.9, 3.10 and 3.11 in MacOS, Windows and Linux.
You can install Liquid Enginevia pip:
pip install liquid_engine
License
Distributed under the terms of the CC-By v4.0 license, "Liquid Engine" is free and open source software
Issues
If you encounter any problems, please file an issue along with a detailed description.
Metadata
Release files for liquid-engine 0.2.0
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 |
|---|---|---|---|---|
| liquid_engine-0.2.0.tar.gz | 14.3 kB | Without provenance | Details for liquid_engine-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| liquid_engine-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for liquid_engine-0.2.0-py3-none-any.whl |
Total release size: 28.7 kB
Release files / liquid_engine-0.2.0.tar.gz
| Download URL | liquid_engine-0.2.0.tar.gz |
|---|---|
| Size | 14.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
88f95498580bb0e47a9bc53bf8c01fc2b5f12d2aa16719cd9941886265370852
|
|
BLAKE2b-256 checksum How to use checksums |
ba6b7fcdf771dac965b92c282d775b53feba839cd085168bbdfb068edfa326df
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Release files / liquid_engine-0.2.0-py3-none-any.whl
| Download URL | liquid_engine-0.2.0-py3-none-any.whl |
|---|---|
| Size | 14.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5fb7d6471e09ea29cb51468d5abdc416802d6a9262677febe0469202e17ded0f
|
|
BLAKE2b-256 checksum How to use checksums |
91ad5d148a9077fcf7de13acde787681fd24bcf58c9ae57086a9c4083733326a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Security for liquid-engine 0.2.0
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.