docs: guide choosing iterations_per_quick_update for quick result inspection#65
Merged
Merged
Conversation
…pection al_configure_search: prompt the assistant to actively pick iterations_per_quick_update so the user always gets early, regular fit/sample inspection without visualisation overhead dominating throughput. Rules of thumb (lower for slow/expensive likelihoods e.g. big MGE / pixelised / GPU / high n_live; raise only for very fast likelihoods), and the HPC note that the same value governs what a sync pull surfaces — pick it before submitting. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HD3ZkpFRydshFLeu2V6xDi
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.
Adds guidance to
skills/al_configure_search.mdso the assistant actively choosesiterations_per_quick_updaterather than defaulting it, ensuring the user always gets early, regular fit/sample inspection without visualisation overhead dominating throughput.n_live); raise (~2500–5000) only for very fast likelihoods.sync pullsurfaces — pick it before submitting.🤖 Generated with Claude Code