Skip to content

Record interpolated resumes before the first step; drop optmat tracker ids from warnings - #821

Open
jtravs wants to merge 2 commits into
mainfrom
fix/resume-record-152
Open

jtravs wants to merge 2 commits into
mainfrom
fix/resume-record-152

Conversation

@jtravs

@jtravs jtravs commented Nov 13, 2026

Copy link
Copy Markdown
Contributor
  • An interrupted resume="interpolated" leaves no interpolated_resumes record #152: interpolated_resumes is written before a resume="interpolated" session's first step, beside the run summary, so a stopped or failed continuation still records where it restarted. The SEP 42 execution-record route the issue preferred isn't available: SEP 42 was superseded by ADR-066, and the execution record is replaced by each session. Interface note: run_problem gains an interpolated_resume: bool = False keyword, the way to pass this fact to the session loop without touching the Start seam. The annotation stays outside the configuration hash. A session stopped before saving a plane and resumed from the same plane records that position twice; that is still accurate.
  • Warnings from optmat's Raman ranges reach users carrying optmat's internal tracker ids #166: optmat's internal tracker ids ((TC-n[, TC-m])) are stripped from the optmat warning texts solprop forwards (Raman responses, ionisation rates, material bridge), in both the warning and the run's record. Other parentheses are kept. If optmat changes its id form (Warnings reach solprop's users carrying register numbers optmat#32), the pattern will need revisiting.
  • Tests: a stopped interpolated resume records its position, and a later resume appends to it; synthetic optmat warnings for each forwarding site. All fail on main.

Closes #152
Closes #166

🤖 Generated with Claude Code

https://claude.ai/code/session_01XGENPwwkUUG9KSAwneHjgH

jtravs and others added 2 commits November 13, 2026 19:38
resume="interpolated" appended its position to the interpolated_resumes
annotation only after the run closed, on the success path, so a stopped
or failed continuation left planes beyond the position and no record of
it. The session loop now writes the annotation beside the run summary,
before the first step, when Simulation.run says the start is an
interpolated plane (run_problem's new interpolated_resume keyword).

The issue's other route, deriving the record from SEP 42's execution
record entry for forced resumes, is not available: SEP 42 was superseded
by ADR-066 and that entry never existed, and the execution record is
replaced by each execution, so it cannot hold the earlier positions.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XGENPwwkUUG9KSAwneHjgH
optmat 0.9.1 ends some ModelRangeWarning texts, the Raman responses'
density and temperature warnings among them, with ids of its internal
tracker such as "(TC-527, TC-688)". solprop forwarded the text unchanged
into MaterialRangeWarning and the run's material record, so users got a
reference they cannot look up.

_optmat.optmat_text removes a parenthesis that holds only such ids and
keeps the rest of the text. It is applied wherever optmat's warning text
is passed on: the Raman responses' _reemit, the ionisation rates'
warnings at resolution (which carry no ids in 0.9.1) and the material
bridge's range and absorption warnings.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XGENPwwkUUG9KSAwneHjgH
@jtravs
jtravs marked this pull request as ready for review November 13, 2026 21:32
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-13T21:33:51.390188Z 39a08aa Draft marked ready
🔒 Security Review ✅ Completed 2026-11-13T21:35:33.151076Z 39a08aa Draft marked ready
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@codecov

codecov Bot commented Nov 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant