EMEWS QUEUES in SQL for Python
The eqsql package provies an API for HPC workflows to submit tasks (such as simulation model runs) to a queue implemented in a database. eqsql worker pools pop tasks off this queue for evaluation, and push the results back to a database input queue. The tasks can be provided by a Python or R language model exploration (ME) algorithm.
A task is submitted with the following arguments: an experiment id; the task work type; the task payload; an optional priority that defaults to 0; and an optional metadata tag string. The payload contains sufficient information for a worker pool to execute the task and is typically a JSON formatted string, either a JSON dictionary or in less complex cases a simple JSON list. On submission, the API creates a unique task identifier (an integer) for the task and inserts that identifier, the experiment identifier, the work type, and the payload into the EMEWS DB tasks table, together with a task creation timestamp. That task identifier, priority and work type are then inserted into the EMEWS DB output queue table.
API docs are here
1 maintainer
Metadata
1 maintainer
Release files for eqsql 0.15.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 |
|---|---|---|---|---|
| eqsql-0.15.0.tar.gz | 40.3 kB | Without provenance | Details for eqsql-0.15.0.tar.gz |
Release files / eqsql-0.15.0.tar.gz
| Download URL | eqsql-0.15.0.tar.gz |
|---|---|
| Size | 40.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
61e0bd2aac2f82cb771376b701f7c9d60d6034f9a4bc3490ca4b081211a3ca93
|
|
BLAKE2b-256 checksum How to use checksums |
8e383fee6efd5ebc7051a9c14a6ca09fecd9a2e685cddf957e317a3b4333d2f9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.3
|
Security for eqsql 0.15.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.
