# Deprecated
To reduce the number of repositories to keep in sync, common plan functionality will be moved to the dls-dodal repository and use of this project discontinued.
dls-bluesky-core
This module stores Bluesky functionality that is common to multiple techniques or groups within the Diamond Light Source organisation, such that it can be imported by instances of BlueAPI, or built upon within more focussed plan repositories to reduce duplication.
The ‘plans’ package contains functions that describe a full operation which performs an experiment and captures data, and may wish to be available to instances of BlueAPI to allow common experiment types to be maintained centrally. The ‘stubs’ package contains modular partial instructions that may act as a building block for constructing plans, for which the implementation is common: e.g. querying APIs, standard handling of metadata The ‘tasks’ package contains instructions that are not sufficient to run a full experiment but are useful utilities for providing functionality to instances of BlueAPI: e.g. moving a motor.
PyPI |
pip install dls-bluesky-core |
Source code |
|
Documentation |
|
Releases |
https://github.com/DiamondLightSource/dls-bluesky-core/releases |
The module built from this repository is intended to either act directly as a source of plans for an instance of BlueAPI by being a planFunctions source in the config of an instance:
worker:
env:
sources:
- kind: planFunctions
module: dls_bluesky_core.plans
- kind: planFunctions
module: dls_bluesky_core.tasks
Or else contributing functionality that may be common with other plan repositories within Diamond.
import dls_bluesky_core.stubs as cps
def technique_specific_plan(*args, **kwargs):
yield from cps.common_diamond_setup()
See https://DiamondLightSource.github.io/dls-bluesky-core for more detailed documentation.
Metadata
Release files for dls-bluesky-core 0.0.4
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 |
|---|---|---|---|---|
| dls_bluesky_core-0.0.4.tar.gz | 55.2 kB | Without provenance | Details for dls_bluesky_core-0.0.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dls_bluesky_core-0.0.4-py3-none-any.whl | Python 3 | none | any | Details for dls_bluesky_core-0.0.4-py3-none-any.whl |
Total release size: 74.8 kB
Release files / dls_bluesky_core-0.0.4.tar.gz
| Download URL | dls_bluesky_core-0.0.4.tar.gz |
|---|---|
| Size | 55.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
36010c1d8f352485940933a7da62b7b4b334477a38b87ae68f37d2aab3f3bb89
|
|
BLAKE2b-256 checksum How to use checksums |
4fd13a9f3d51e1948a372998beeeaa524b21fd6ef5c67f34c8833e8e3ffcd77b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Release files / dls_bluesky_core-0.0.4-py3-none-any.whl
| Download URL | dls_bluesky_core-0.0.4-py3-none-any.whl |
|---|---|
| Size | 19.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
060b69e750b272e6ab2a24eea8b032a3e2573f6b5c9f635af0cb2f3f9da026a1
|
|
BLAKE2b-256 checksum How to use checksums |
e9f638fe0dc4f404c0898098e7e5953feb6a5fb6d7a941b59b1ac9b0b259aec4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.0 CPython/3.12.4
|
Security for dls-bluesky-core 0.0.4
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.