x01dcandClaude Sonnet 5
8cd9235e12
Implements docs/plans/flomni-fermat-asymmetry.md as written: generate the spiral against an inflated fovy half-width (length_axis2 * fermat_asymmetry), then compress the accepted y-coordinate back down by the ratio before storing -- keeps x spacing fixed at step, scales y spacing by the ratio, preserves the requested FOV. Composes with the already-landed sub-step randomization: the offset is subtracted at the raw (pre-compression) scale on both axes, before the inflated-window check, so the offset's phase-shift stays proportional to the local spacing on both axes. Wired through the scan class (FlomniFermatScan), Flomni's global var + queue/CLI plumbing (_TOMO_SCAN_PARAM_NAMES, scan_kwargs, tomo_parameters() print/prompt, _set_default_tomo_params()), and the tomo_params Qt widget (new field with a "?" help button, following the widget's existing offsets-section help-button pattern). Added tests verifying the inflate/compress math directly (against an equivalent call with an inflated FOV and fermat_asymmetry=1.0, same seed) rather than via an approximate spacing-ratio heuristic -- a first attempt at the latter proved too noisy on a Fermat spiral to assert reliably. Updated the flOMNI user docs and the OMNY port TODO (out of scope here, explicitly excludes LamNI per the plan). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Lx3KffiFyyDMKT8vvPENUW
Getting Started with Testing using pytest
BEC is using the pytest framework. It can be installed via
pip install pytest
in your python environment.
We note that pytest is part of the optional-dependencies [dev] of the plugin package.
Introduction
Tests in this package should be stored in the tests directory.
We suggest to sort tests of different submodules, i.e. scans or devices in the respective folder structure, and to folow a naming convention of <test_module_name.py>.
It is mandatory for test files to begin with test_ for pytest to discover them.
To run all tests, navigate to the directory of the plugin from the command line, and run the command
pytest -v --random-order ./tests
Note, the python environment needs to be active.
The additional arg -v allows pytest to run in verbose mode which provides more detailed information about the tests being run.
The argument --random-order instructs pytest to run the tests in random order, which is the default in the CI pipelines.
Test examples
Writing tests can be quite specific for the given function. We recommend writing tests as isolated as possible, i.e. try to test single functions instead of full classes. A very useful class to enable isolated testing is MagicMock. In addition, we also recommend to take a look at the How-to guides from pytest.