Skip to content

Add ASIMOV 0.7 compatibility and PESummary assets - #176

Draft
oshaughnessy-junior wants to merge 2 commits into
oshaughn:rift_O4cfrom
oshaughnessy-junior:agent/asimov-070-compat-o4c
Draft

Add ASIMOV 0.7 compatibility and PESummary assets#176
oshaughnessy-junior wants to merge 2 commits into
oshaughn:rift_O4cfrom
oshaughnessy-junior:agent/asimov-070-compat-o4c

Conversation

@oshaughnessy-junior

Copy link
Copy Markdown

What changed

  • keep legacy automatic PESummary when ASIMOV still provides PESummaryPipeline;
  • defer to a separate postprocessing analysis on ASIMOV 0.7+;
  • publish the versioned rift-assets/v1 sample/config/PSD/calibration contract;
  • bridge the ASIMOV 0.5 get_psds() and ASIMOV 0.7 PSD attribute APIs;
  • preserve and extend safe combined-metafile bootstrap handling;
  • prefer canonical likelihood.minimum frequency while retaining the old ledger fallback.

Why

ASIMOV 0.7 removes the in-core PESummary class, which previously prevented the
RIFT entry point from importing. Separate PESummary jobs also need a complete,
stable set of RIFT assets.

Validation

On Caltech with Python 3.11:

  • ASIMOV 0.5.8: 22 focused compatibility/bootstrap tests passed;
  • ASIMOV 0.7.0: 22 focused compatibility/bootstrap tests passed;
  • ASIMOV 0.7.0 no-submit DAG-build probe passed and selected the RIFT plugin.

No scheduler or science DAG was submitted.

@oshaughnessy-junior
oshaughnessy-junior had a problem deploying to private-review-dispatch-rift-upstream August 17, 2026 15:03 — with GitHub Actions Failure
@oshaughnessy-junior

Copy link
Copy Markdown
Author

Critical audit follow-up is now at 3b79d2a. Fixed repository-relative PSD/calibration resolution, stopped advertising rift-assets/v1 for incomplete payloads, guarded dependency asset collection, and made stale bootstrap-grid reuse fail closed unless explicitly opted in. Added regression coverage for relative assets, dual standard/calmarg plus all.net publication, incomplete contracts, and bootstrap reuse. Caltech PR-checkout suite: 10/10. Adapter stable suite in the O4c environment: 18/18.

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.

1 participant