Skip to content

critical-curves: decision toward JAX zero-contour in modeling viz + feasibility task - #93

Merged
Jammy2211 merged 1 commit into
mainfrom
feature/pulse-critical-curves-feasibility
Nov 6, 2026
Merged

Jammy2211 merged 1 commit into
mainfrom
feature/pulse-critical-curves-feasibility

Conversation

@Jammy2211

Copy link
Copy Markdown
Contributor

Summary

Records the human decision of 2026-11-06 on the critical-curves campaign: move toward the JAX zero-contour engine for critical curves and caustics drawn during modeling-run visualization, starting with a feasibility phase. The campaign goes needs-decision → active.

It files tasks/critical_curves_jax_modeling_viz_feasibility.md (status ready, research only, no default change). The study covers:

  • correctness on phase-4 posterior draws, per scale, against the pre-registered two-pixel rule;
  • cold and warm cost per visualization call, on CPU and A100;
  • cheap detection of incomplete curves, with a marching-squares fallback;
  • a GO/NO-GO per scale.

It also notes a docs drift: PyAutoGalaxy plot_utils calls zero_contour the default, but the config default is marching_squares.

No measurement, compute or default change.

Test Plan

  • pytest tests (380 passed)
  • bin/pyauto-pulse board --offline / check --offline: OK

🤖 Generated with Claude Code

…iz; file the feasibility task

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Jammy2211
Jammy2211 merged commit 7208ec8 into main Nov 6, 2026
2 checks passed
@Jammy2211
Jammy2211 deleted the feature/pulse-critical-curves-feasibility branch November 6, 2026 10:45
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