fix: skip latents on A100 search submits#30
Merged
Conversation
The first PR-29 submission of the searches/nautilus/imaging/mge A100 run completed Nautilus convergence (log_Z=+31690.50, 65500 evals, 11m40s) but errored in the post-fit latent-variable computation: ValueError: magzero must be passed to the Analysis via kwargs to compute the 'total_lens_flux_mujy' latent. autolens_profiling/config/latent.yaml enables this latent for the latent/imaging/ profiling scripts, but the search-profiling scripts' AnalysisImaging doesn't carry magzero. PYAUTO_SKIP_LATENTS=1 bypasses latent computation entirely — latents are not part of the search profile, and the search itself ran to convergence. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This was referenced May 28, 2026
Jammy2211
added a commit
that referenced
this pull request
May 28, 2026
) PR #30 added PYAUTO_SKIP_LATENTS=1 as a workaround for the magzero-required µJy latents that crashed the first A100 submit. Upstream PyAutoLens commit dd3d09b4 ("fix(latent): raw-flux latents + soft-fail magzero-required µJy", PR #557) replaces the _require_magzero raise with a soft NaN + one warning per process, and adds three magzero-free raw-flux latents that default-on. Search profiling now exercises the full first-class latent pipeline as intended. Co-authored-by: Jammy2211 <JNightingale2211@gmail.com> Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
The first A100 search submit (#29 → job 322548) ran Nautilus to convergence (
log_Z=+31690.50, 65500 evals, 11m40s) but errored in the post-fit latent-variable step:autolens_profiling/config/latent.yamlenablestotal_lens_flux_mujy(needed by thelatent/imaging/per-latent profiling scripts) but the search-profiling scripts'AnalysisImagingdoesn't carrymagzero. Result: the fit completed but_runner.py's metric-JSON write never happened.PYAUTO_SKIP_LATENTS=1bypasses latent computation entirely. Latents aren't part of what the search profile is measuring, and the search itself ran cleanly.A proper upstream fix (so user code doesn't have to set this env var) will be tracked separately in PyAutoPrompt — this is an unblocking workaround for the immediate A100 run.
Test plan
results/searches/nautilus/imaging/mge/hst/hpc_a100_fp64.{json,png}.🤖 Generated with Claude Code