pldflow
pldflow is a desktop workflow package for PLD parameter capture and raw-data visualization.
PyPI package name: pldflow
Python import package: pld_workflow
Install from PyPI
python -m pip install pldflow
This installs the parameter form and exposes:
pld-parameter-form
Development install from a Git clone
From the repository root:
python -m venv .venv
source .venv/bin/activate
python -m pip install --upgrade pip
python -m pip install -r requirements-dev.txt
This gives you an editable install of the package plus the optional analysis, visualization, docs, and build dependencies.
Launch commands:
pld-parameter-form
pld-raw-visualizer
python -m pld_workflow
python examples/pld_app_parameter.py
python examples/pld_app_visualizer.py
How from pld_workflow.app import main works
That import does not by itself mean the package is editable-installed. It works in three cases:
- The package is installed normally with
pip install .orpip install pldflow. - The package is installed in editable mode with
pip install -e .. - The caller adds
src/tosys.pathbefore importing.
In this repository, examples/pld_app_parameter.py uses option 3. It prepends src/ to sys.path, so you can run the example directly from the repo root even if the package is not installed. Using pip install -r requirements-dev.txt is still the cleaner setup for daily work.
Visualization dependencies
The raw-data visualizer depends on the companion packages:
AFM-toolsXRD-utilsxrayutilities
Those are included by requirements-dev.txt and by the package extra:
python -m pip install -e ".[visualization]"
If you only want the form application, PyQt5 is the only required runtime dependency.
Windows executable build
PyInstaller build support is included through the build extra:
python -m pip install -e ".[build,visualization]"
python scripts/build_windows_exe.py
Detailed packaging notes are in DISTRIBUTION.md.
Release workflow
GitHub Actions now follows the same release markers used in the AFM and XRD repos.
#majorbumps+1.0.0#minorbumps+0.1.0#patchbumps+0.0.1- no marker runs CI only and does not publish
The workflow builds on every push and pull request to main. When a push to main contains one of the release markers, it creates the next vX.Y.Z tag and publishes to PyPI.
Before the first automated publish, configure PyPI trusted publishing for the pldflow project so GitHub Actions is allowed to upload releases.
Read the Docs
Docs build from docs/source/ using .readthedocs.yaml. Read the Docs should install:
docs/requirements.txt- the package itself from the repo root
Current scope
- Parameter form for PLD growth records
- JSON and HTML export
- Standalone raw-data visualizer for XRD, RSM, and AFM inputs
Metadata
Release files for pldflow 2.0.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 |
|---|---|---|---|---|
| pldflow-2.0.0.tar.gz | 14.8 MB | With provenance | Details for pldflow-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pldflow-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for pldflow-2.0.0-py3-none-any.whl |
Total release size: 14.8 MB
Release files / pldflow-2.0.0.tar.gz
| Download URL | pldflow-2.0.0.tar.gz |
|---|---|
| Size | 14.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d778c53bdd078843eef55734ac076068ba71a2a0df7426b95474810a32ef2798
|
|
BLAKE2b-256 checksum How to use checksums |
ecbeadb591b92b8c111beefc28ff7b2ed97b96185204c76a3182c9af082b1da6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 12, 2026.
Transparency logRelease files / pldflow-2.0.0-py3-none-any.whl
| Download URL | pldflow-2.0.0-py3-none-any.whl |
|---|---|
| Size | 27.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
23727871cda0a90c725f20069c7a7211916ed9738afbdbdc407f078f47aaa8f0
|
|
BLAKE2b-256 checksum How to use checksums |
be5bcea98a0dd7358b39114a843ae58b47f883853a8c60dc54c3c2000f119441
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 12, 2026.
Transparency logSecurity for pldflow 2.0.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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for pldflow-2.0.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Mar 12, 2026.
Transparency logA 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.