pymmcore-plus/pymmcore-plus - CodSpeed

pymmcore-plus

Blog Docs Changelog

Performance History

Latest Results

fix: preserve user-provided fov_width/fov_height in grid plans (#619) * fix: preserve user-provided fov_width/fov_height in grid plans The MDA engine was unconditionally overwriting `grid_plan.fov_width` and `grid_plan.fov_height` with `camera_roi_pixels * pixel_size_um` during `setup_sequence`. This silently discards values supplied by the user via YAML or programmatic construction. Only assign these fields when they are currently `None`, so the engine fills in unset values but leaves user-provided values intact. This is useful when: - the configured pixel size is uncalibrated or known to be wrong - the physical FOV differs from `camera_size * pixel_size` (e.g. oblique plane / light-sheet geometries where the imaged sample area on the XY stage is not the camera footprint) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * reduce attribute access --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Talley Lambert <talley.lambert@gmail.com>

main

2 days ago

Avoid flaky capfd in test (Assisted by Claude Code; any errors are mine.)

marktsuchida:logging-to-mmcore

6 days ago

Replace CLI logs testing with more direct tests Instead of the end-to-end test (which was flaky), test the CLI behavior against files we directly create/modify. And control timing of the tail command for robustness. (Assisted by Claude Code; any errors are mine.)

marktsuchida:logging-to-mmcore

6 days ago

fix: preserve user-provided fov_width/fov_height in grid plans (#619) * fix: preserve user-provided fov_width/fov_height in grid plans The MDA engine was unconditionally overwriting `grid_plan.fov_width` and `grid_plan.fov_height` with `camera_roi_pixels * pixel_size_um` during `setup_sequence`. This silently discards values supplied by the user via YAML or programmatic construction. Only assign these fields when they are currently `None`, so the engine fills in unset values but leaves user-provided values intact. This is useful when: - the configured pixel size is uncalibrated or known to be wrong - the physical FOV differs from `camera_size * pixel_size` (e.g. oblique plane / light-sheet geometries where the imaged sample area on the XY stage is not the camera footprint) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com> * reduce attribute access --------- Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: Talley Lambert <talley.lambert@gmail.com>

main

6 days ago

Fix logging config leak between tests (Assisted by Claude Code; any errors are mine.)

marktsuchida:logging-to-mmcore

7 days ago

Fix logging config leak between tests (Assisted by Claude Code; any errors are mine.)

marktsuchida:logging-to-mmcore

7 days ago

fix: preserve user-provided fov_width/fov_height in grid plans The MDA engine was unconditionally overwriting `grid_plan.fov_width` and `grid_plan.fov_height` with `camera_roi_pixels * pixel_size_um` during `setup_sequence`. This silently discards values supplied by the user via YAML or programmatic construction. Only assign these fields when they are currently `None`, so the engine fills in unset values but leaves user-provided values intact. This is useful when: - the configured pixel size is uncalibrated or known to be wrong - the physical FOV differs from `camera_size * pixel_size` (e.g. oblique plane / light-sheet geometries where the imaged sample area on the XY stage is not the camera footprint) Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

ieivanov:fix/preserve-user-fov-sizes

7 days ago

feat: unified logging via MMCore This uses https://github.com/micro-manager/mmCoreAndDevices/pull/906 and https://github.com/micro-manager/mmCoreAndDevices/pull/909 to send all Python pymmcore-plus logging to CMMCore.log(), with log sinks and rotation handled by MMCore. PYMM_LOG_RICH is removed because there is no Python-side formatting any more. Questions remain about what happens when there is more than one CMMCore, but I think that was already semi-broken. Bumps the required pymmcore version. (Assisted by Claude Code; any errors are mine.)

marktsuchida:logging-to-mmcore

7 days ago

Latest Branches

+94%

feat: unified logging via MMCore#618

6 days ago

8dfe571

marktsuchida:logging-to-mmcore

0%

fix: preserve user-provided fov_width/fov_height in grid plans#619

7 days ago

c361b19

ieivanov:fix/preserve-user-fov-sizes

0%

refactor: delegate per-device timeout to upstream MMCore #914#614

8 days ago

1f759fa

hinderling:feat/wait-for-device-timeout

© 2026 CodSpeed Technology

Home Terms Privacy Docs