Repository navigation
Conversation
…eplaces it The plugin (Localize/Bead calibration), its window (calibrate/qt_gui.py), its assistant actions and its pages are removed. The bead average is the PSF calibration window's, which already had every page, the bead table and the assistant's actions; its method's explanation moves to a widgetless help page, Panels/Bead average. smappy-calibrate opens the PSF calibration window (headless --out unchanged). The tests of the use_calibration hand-over and of the bead settings' forms are kept. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014JegwAEzHHExiXkwvXgA2j
…est tested on the minimal pupil From round 2, once the coverslip edge has set the focus, a unit localised more than 3 errors below the coverslip (its CRLB times the edge's scatter factor, with the edge's own error) is not chosen (`insitu_rounds.below_coverslip`, `RoundSettings.below_coverslip_sd`): the z bins below 0 had filled with molecules the model placed badly. The twin test already mirrored held modes; a test now pins it for the minimal pupil, in situ's default. The roadmap's in situ line and the architecture's known flaws brought up to date. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014JegwAEzHHExiXkwvXgA2j
…U-only PyTorch beside an NVIDIA card The line Detect writes now ends with where learning runs (uipsf.device.describe: the graphics card by name, Apple's GPU or the CPU). A torch built for the CPU only on a machine with an NVIDIA card (torch_install.cpu_build_on_nvidia, from its version's local label: a plain pip install on Windows brings it) learnt on the CPU without a word; the window now says so and offers Install PyTorch, whose command then reinstalls the card's build from the CUDA index (command(replace=True)), and asks for a restart where the old build is already loaded. Neither blocks a run. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014JegwAEzHHExiXkwvXgA2j
…er height, from the molecules' heights heights.py localises every molecule of the nucleus movie once per model and saves height, CRLB, ½ Σ deviance, chip position and frame; tilt_from_edge.py fits the coverslip's edge per tile and a plane through it (a real 1.6° tilt is ~28 nm per µm), edge_vs_time.py the edge per block of frames, score_by_height.py two models' scores per height bin on the unseen molecules. Smoke-tested here on synthetic files (a planted 1.6° tilt read as 1.63°, a planted drift and a height-dependent score recovered) and heights.py on a small simulated movie; not yet run on M2's data, which are not in git. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014JegwAEzHHExiXkwvXgA2j
…ta against the images Every M2 in situ run's twin test prefers the mirrored pupil, which a ZPositionUm running opposite to the code's convention would give (beads and sweeps on the glass cannot tell the twin). The script prints the files' z tags and direction, the sweeps' and bead stacks' spot elongation at the smallest and largest stage z, and the elongation of the movie's glass molecules, below the focus in its first frames: opposite to the smallest stage z's if the convention holds. Smoke-tested on simulated files; not run on M2's data. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_014JegwAEzHHExiXkwvXgA2j
# Conflicts: # benchmarks/uipsf/real/m2_pairs/tilt_from_edge.py # docs/uipsf/architecture.md
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Every M2 in situ run's twin test prefers the mirrored pupil, by 800–1500 nats. A stage z running opposite to the code's convention would give exactly that:
ZPositionUmas the objective raised.calibrate.input.read_bead_stacks).molecule_stack).What it checks
benchmarks/uipsf/real/m2_pairs/z_direction.py, model-free:ZPositionUmcomes from, and any PI or focus device beside it), their first and last values and direction.If the convention holds, the glass molecules are elongated the opposite way to the stack spots at the smallest stage z. The same way means the stage z runs opposite to the convention for these files, and every M2 bead and sweep model is the twin.
A paragraph in the M2 section of
docs/uipsf/architecture.mdpoints to it.Checked
PositionZper plane gives the right direction and elongation, and a simulated movie's early glass excess is read on the right side.ruff check benchmarks/uipsf/real/m2_pairsis clean.Tests
--slowwas not run: the PR adds only a benchmark script and documentation.Generated by Claude Code