Skip to content

GWSignal options: compatibility with older DAGs and calibration workers - #442

Merged
oshaughn merged 1 commit into
rift_O4dfrom
claude/gwsignal-options-compat-o4d
Oct 12, 2026
Merged

oshaughn merged 1 commit into
rift_O4dfrom
claude/gwsignal-options-compat-o4d

Conversation

@oshaughnessy-junior

Copy link
Copy Markdown
Owner

Port of the O4c compatibility fixes from oshaughn#217 to the #438 code on rift_O4d.

Submit side and worker containers are upgraded at different times. Three combinations broke after #438:

  • DAGs built by older RIFT pass calibration "{antisymmetric_modes_hm: True, ...}" with unquoted keys, and the new parser raised. The legacy parser is restored and now reads values as literals.
  • Workers built before Forward generic GWSignal options through production argument paths #438 read lmax_nyquist only from --use-gwsignal-lmax-nyquist. pseudo_pipe emits that flag again; the dictionary value wins, as in ILE.
  • With both gwsignal arguments and arguments in a blueprint, gwsignal arguments wins again.

Tests

  • New tests for each change fail on the rift_O4d tip.
  • 202 passed in the five GWSignal option files (ldas-grid, IGWN python).
  • O4c end-to-end check against the production container: ~/LVK/IR1/code_validation/o4c-gwsignal-options-pr217-20261011/ on CIT.

🤖 Generated with Claude Code

Port of the O4c review fixes to #438 (oshaughn#217).

- calibration_reweighting: parse the unquoted-key dictionary that DAGs
  built by older RIFT deliver ("{antisymmetric_modes_hm: True, ...}");
  #438 raised ValueError there. Values are read as literals.
- pseudo_pipe: when the GWSignal dictionary carries lmax_nyquist, also
  emit --use-gwsignal-lmax-nyquist for calibration. Workers older than
  gwsignal_extra_kwargs read only that flag.
- rift.ini: 'gwsignal arguments' wins over 'arguments' when both are
  given, as before #438.
- Tests for each; they fail on the rift_O4d tip.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Independent automated review completed at the recorded exact commit. Detailed findings were withheld from public output by the private-context egress policy and require private human declassification.

@oshaughn
oshaughn merged commit fc532d0 into rift_O4d Oct 12, 2026
36 checks passed
@oshaughn
oshaughn deployed to private-review-dispatch-rift October 12, 2026 05:10 — with GitHub Actions Active

This branch was successfully deployed

1 active deployment
private-review-dispatch-rift — c3069a6e Deployed Oct 12, 2026 by oshaughn via Dispatch exact RIFT PR generation #1732
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.

2 participants