Skip to content

fix: nautilus_plotter.py runs a real capped search instead of test mode - #150

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/nautilus-plotter-real-search-cap
Aug 28, 2026
Merged

fix: nautilus_plotter.py runs a real capped search instead of test mode#150
Jammy2211 merged 1 commit into
mainfrom
feature/nautilus-plotter-real-search-cap

Conversation

@Jammy2211

Copy link
Copy Markdown
Collaborator

Summary

scripts/plot/nautilus_plotter.py failed under PyAutoHeart's release profile: with PYAUTO_TEST_MODE=1 Nautilus stops after its first batch with a single non-zero weight, so the script's range=0.999 collapsed corner's range to a sliver and corner raised ValueError: ... 'range' is not valid or the sample is empty (run 33177898708, job integrate / run_scripts (3.12, autofit, plot)).

A plot example needs a real posterior, and the human declined raising the global test-mode budget in PyAutoFit (it would slow every release-wave search). So this script now declares ENV: real_search in its __Env__ section — the runner releases PYAUTO_TEST_MODE for this one script — and caps the search with n_like_max=3000, the same lever other workspace examples use.

Calibration under the release profile with output/ wiped: 300 / 500 / 1000 calls still crash (Nautilus still in its exploration phase, N_eff = 1); 2000 renders no corner (N_eff = 3); 2500 renders but at N_eff 13–20; 3000 gives N_eff 357–527 in 22–26 s (3/3 stable); natural finish is 3500 calls / 35 s. emcee_plotter.py still runs under test mode (control, exit 0).

The notebook is regenerated (generate.py strips the __Env__ section). Corrective PR for the Heart RED reason release validation FAILED (stage integrate).

Scripts Changed

  • scripts/plot/nautilus_plotter.pyn_like_max=3000 on af.Nautilus; __Env__ (Developer Only) section with ENV: real_search
  • notebooks/plot/nautilus_plotter.ipynb — regenerated

Upstream PR

PyAutoLabs/PyAutoFit#1542

Test Plan

  • nautilus_plotter.py exit 0 under profile_release.yaml, corner rendered, 3/3 runs
  • emcee_plotter.py unchanged under test mode (exit 0)
  • Env resolution: PYAUTO_TEST_MODE absent for this script, still 1 for its siblings
  • Smoke tests pass for all affected workspaces
  • Release integrate autofit / plot job green

Closes #149

Generated by the PyAutoLabs agent workflow.

🤖 Generated with Claude Code

https://claude.ai/code/session_01KeLmyZD5aG6BrTTdJzSmDv

Under the release profile (PYAUTO_TEST_MODE=1) Nautilus stops after its
first batch with one non-zero weight, so the script's range=0.999 collapsed
corner's range to a sliver and corner raised "'range' is not valid or the
sample is empty" (Heart release-integrate run 33177898708). The plot
example needs a real posterior, so the script declares ENV: real_search
(releases PYAUTO_TEST_MODE for this script only) and caps the search with
n_like_max=3000, as other workspace examples do.

Calibration (release profile, output wiped): 300/500/1000 calls still crash
(exploration phase, N_eff 1); 2500 renders but at N_eff 13-20; 3000 gives
N_eff 357-527 in 22-26 s (3/3); natural finish is 3500 calls / 35 s.

Notebook regenerated with autohands generate.py (the __Env__ section is
stripped from it).

Upstream: PyAutoLabs/PyAutoFit#1542 (ESS corner guard).
Closes #149

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01KeLmyZD5aG6BrTTdJzSmDv
@Jammy2211 Jammy2211 added the pending-release PR queued for the next release build label Aug 28, 2026
@Jammy2211
Jammy2211 merged commit 36eebdb into main Aug 28, 2026
6 checks passed
@Jammy2211
Jammy2211 deleted the feature/nautilus-plotter-real-search-cap branch August 28, 2026 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

pending-release PR queued for the next release build

Projects

None yet

Development

Successfully merging this pull request may close these issues.

fix: nautilus_plotter.py opts out of test mode and caps the search with n_like_max

1 participant