Plesty PL Image Scan Experiment
Photoluminescence image scan of a QD chip with etched marker fields, built on
the plesty.lib.experiment framework. For every marker cell the piezo stage
centres the cell in the camera image and captures one image per configured
illumination (marker / qd) at that exact position. Every cell is an atomic,
journaled step: an interrupted scan resumes at the cell it stopped at, and a
partially captured cell is retaken as a whole so its images stay spatially
aligned.
Installation
git clone https://gitlab.com/plesty/hub/experiments/plesty-pl-image-scan.git
cd plesty-pl-image-scan
uv sync
Usage
setup.yaml names the benches the instruments are served from and the device
on each; .env holds their values — the shared data disk and each bench's
address and token (see .env.example). A bench gives the run each device's
address (CAM_ADDRESS, LED_ADDRESS, AMC_ADDRESS). Measurement tuning
(cells, reference alignment, illuminations) lives in config/scan.yaml.
cp .env.example .env # the shared disk, the benches
uv run python -m plesty.pl_image_scan --dry-run # print the planned steps
uv run python -m plesty.pl_image_scan # run the scan
uv run python -m plesty.pl_image_scan --resume <run_id> # continue a stopped run
uv run python -m plesty.pl_image_scan --manifest # the settings it accepts, as JSON
uv run python -m plesty.pl_image_scan.mapping <PLESTY_DATA>/pl-image-scan/<run_id> # the QD map
The docs (docs/) show the rest: the devices, the plan and every setting
(setup.md), starting, resuming and watching a run and what it writes
(running.md), and how the focus and the QD map work and how to read the map
(analysis.md).
Metadata
Release files for plesty-pl-image-scan 0.1.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 |
|---|---|---|---|---|
| plesty_pl_image_scan-0.1.0.tar.gz | 938.9 kB | Without provenance | Details for plesty_pl_image_scan-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| plesty_pl_image_scan-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for plesty_pl_image_scan-0.1.0-py3-none-any.whl |
Total release size: 1.0 MB
Release files / plesty_pl_image_scan-0.1.0.tar.gz
| Download URL | plesty_pl_image_scan-0.1.0.tar.gz |
|---|---|
| Size | 938.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e68a90e16e8380dd05d8d9b8dc5229ce7a4203027c41effe5716ff33228ae5ea
|
|
BLAKE2b-256 checksum How to use checksums |
a05378c2998b2d06a20bbdda5d6e1d27e5fd077450ade8c8c716b4dbe5e28ef9
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / plesty_pl_image_scan-0.1.0-py3-none-any.whl
| Download URL | plesty_pl_image_scan-0.1.0-py3-none-any.whl |
|---|---|
| Size | 89.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ad0c83df431254e4ecba81acbc86dbb2754346526bb59def46acfde0dd71c893
|
|
BLAKE2b-256 checksum How to use checksums |
9932a3bd0a236c7eadc93608cf1e4b720d0050770d6b653a153147d35374f88b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
uv/0.9.30 {"installer":{"name":"uv","version":"0.9.30","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"12","id":"bookworm","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for plesty-pl-image-scan 0.1.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.