LDCon
Still in active development.
Laser locking, characterization and a Web dashboard. ECDL and DFB/DBR control are implemented, including ESP32-based native PI and TOPTICA DLCpro adapters.
pip install "ldcon[web,instruments,analysis]"
ldcon-simulate --mode deterministic
ldcon-examples ./my-lab
Python 3.10+ on Linux. experiment-core installs automatically. Optional agent
messaging: pip install "ldcon[agents]" (installs fanharvard-agentbridge).
Provider CLIs and their authentication are separate.
Agents monitor results, diagnose problems and run bounded characterization, parameter tuning and recovery through registered control cards. Humans choose the experiment, target, hardware configuration and physical safety limits, and authorize safety-relevant changes. The fast feedback loop runs on the controller; the agent is not the real-time servo.
Locking and quality: wavemeter feedback drives PI control of ECDL piezo or DFB/DBR current; slower temperature/current corrections and feedforward are available where configured. Quality is reported using frequency error/stability, mode hops, position-independent fringe secondary peaks/width and dither response. Missing data remains unknown; quality labels are distinct from physical safety.
| Configuration | Hardware |
|---|---|
| ECDL / ESP32 | Wavemeter and data feed, ESP32 servo DAC/firmware, piezo driver, current/TEC controllers and supported AWGs (e.g. Siglent SDG) |
| DFB/DBR | Wavemeter, current/TEC controller (e.g. Thorlabs CLD1015); ESP32 DAC and modulation input for native current PI |
| ECDL / DLCpro | TOPTICA DLCpro, wavemeter feedback; AWG/trigger connections for configured feedforward scans |
| Spectral quality / studies | Fringe image source for secondary-peak analysis; scope/telemetry and AWG where required by the selected measurement |
Tests use simulations, fake instruments and loopback services to cover control contracts, owner exclusivity, uncertain writes, cancellation/recovery, tuning, sweeps, configuration, quality reporting and Web behavior. They do not certify a new physical setup. See test suite.
Bundled examples include Sr422, Sr1092 and ThF685 laser definitions, decks and assignments, with output disabled and placeholder connections. Installation starts no hardware or service and includes no credentials. Publishing · MIT license
1 maintainer
Metadata
1 maintainer
Release files for ldcon 0.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 | Provenance | Actions |
|---|---|---|---|---|
| ldcon-0.2.0.tar.gz | 2.1 MB | With provenance | Details for ldcon-0.2.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| ldcon-0.2.0-py3-none-any.whl | Python 3 | none | any | Details for ldcon-0.2.0-py3-none-any.whl |
Total release size: 3.8 MB
Release files / ldcon-0.2.0.tar.gz
| Download URL | ldcon-0.2.0.tar.gz |
|---|---|
| Size | 2.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2b4aeb4bcad79ce0ca67ad0c6d59ae8dd904617e78a99363dc82876aa1e4a840
|
|
BLAKE2b-256 checksum How to use checksums |
fcbc3fcba5f27193d2d2009acd0b834bf8c3cf13064d26b48763970dd6f7a326
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 30, 2026.
Transparency logRelease files / ldcon-0.2.0-py3-none-any.whl
| Download URL | ldcon-0.2.0-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
435fac0dcadb5179031c6206e53a2d54989d0d88f8888d070f430e1cb21d43e6
|
|
BLAKE2b-256 checksum How to use checksums |
158d657999a1b2a830cc667d57854068031f2938b66f402349c39b881288f00e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Oct 30, 2026.
Transparency logSecurity for ldcon 0.2.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
Both files in this release have been uploaded with provenance metadata.
Attestation for ldcon-0.2.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 Oct 30, 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.
