Bluesky Queue Server Client (Qt)
A PyQt5-based graphical interface for the Bluesky Queue Server. This client provides a user-friendly way to manage experimental queues, control the Run Engine (RE) environment, and monitor status in real-time.
Features
- Multi-Protocol Support: Connect via ZMQ or HTTP/HTTPS to your Queue Server.
- Queue Management: Add, remove, edit, and reorder items in the queue.
- Plan Browser: Explore allowed plans and devices with drag-and-drop support for adding plans to the queue.
- Batch Operations: Create and submit batches of plans efficiently.
- RE Control: Start, stop, pause, resume, abort, and halt the Run Engine.
- Environment Management: Open, close, and destroy the worker environment.
- Real-time Monitoring: Live status updates and log monitoring.
- History Tracking: View previously executed plans and clear history.
- Modern UI: Dark-themed interface using the Fusion style.
Installation
Using pip
pip install bluesky-queueserver-qt
Using pixi
If you have pixi installed, you can clone the repository and run:
pixi run start
Usage
Once installed, you can start the application using the command:
bluesky-queueserver-qt
Connecting to a Server
- Click on the Connect button (or go to
File -> Connect). - Choose the protocol (ZMQ or HTTP).
- Enter the server address (e.g.,
localhost:60615for ZMQ orhttp://localhost:8080for HTTP). - (Optional) Provide API keys or credentials if required by your server configuration.
Development
This project uses pixi for development environment management.
# Install dependencies and set up environment
pixi install
# Run the application in development mode
pixi run start
# Run linting
pixi run -e dev ruff check .
License
This project is licensed under the BSD-3-Clause License.
Metadata
Release files for bluesky-queueserver-qt 0.1.3
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 |
|---|---|---|---|---|
| bluesky_queueserver_qt-0.1.3.tar.gz | 28.5 kB | Without provenance | Details for bluesky_queueserver_qt-0.1.3.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| bluesky_queueserver_qt-0.1.3-py3-none-any.whl | Python 3 | none | any | Details for bluesky_queueserver_qt-0.1.3-py3-none-any.whl |
Total release size: 62.9 kB
Release files / bluesky_queueserver_qt-0.1.3.tar.gz
| Download URL | bluesky_queueserver_qt-0.1.3.tar.gz |
|---|---|
| Size | 28.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ae1da7b65102e3f087b69c9acb0ee2c9578402d6e73aeb40f5f3970362de7f1b
|
|
BLAKE2b-256 checksum How to use checksums |
1c2c5ea334d3226748ff3818d7f6884377cf03d39fd8a66423cd51b38b19ed90
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Release files / bluesky_queueserver_qt-0.1.3-py3-none-any.whl
| Download URL | bluesky_queueserver_qt-0.1.3-py3-none-any.whl |
|---|---|
| Size | 34.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7a7af02310a563ef796b2a6125c54e60828bd2385f9fb5e44a8e430262db5a9c
|
|
BLAKE2b-256 checksum How to use checksums |
5edf8f30fb7591a27fe7bc1181678706e8785bc9e3bfa894a6c45cb91723104f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.4
|
Security for bluesky-queueserver-qt 0.1.3
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.