chore: entry-point cleanup — delete run_search.py, prune one-off console scripts#10
Merged
Conversation
- Remove chained-eclipse-total-tracks-2027 and chained-eclipse-eclipse4-atlanta from [project.scripts]; they are one-off analyses and stay runnable via python -m chained_eclipse.<module>. - Point the README quick-start and reproducible modes at the chained-eclipse console script instead of run_search.py (deleted in the next commit).
It duplicated the chained-eclipse console script installed by [project.scripts]; the README now points at the console script.
13 tasks
wiyth00
added a commit
that referenced
this pull request
Jul 25, 2026
…--resume Item 15: - argparse --version prints package version, MODEL_VERSION, and kernel name. - Stage progress messages use the logging module (INFO default, --quiet for warnings only, --verbose for debug). Data outputs (json dumps, headline) stay on stdout. terminal_summary.txt is byte-identical. Deferred #12 follow-ups: - --allow-unverified-ephemeris is wired through every mode's load_ephemeris. - events.json records the kernel digest from the verified context (no re-hash) plus the new verified flag. - run_manifest.json command string reflects the real entry point (the old string referenced run_search.py, deleted in #10) and records resume use. Item 16: - --resume reuses per-stage artifacts in --output when a resume_manifest records matching model_version, config sha256, and kernel sha256; refuses to resume across any mismatch. Stages 1 (enumeration/screening), 2 (validation), 3 (optimized design), and 5 (stability) are checkpointable; stage 4 is always recomputed because fixed-system ground tracks are not serialized and downstream figures need them. - New tests cover parser flags, the version string, a --version subprocess run, and the pure resume-guard helper.
5 tasks
wiyth00
added a commit
that referenced
this pull request
Jul 25, 2026
#14) Item 15: - argparse --version prints package version, MODEL_VERSION, and kernel name. - Stage progress messages use the logging module (INFO default, --quiet for warnings only, --verbose for debug). Data outputs (json dumps, headline) stay on stdout. terminal_summary.txt is byte-identical. Deferred #12 follow-ups: - --allow-unverified-ephemeris is wired through every mode's load_ephemeris. - events.json records the kernel digest from the verified context (no re-hash) plus the new verified flag. - run_manifest.json command string reflects the real entry point (the old string referenced run_search.py, deleted in #10) and records resume use. Item 16: - --resume reuses per-stage artifacts in --output when a resume_manifest records matching model_version, config sha256, and kernel sha256; refuses to resume across any mismatch. Stages 1 (enumeration/screening), 2 (validation), 3 (optimized design), and 5 (stability) are checkpointable; stage 4 is always recomputed because fixed-system ground tracks are not serialized and downstream figures need them. - New tests cover parser flags, the version string, a --version subprocess run, and the pure resume-guard helper.
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.
Summary
run_search.py. It was a 9-line duplicate of thechained-eclipseconsole script already installed via[project.scripts].chained-eclipse-total-tracks-2027andchained-eclipse-eclipse4-atlantafrom[project.scripts]. They are one-off analyses that were being installed onto every user's PATH. The modules stay runnable viapython -m chained_eclipse.total_tracks_2027/python -m chained_eclipse.eclipse4_atlanta— which is already exactly how the README documents them — and the README now says explicitly that this is intentional.uv run chained-eclipse --mode full, and the four "Reproducible modes" examples use.venv/bin/chained-eclipse --mode <mode>instead of the deleted script.Work plan item P2 / 12.
Note: this touches
[project.scripts]inpyproject.toml; #5 touches[project] dependencies. Different hunks, so whichever merges second should rebase cleanly.Scientific impact
None. Entry-point metadata and documentation only;
cli.mainand all analysis modules are unchanged.Checklist
ruff check .passespytestpasses locallyLint/test boxes left unchecked because this branch was pushed without a local run — CI on this PR is the first execution.