x01dcandClaude Sonnet 5
8a7a350280
FlomniFermatScan/LamNIFermatScan already refuse to run with fewer than 20 positions (_check_min_positions(), raises ScanAbortion), but only once the scan actually starts -- too late for an unattended tomo-queue run, where the job just aborts mid-run and pauses the queue. Surface the same prediction earlier instead, as a non-blocking warning: - Extracted the position-generating methods on both scan classes (get_flomni_fermat_spiral_pos, and lamni's chain -- _lamni_compute_scan_center, _lamni_compute_stitch_center, _compute_total_shift, _lamni_check_pos_in_fov_range_and_circ_fov, get_lamni_fermat_spiral_pos) into pure @staticmethods, so the exact same algorithm the scan server runs can also be called from client-side code without a live scan session. Behavior-preserving -- verified against the existing exact-position/instruction assertion tests for both classes. Lifted the hardcoded "20" into a _MIN_POSITIONS class attribute on each, so client code references the same threshold. - lamni.py/flomni.py: new _expected_fermat_position_count() calls the real scan-class algorithm with the live tomo parameters and prints a warning line in tomo_parameters() when below the minimum. - tomo_params.py: a new live-updating "Estimated Fermat scan points" field (mirroring the existing achievable-step preview's styling), wired to the fov/step/stitch/piezo-range fields, flagged orange below the minimum -- never blocks Submit/Add-to-queue. lamni's circular-FOV crop is angle/stitch-dependent, so the estimate is representative (center tile, angle 0 for the CLI; the live stitch tile for the GUI, which has those fields right there) rather than an exact per-projection guarantee -- documented as such in both places. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.