NIST Autonomous Formulation Laboratory - Automation Software
This package contains the core laboratory automation software used in the NIST AFL platform.
Its core is the 'DeviceServer' API, a simple way of exposing functionality in simple Python classes to the outside world via HTTP servers. It includes robust item queueing support, output rendering, and hooks to allow for 'smart' generation of user interfaces automatically.
Specific deviceserver instances are provided for a variety of hardware used in the AFL platform: syringe pumps, valves, multiposition flow selectors, UV-Vis spectrometers, x-ray and neutron scattering instruments/beamlines. There are further deviceserver classes that integrate these base devices to perform higher-level functions, e.g. "loading". These classes aim to specify instructions for running a particular protocol in a hardware-agnostic way.
Virtual servers for offline testing
Several stub modules are provided so you can launch the AFL stack without any physical hardware. Running one of these modules the first time creates ~/.afl/config.json containing the Tiled server URL, API key and port bindings. Update this file as needed.
Example commands to start the dummy services:
# start a dummy OT2 robot
python -m AFL.automation.prepare.Dummy_OT2_Driver
# start a virtual sample loader
python server_scripts/virtual_instrument/DummyLoader.py
# optional virtual detectors
python server_scripts/virtual_instrument/VirtualSANS_data.py
python server_scripts/virtual_instrument/VirtualSpec_Data.py
For a full offline demo you can start everything at once:
python server_scripts/virtual_instrument/AllDummy.py
These stub servers expose the same HTTP API as the real hardware allowing you to test an AFL workflow entirely in software.
Production deployment
By default the APIServer will use the waitress WSGI server if it is installed. To fall back to Flask's built-in server pass --no-waitress to AFL.automation.shared.launcher.
Running tests
This repository uses pytest for unit tests. A GitHub Actions workflow runs the
tests automatically on every push and pull request using
.github/workflows/test.yaml. The workflow installs the package along with the
dependencies listed in pyproject.toml.
To execute the tests locally, install the package in editable mode and run
pytest. If the installation fails because the package version cannot be
determined from Git tags, set SETUPTOOLS_SCM_PRETEND_VERSION=0.0.0 as in the
CI workflow:
SETUPTOOLS_SCM_PRETEND_VERSION=0.0.0 pip install -e .
pytest
Metadata
Release files for AFL-automation 1.2.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 | |
|---|---|---|---|
| afl_automation-1.2.0.tar.gz | 18.9 MB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| afl_automation-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 38.5 MB
Release files / afl_automation-1.2.0.tar.gz
| Download URL | afl_automation-1.2.0.tar.gz |
|---|---|
| Size | 18.9 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a0c20dbad4c83c53a22c85044bef8e65a3bf0244df533d21d1fa88b279d21d94
|
|
BLAKE2b-256 checksum How to use checksums |
40eab9d573341510af8f5675ae7d9c3312eaefcd7bb1a895b095fdf6e336f164
|
| 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 Dec 10, 2025.
Transparency logRelease files / afl_automation-1.2.0-py3-none-any.whl
| Download URL | afl_automation-1.2.0-py3-none-any.whl |
|---|---|
| Size | 19.6 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
083fc705b03a34e471668eaa2206d48314e0ca6335f5e814b2b5dc3f040d74b7
|
|
BLAKE2b-256 checksum How to use checksums |
2614b76847ac147550f21a3572586e7883985ac2c486b303c27fcd76e6a0d9d1
|
| 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 Dec 10, 2025.
Transparency log