pytestlab 0.2.3__tar.gz → 0.2.4__tar.gz

{pytestlab-0.2.3 → pytestlab-0.2.4}/.github/workflows/test.yml

@@ -11,7 +11,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.11", "3.12"]
+        python-version: ["3.11", "3.12", "3.13", "3.14"]
 
     steps:
       - uses: actions/checkout@v4

{pytestlab-0.2.3 → pytestlab-0.2.4}/.pre-commit-config.yaml

@@ -12,14 +12,11 @@ repos:
       - id: ruff
         args: [--fix, --exit-non-zero-on-fix]
       - id: ruff-format
-  - repo: https://github.com/pre-commit/mirrors-mypy
-    rev: v1.10.1
+  - repo: local
     hooks:
-      - id: mypy
-        stages: [pre-commit]
+      - id: ty
+        name: ty
+        entry: uvx ty check
+        language: system
         pass_filenames: false
-        additional_dependencies:
-          - types-PyYAML
-          - types-requests
-          - types-Pillow
-          - types-tqdm
+        stages: [pre-commit]

pytestlab-0.2.4/CHANGELOG.md

@@ -0,0 +1,78 @@
+# Changelog
+
+All notable changes to this project are documented in this file.
+
+The format follows Keep a Changelog (https://keepachangelog.com/en/1.0.0/)
+and the project adheres to Semantic Versioning (https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [v0.2.4] - 2026-05-12
+### Added
+- Added `ptl` as the preferred short CLI entry point while keeping `pytestlab` as a compatibility alias.
+- Added instrument profile verification utilities and CLI coverage for schema, connection, identity, SCPI, and safety-oriented probe checks.
+- Added profile registry tests to lock built-in device type discovery.
+- Added CLI smoke and benchmark scripts for startup and common command paths.
+
+### Changed
+- Split the heavy Typer CLI implementation into a lazy-loaded module so common CLI commands start faster.
+- Updated documentation, examples, and scripts to use `ptl` by default.
+- Lazy-loaded selected package exports in config, experiment, and instrument modules to reduce import-time overhead.
+- Cleaned examples, compliance modules, and tests to pass the current Ruff and ty gates.
+
+### Fixed
+- Fixed CLI bootstrap dispatch so option-bearing commands such as `ptl profile show --help`, `ptl bench validate --help`, and `ptl profile list --profile-dir ...` fall through to Typer instead of being intercepted by fast paths.
+- Fixed compliance typing issues around generic callables and configuration dictionaries.
+- Removed the tracked `.DS_Store` artifact.
+
+## [v0.2.3] - 2025-10-05
+### Added
+- Initial SCPI engine integration for instrument control.
+- Comprehensive plotting utilities and examples.
+- CLI enhancements for a better command-line experience.
+
+### Changed
+- Multimeter module overhaul with improved structure and behavior.
+- Documentation site updates (MkDocs configuration and content).
+- Type-checking and lint configuration refined (mypy and ruff) with project-wide cleanups.
+- Pre-commit and CI adjustments to improve developer workflow and reliability.
+
+### Fixed
+- Type checking issues addressed across modules (targeted mypy fixes and cleaned ignores).
+- Lint violations resolved with ruff adjustments.
+- Release workflow corrections.
+
+### Removed
+- Full removal of legacy async code paths.
+
+## [v0.2.1] - 2025-08-06
+### Added
+- Measurement sweeps and example workflows.
+- Simulation v2 promoted and examples added.
+- New instrument support and profiles (including MSOX2024A; PSU integration via SCPI).
+- GUI and documentation site improvements; language support for docs/examples.
+
+### Changed
+- Significant test stabilization with “all tests passing” milestone and follow-up fixes.
+- Documentation and notebooks improved; site build updated.
+- Initial reduction/removal of legacy async components.
+
+### Fixed
+- Documentation site mobile menu behavior.
+- CI workflows and packaging adjustments.
+- Invalid or flaky tests removed/reworked.
+
+## [0.1.3] - 2025-02-19
+### Added
+- DC Active Load instrument initial support and configuration scaffolding.
+
+### Fixed
+- Early integration fixes and stability improvements around DC Load support.
+
+---
+
+[Unreleased]: https://github.com/labiium/pytestlab/compare/v0.2.4...HEAD
+[v0.2.4]: https://github.com/labiium/pytestlab/compare/v0.2.3...v0.2.4
+[v0.2.3]: https://github.com/labiium/pytestlab/compare/v0.2.1...v0.2.3
+[v0.2.1]: https://github.com/labiium/pytestlab/compare/13b5439...v0.2.1
+[0.1.3]: https://github.com/labiium/pytestlab/commit/13b5439

{pytestlab-0.2.3 → pytestlab-0.2.4}/CONTRIBUTING.md

@@ -6,12 +6,12 @@ This document provides guidelines for contributing to PyTestLab. Please read it
 
 ## Code of Conduct
 
-This project and everyone participating in it is governed by the [PyTestLab Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to `pytestlab-conduct@example.com`.
+This project and everyone participating in it is governed by the [PyTestLab Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code. Please report unacceptable behavior to `support@pytestlab.org`.
 
 ## Getting Started
 
 1.  **Fork the repository** on GitHub.
-2.  **Clone your fork** locally: `git clone https://github.com/YOUR_USERNAME/pytestlab.git`
+2.  **Clone your fork** locally: `git clone https://github.com/labiium/pytestlab.git`
 3.  **Set up the development environment:**
     *   It's recommended to use a virtual environment:
         ```bash
@@ -74,7 +74,7 @@ Now, every time you run `git commit`, the pre-commit hooks will run and check yo
 5.  **Ensure pre-commit checks pass.** If they make changes, `git add` those files and re-commit.
 6.  **Commit your changes** using conventional commit messages (`cz c` or `git cz commit`).
 7.  **Push your branch** to your fork: `git push origin name-of-your-feature`
-8.  **Open a Pull Request (PR)** to the `main` branch of the official PyTestLab repository.
+8.  **Open a Pull Request (PR)** to the `master` branch of the official PyTestLab repository.
     *   Provide a clear title and description for your PR.
     *   Link to any relevant issues.
 

{pytestlab-0.2.3 → pytestlab-0.2.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: pytestlab
-Version: 0.2.3
+Version: 0.2.4
 Summary: Scientific test & measurement toolbox
 Author-email: Emmanuel Olowe <e.a.olowe@ed.ac.uk>
 License: Apache-2.0
@@ -9,7 +9,6 @@ Requires-Python: >=3.11
 Requires-Dist: aiofiles
 Requires-Dist: cryptography
 Requires-Dist: httpx
-Requires-Dist: mypy>=1.17.1
 Requires-Dist: numpy
 Requires-Dist: pillow
 Requires-Dist: polars
@@ -21,6 +20,7 @@ Requires-Dist: pyyaml
 Requires-Dist: requests
 Requires-Dist: ruff>=0.12.9
 Requires-Dist: tqdm
+Requires-Dist: ty>=0.0.1a29
 Requires-Dist: typer
 Requires-Dist: types-pillow>=10.2.0.20240822
 Requires-Dist: types-pyyaml>=6.0.12.20250809
@@ -30,11 +30,11 @@ Requires-Dist: uncertainties
 Provides-Extra: dev
 Requires-Dist: aiofiles; extra == 'dev'
 Requires-Dist: httpx; extra == 'dev'
-Requires-Dist: mypy; extra == 'dev'
 Requires-Dist: pre-commit; extra == 'dev'
 Requires-Dist: pytest; extra == 'dev'
 Requires-Dist: pytest-cov; extra == 'dev'
 Requires-Dist: ruff; extra == 'dev'
+Requires-Dist: ty>=0.0.1a29; extra == 'dev'
 Provides-Extra: docs
 Requires-Dist: ghp-import>=2.1.0; extra == 'docs'
 Requires-Dist: matplotlib>=3.10.3; extra == 'docs'
@@ -86,6 +86,9 @@ Description-Content-Type: text/markdown
      src="https://img.shields.io/badge/docs-latest-blue"/></a>
   <a href="https://opensource.org/licenses/Apache-2.0"><img alt="Apache License"
         src="https://img.shields.io/badge/license-Apache%202.0-blue"/></a>
+  <a href="https://github.com/labiium/pytestlab/actions/workflows/test.yml"><img
+     alt="Tests"
+     src="https://github.com/labiium/pytestlab/actions/workflows/test.yml/badge.svg"/></a>
 </p>
 
 ---
@@ -102,7 +105,7 @@ Description-Content-Type: text/markdown
 * **Bench descriptors** – group multiple instruments in one `bench.yaml`, define safety limits, automation hooks, traceability and measurement plans.
 * **High-level measurement builder** – notebook-friendly `MeasurementSession` for parameter sweeps that stores data as Polars DataFrames and exports straight to the experiment database.
 * **Rich database** – compressed storage of experiments & measurements with full-text search (`MeasurementDatabase`).
-* **Powerful CLI** – `pytestlab …` commands to list/validate profiles, query instruments, convert benches to simulation, replay sessions, etc.
+* **Powerful CLI** – `ptl ...` commands to list/validate profiles, query instruments, convert benches to simulation, replay sessions, etc.
 * **Extensible back-ends** – VISA, Lamb server, pure simulation; drop-in new transports via the `InstrumentIO` protocol.
 * **Docs & examples** – Jupyter tutorials, MkDocs site, and 40+ ready-to-run scripts in `examples/`.
 
@@ -122,7 +125,7 @@ pip install pytestlab[full]     # + plotting, uncertainties, etc.
 ### 2. Hello Oscilloscope (simulated)
 
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 
 def main():
     scope = AutoInstrument.from_config("keysight/DSOX1204G", simulate=True)
@@ -175,14 +178,26 @@ Record real instrument interactions and replay them exactly:
 
 ```bash
 # Record a measurement session
-pytestlab replay record my_measurement.py --bench bench.yaml --output session.yaml
+ptl replay record my_measurement.py --bench bench.yaml --output session.yaml
 
 # Replay the recorded session
-pytestlab replay run my_measurement.py --session session.yaml
+ptl replay run my_measurement.py --session session.yaml
 ```
 
 Perfect for reproducible measurements, offline analysis, and catching script changes!
 
+### 5. Run the Tests
+
+The CI matrix runs `pytest` on Ubuntu for Python 3.11 - 3.14 (see the badges above).
+Replicate the same checks locally with the dev extras installed:
+
+```bash
+pip install -e .[dev]
+pytest tests/ --cov=pytestlab
+```
+
+The suite writes `coverage.xml`, which the workflow uploads to Codecov for the coverage badge.
+
 ---
 
 ## 🔄 Record & Replay Mode
@@ -207,15 +222,15 @@ PyTestLab's **Record & Replay** system enables you to capture real instrument in
 #### Basic Recording & Replay
 ```bash
 # Record a measurement with real instruments
-pytestlab replay record voltage_sweep.py --bench lab_bench.yaml --output sweep_session.yaml
+ptl replay record voltage_sweep.py --bench lab_bench.yaml --output sweep_session.yaml
 
 # Replay the exact sequence (simulated)
-pytestlab replay run voltage_sweep.py --session sweep_session.yaml
+ptl replay run voltage_sweep.py --session sweep_session.yaml
 ```
 
 #### Programmatic Usage
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 from pytestlab.instruments.backends import ReplayBackend
 
 def main():
@@ -332,7 +347,7 @@ with MeasurementSession("Quick Session") as session:
 
 ### Oscilloscope example – Keysight DSOX1204G (simulated)
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 from pytestlab.plotting import PlotSpec
 
 scope = AutoInstrument.from_config("keysight/DSOX1204G", simulate=True)
@@ -354,7 +369,7 @@ PyTestLab features a fluent, chainable API that makes instrument control code cl
 
 ### Power Supply Example
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 
 psu = AutoInstrument.from_config("keysight/E36312A")
 
@@ -429,13 +444,15 @@ PyTestLab's `MeasurementSession` provides a powerful framework for parameter swe
 
 ### Basic Parameter Sweep
 ```python
-from pytestlab.measurements import MeasurementSession
+from pytestlab.measurements import MeasurementSession, step
 import numpy as np
 
 with MeasurementSession("Voltage Response Test") as session:
     # Define sweep parameters
     session.parameter("voltage", np.linspace(0, 5, 10), unit="V")
     session.parameter("delay", [0.1, 0.5], unit="s")
+    # Declarative helpers for non-linear sweeps are available via pytestlab.measurements.step
+    session.parameter("frequency", step.log(start=1e3, stop=1e6, count=50), unit="Hz")
 
     # Setup instruments
     psu = session.instrument("psu", "keysight/EDU36311A", simulate=True)
@@ -667,7 +684,7 @@ PyTestLab provides built-in compliance features for regulated environments:
 ### Automatic Measurement Signing
 ```python
 # Compliance features are automatically enabled
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 
 dmm = AutoInstrument.from_config("keysight/34470A")
 dmm.connect_backend()
@@ -745,7 +762,7 @@ else:
 ## 🧑‍💻 Contributing
 
 Pull requests are welcome! See [`CONTRIBUTING.md`](CONTRIBUTING.md) and the [Code of Conduct](CODE_OF_CONDUCT.md).
-Run the test-suite (`pytest`), type-check (`mypy`), lint/format (`ruff`), and keep commits conventional (`cz c`).
+Run the test-suite (`pytest`), type-check (`uvx ty check`), lint/format (`ruff`), and keep commits conventional (`cz c`).
 
 ---
 

{pytestlab-0.2.3 → pytestlab-0.2.4}/README.md

@@ -24,6 +24,9 @@
      src="https://img.shields.io/badge/docs-latest-blue"/></a>
   <a href="https://opensource.org/licenses/Apache-2.0"><img alt="Apache License"
         src="https://img.shields.io/badge/license-Apache%202.0-blue"/></a>
+  <a href="https://github.com/labiium/pytestlab/actions/workflows/test.yml"><img
+     alt="Tests"
+     src="https://github.com/labiium/pytestlab/actions/workflows/test.yml/badge.svg"/></a>
 </p>
 
 ---
@@ -40,7 +43,7 @@
 * **Bench descriptors** – group multiple instruments in one `bench.yaml`, define safety limits, automation hooks, traceability and measurement plans.
 * **High-level measurement builder** – notebook-friendly `MeasurementSession` for parameter sweeps that stores data as Polars DataFrames and exports straight to the experiment database.
 * **Rich database** – compressed storage of experiments & measurements with full-text search (`MeasurementDatabase`).
-* **Powerful CLI** – `pytestlab …` commands to list/validate profiles, query instruments, convert benches to simulation, replay sessions, etc.
+* **Powerful CLI** – `ptl ...` commands to list/validate profiles, query instruments, convert benches to simulation, replay sessions, etc.
 * **Extensible back-ends** – VISA, Lamb server, pure simulation; drop-in new transports via the `InstrumentIO` protocol.
 * **Docs & examples** – Jupyter tutorials, MkDocs site, and 40+ ready-to-run scripts in `examples/`.
 
@@ -60,7 +63,7 @@ pip install pytestlab[full]     # + plotting, uncertainties, etc.
 ### 2. Hello Oscilloscope (simulated)
 
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 
 def main():
     scope = AutoInstrument.from_config("keysight/DSOX1204G", simulate=True)
@@ -113,14 +116,26 @@ Record real instrument interactions and replay them exactly:
 
 ```bash
 # Record a measurement session
-pytestlab replay record my_measurement.py --bench bench.yaml --output session.yaml
+ptl replay record my_measurement.py --bench bench.yaml --output session.yaml
 
 # Replay the recorded session
-pytestlab replay run my_measurement.py --session session.yaml
+ptl replay run my_measurement.py --session session.yaml
 ```
 
 Perfect for reproducible measurements, offline analysis, and catching script changes!
 
+### 5. Run the Tests
+
+The CI matrix runs `pytest` on Ubuntu for Python 3.11 - 3.14 (see the badges above).
+Replicate the same checks locally with the dev extras installed:
+
+```bash
+pip install -e .[dev]
+pytest tests/ --cov=pytestlab
+```
+
+The suite writes `coverage.xml`, which the workflow uploads to Codecov for the coverage badge.
+
 ---
 
 ## 🔄 Record & Replay Mode
@@ -145,15 +160,15 @@ PyTestLab's **Record & Replay** system enables you to capture real instrument in
 #### Basic Recording & Replay
 ```bash
 # Record a measurement with real instruments
-pytestlab replay record voltage_sweep.py --bench lab_bench.yaml --output sweep_session.yaml
+ptl replay record voltage_sweep.py --bench lab_bench.yaml --output sweep_session.yaml
 
 # Replay the exact sequence (simulated)
-pytestlab replay run voltage_sweep.py --session sweep_session.yaml
+ptl replay run voltage_sweep.py --session sweep_session.yaml
 ```
 
 #### Programmatic Usage
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 from pytestlab.instruments.backends import ReplayBackend
 
 def main():
@@ -270,7 +285,7 @@ with MeasurementSession("Quick Session") as session:
 
 ### Oscilloscope example – Keysight DSOX1204G (simulated)
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 from pytestlab.plotting import PlotSpec
 
 scope = AutoInstrument.from_config("keysight/DSOX1204G", simulate=True)
@@ -292,7 +307,7 @@ PyTestLab features a fluent, chainable API that makes instrument control code cl
 
 ### Power Supply Example
 ```python
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 
 psu = AutoInstrument.from_config("keysight/E36312A")
 
@@ -367,13 +382,15 @@ PyTestLab's `MeasurementSession` provides a powerful framework for parameter swe
 
 ### Basic Parameter Sweep
 ```python
-from pytestlab.measurements import MeasurementSession
+from pytestlab.measurements import MeasurementSession, step
 import numpy as np
 
 with MeasurementSession("Voltage Response Test") as session:
     # Define sweep parameters
     session.parameter("voltage", np.linspace(0, 5, 10), unit="V")
     session.parameter("delay", [0.1, 0.5], unit="s")
+    # Declarative helpers for non-linear sweeps are available via pytestlab.measurements.step
+    session.parameter("frequency", step.log(start=1e3, stop=1e6, count=50), unit="Hz")
 
     # Setup instruments
     psu = session.instrument("psu", "keysight/EDU36311A", simulate=True)
@@ -605,7 +622,7 @@ PyTestLab provides built-in compliance features for regulated environments:
 ### Automatic Measurement Signing
 ```python
 # Compliance features are automatically enabled
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 
 dmm = AutoInstrument.from_config("keysight/34470A")
 dmm.connect_backend()
@@ -683,7 +700,7 @@ else:
 ## 🧑‍💻 Contributing
 
 Pull requests are welcome! See [`CONTRIBUTING.md`](CONTRIBUTING.md) and the [Code of Conduct](CODE_OF_CONDUCT.md).
-Run the test-suite (`pytest`), type-check (`mypy`), lint/format (`ruff`), and keep commits conventional (`cz c`).
+Run the test-suite (`pytest`), type-check (`uvx ty check`), lint/format (`ruff`), and keep commits conventional (`cz c`).
 
 ---
 

{pytestlab-0.2.3 → pytestlab-0.2.4}/docs/en/api/measurements.md

@@ -31,7 +31,7 @@ This abstraction is ideal for automating multi-instrument experiments, batch mea
 
 ```python
 from pytestlab.measurements import MeasurementSession
-from pytestlab.instruments import AutoInstrument
+from pytestlab import AutoInstrument
 
 def main():
     # Create instrument instances (simulated for this example)
@@ -70,4 +70,21 @@ main()
 
 ---
 
+## Step Helpers for Parameters
+
+PyTestLab exposes `pytestlab.measurements.step` helpers so you can succinctly define logarithmic, exponential, geometric, or fully custom sequences for `session.parameter(...)`:
+
+```python
+from pytestlab.measurements import MeasurementSession, step
+
+with MeasurementSession() as session:
+    session.parameter("freq", step.log(start=1e3, stop=1e6, count=100))
+    session.parameter("gain", step.exp(exponent_start=-3, exponent_stop=2, count=25))
+    session.parameter("impedance", step.points([1+1j, 1-1j, -1+1j]))
+```
+
+Each helper returns a `StepSpec` that lazily generates the final iterable just before the sweep runs, keeping scripts tidy while still supporting exotic sweep shapes.
+
+---
+
 For more advanced usage, see the [Experiments & Sweeps API](experiments.md) and the [10-Minute Tour](../tutorials/10_minute_tour.ipynb).

{pytestlab-0.2.3 → pytestlab-0.2.4}/docs/en/changelog.md

@@ -13,7 +13,12 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ## [Unreleased]
 
+## [v0.2.4] - 2026-05-12
+
 ### Added
+- Added `ptl` as the preferred short CLI entry point while retaining the existing `pytestlab` command.
+- Added instrument profile verification utilities and tests.
+- Added CLI smoke and benchmark scripts for startup-sensitive command paths.
 - Initial migration to new documentation structure under `docs/en/`.
 - Enhanced theme and navigation for multilingual and modern Material for MkDocs features.
 - Improved simulation backend documentation and CLI reference.
@@ -21,12 +26,19 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 - Bench descriptor and safety limit documentation improvements.
 
 ### Changed
+- Updated CLI documentation and examples to use `ptl` by default.
+- Split the CLI into a lightweight bootstrap and lazy-loaded Typer implementation for faster common commands.
+- Lazy-loaded selected package exports to reduce import-time overhead.
+- Cleaned examples, compliance modules, and tests for Ruff and ty.
 - Home page and quick start rewritten for clarity and improved onboarding.
 - Installation instructions updated for clarity and VISA backend support.
 - User guide reorganized for better onboarding and discoverability.
 - Custom styles simplified for new theme.
 
 ### Fixed
+- Fixed CLI help and option handling for bootstrap fast paths.
+- Fixed compliance typing issues around generic callables and configuration dictionaries.
+- Removed a tracked `.DS_Store` artifact.
 - Navigation bugs and broken links in documentation.
 - Outdated references to old profile and bench formats.
 
@@ -60,6 +72,7 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 
 ---
 
-[Unreleased]: https://github.com/labiium/pytestlab/compare/v0.1.5...HEAD
+[Unreleased]: https://github.com/labiium/pytestlab/compare/v0.2.4...HEAD
+[v0.2.4]: https://github.com/labiium/pytestlab/compare/v0.2.3...v0.2.4
 [0.1.5]: https://github.com/labiium/pytestlab/releases/tag/v0.1.5
 [0.1.0]: https://github.com/labiium/pytestlab/releases/tag/v0.1.0

{pytestlab-0.2.3 → pytestlab-0.2.4}/docs/en/contributing.md

@@ -67,7 +67,7 @@ All contributors are expected to follow the [PyTestLab Code of Conduct](CODE_OF_
 ## Code Style & Quality
 
 - **Linting & Formatting:** PyTestLab uses [Ruff](https://docs.astral.sh/ruff/) for linting and formatting, and [Black](https://black.readthedocs.io/) for code style. These are enforced by pre-commit.
-- **Type Checking:** Use [MyPy](http://mypy-lang.org/) for static type checking.
+- **Type Checking:** Use [ty](https://docs.astral.sh/ty/) for static type checking (e.g., `uvx ty check`).
 - **Commit Messages:** Follow the [Conventional Commits](https://www.conventionalcommits.org/) specification. Use `cz c` to help format your commit messages.
 
 ---

{pytestlab-0.2.3 → pytestlab-0.2.4}/docs/en/installation.md

@@ -59,8 +59,8 @@ pip install --upgrade pytestlab
 After installation, you can verify that PyTestLab is installed and working:
 
 ```bash
-pytestlab --version
-pytestlab profile list
+ptl --version
+ptl profile list
 ```
 
 If you see a list of available instrument profiles, your installation is successful.

{pytestlab-0.2.3 → pytestlab-0.2.4}/docs/en/profiles/creating.md

@@ -39,7 +39,7 @@ channels:
 2.  **Add Metadata:** Fill in the `manufacturer`, `model`, and `device_type`. The `device_type` must match one of the defined Pydantic config models in `pytestlab.config`.
 3.  **Add Configuration Data:** Refer to the corresponding Pydantic model in the [Configuration API Reference](../api/config.md) and fill in the fields with the specifications from your instrument's datasheet.
 4.  **Save the Profile:** Save the file in a known location. You can then load it directly by its path in `AutoInstrument.from_config()` or place it in `pytestlab/profiles/<vendor>/` to load it by key.
-5.  **Validate:** Use the CLI to validate your new profile: `pytestlab profile validate path/to/your/profile.yaml`.
+5.  **Validate:** Use the CLI to validate your new profile: `ptl profile validate path/to/your/profile.yaml`.
 
 For more complex instruments, you may need to define nested structures for triggers, channels, FFT, etc., as seen in the built-in profiles.