This release is a pre-release and may not be stable for production use.
daq_queuing_service
A service to queue DAQ experiments and chain BlueAPI calls
The service combines a queue with a worker that consumes items in the queue and sends them to blueapi. A REST API is exposed to interact with the queue, allowing users to add, move, cancel, and get information about, items in the queue, and pause/unpause the queue.
| What | Where |
|---|---|
| Source | https://github.com/DiamondLightSource/daq-queuing-service |
| PyPI | pip install daq-queuing-service |
| Docker | docker run ghcr.io/diamondlightsource/daq-queuing-service:latest |
| Documentation | https://diamondlightsource.github.io/daq-queuing-service |
| Releases | https://github.com/DiamondLightSource/daq-queuing-service/releases |
The server is build with FastAPI. For development and testing, it may be useful to have blueapi and the queue service running locally. To get started, install dependencies into a virtual environment and run the app:
uv sync --group dev
source .venv/bin/activate
podman-compose -f tests/system_tests/compose.yaml up # Local rabbitmq
blueapi --config tests/test_data/test_blueapi_config.yaml serve # Local blueapi
daq-queuing-service -p 8001 --dev # Local queue service
To instead run the i15-1 setup in a development environment first clone crystallography-bluesky. Then run:
uv sync --group dev
source .venv/bin/activate
uv pip install -e `PATH_TO_CRYSTALLOGRAPHY_BLUESKY`
podman-compose -f tests/system_tests/compose.yaml up # Local rabbitmq
blueapi --config tests/test_data/i15_1/test_blueapi_config.yaml serve # Local blueapi pointing at i15-1 plans
daq-queuing-service --config tests/test_data/i15_1/test_daq_queue_config.yaml -p 8001 --dev # Local queue service pointing at i15-1 converters
See https://diamondlightsource.github.io/daq-queuing-service for more detailed documentation.
Metadata
Release files for daq-queuing-service 0.2.3a3
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 |
|---|---|---|---|---|
| daq_queuing_service-0.2.3a3.tar.gz | 795.3 kB | Without provenance | Details for daq_queuing_service-0.2.3a3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| daq_queuing_service-0.2.3a3-py3-none-any.whl | Python 3 | none | any | Details for daq_queuing_service-0.2.3a3-py3-none-any.whl |
Total release size: 846.2 kB
Release files / daq_queuing_service-0.2.3a3.tar.gz
| Download URL | daq_queuing_service-0.2.3a3.tar.gz |
|---|---|
| Size | 795.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
dedf70c7db552413565ccd3f1d3ee2c1c645e9a73da1bcaab166bce886ada0d6
|
|
BLAKE2b-256 checksum How to use checksums |
5b21f6408d41140f0e049543a306ac6eb8845c6a82b1d582a08b40309bf8ac89
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Release files / daq_queuing_service-0.2.3a3-py3-none-any.whl
| Download URL | daq_queuing_service-0.2.3a3-py3-none-any.whl |
|---|---|
| Size | 50.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
f917424b6640f376f88727055ae199f303d7dc51baa00b95e2aa7c50f4b0719e
|
|
BLAKE2b-256 checksum How to use checksums |
584447f521eb6a84a05f3e547010403391ebb75fb58d7ed8a6efabde76a24a96
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Security for daq-queuing-service 0.2.3a3
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.