Skip to content

fix: Lock contrast after first FOV during live acquisition#38

Open
hongquanli wants to merge 2 commits intomainfrom
fix/auto-contrast-first-fov-only
Open

fix: Lock contrast after first FOV during live acquisition#38
hongquanli wants to merge 2 commits intomainfrom
fix/auto-contrast-first-fov-only

Conversation

@hongquanli
Copy link
Collaborator

Summary

  • During live acquisition, NDV auto-scales contrast on every data update, causing brightness to jump between FOVs with different signal levels
  • Now reads the auto-computed clims after the first FOV is displayed and switches each channel to ClimsManual, locking contrast for subsequent FOVs
  • Reset on start_acquisition() so each new acquisition gets fresh auto-contrast on its first FOV

Test plan

  • Visually verified: FOV0 (bright) auto-contrasts normally, FOV1 (dim) stays dark, FOV2 (very bright) looks saturated — contrast locked from FOV0
  • 218 tests pass (5 pre-existing failures unrelated to this change)

🤖 Generated with Claude Code

hongquanli and others added 2 commits March 25, 2026 02:50
During live acquisition, NDV auto-scales contrast on every data update,
causing brightness to jump between FOVs with different signal levels.
Now locks contrast to manual mode after the first FOV is displayed,
preserving consistent visualization across FOVs. Reset on new
acquisition.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Retry up to 3 times if clims aren't computed yet (data still loading)
- Narrow except to (ImportError, AttributeError), log at warning level
- Prevent redundant timer scheduling on rapid _update_ndv_data calls

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant