Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

RIFT PESummary ASIMOV adapter

ASIMOV 0.7+ postprocessing adapter for producing single-analysis and combined PESummary pages from RIFT results.

The adapter consumes the versioned rift-assets/v1 contract published by the RIFT ASIMOV plugin. It intentionally lives outside RIFT so PESummary CLI and metadata changes can be tested and released independently.

Development starts on reviewable feature branches. See the repository's draft pull requests for the first implementation and compatibility matrix.

Install

Install this package in the same environment as ASIMOV and PESummary:

python -m pip install rift-pesummary-asimov-adapter

ASIMOV discovers the rift-pesummary pipeline through its standard asimov.pipelines entry-point group. RIFT itself remains responsible for the inference job and publishes a versioned rift-assets/v1 dictionary. This adapter consumes that dictionary and owns the mutable summarypages command.

Use

Apply examples/single-rift-pesummary.yaml after changing its needs entry to the name of one completed RIFT analysis. For one page comparing every RIFT analysis on an event, apply examples/combined-rift-pesummary.yaml. These are separate analysis blueprints: neither changes the RIFT inference workflow.

asimov apply -f examples/combined-rift-pesummary.yaml -e EVENT
asimov manage build --event EVENT --dry-run

The generated command aligns every sample, configuration, approximant, low and reference frequency, PSD, and calibration envelope. Detector assets use PESummary's per-label arguments, which avoids incorrectly sharing one RIFT analysis's files across a combined page.

When a RIFT run publishes both samples_raw and samples_calmarg, select both as independently labelled PESummary analyses with:

postprocessing:
  pesummary:
    sample variants: all

The accepted values are preferred (the backward-compatible default), standard, calmarg, all, or a list of those values. Missing variants are skipped for all and rejected when explicitly requested alone.

RIFT also publishes its marginalized-likelihood grid as lnL_marg. PESummary 1.6 has no CLI input for the RIFT all.net format, so the adapter does not pass it as posterior samples or weights. It can instead preserve and publish an unaltered copy alongside the postprocessing job:

postprocessing:
  pesummary:
    capture all.net: true

The copy is exposed in collect_assets() and results() under likelihood. This keeps the data available for a future PESummary reader without coupling the stable adapter to an unsupported conversion.

Compatibility policy

The adapter currently targets ASIMOV 0.7 and PESummary 1.6 or newer. Both RIFT rift_O4c (0.0.17.13) and rift_O4d publish the same rift-assets/v1 contract. See compatibility.yaml and docs/coordination.md for the supported matrix and synchronized-change policy.

Metadata

Release files for rift-pesummary-asimov-adapter 0.1.0a2

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for rift-pesummary-asimov-adapter 0.1.0a2
File Size Uploaded
rift_pesummary_asimov_adapter-0.1.0a2.tar.gz 15.9 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for rift-pesummary-asimov-adapter 0.1.0a2
File Interpreter ABI Platform
rift_pesummary_asimov_adapter-0.1.0a2-py3-none-any.whl Python 3 none any Details

Total release size: 27.6 kB

Release files / rift_pesummary_asimov_adapter-0.1.0a2.tar.gz

Download URL rift_pesummary_asimov_adapter-0.1.0a2.tar.gz
Size 15.9 kB
Tags Source
SHA-256 checksum
How to use checksums
b70ab3485b9bd43ecfbf7b1e5348cfadcbcafdfff53afaf9a2f60645bdbf83cd
BLAKE2b-256 checksum
How to use checksums
c45427d78b7c8638faa5c0841971c5f07aeea1f9164bcd5071da69a6dc3d9d6b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Release files / rift_pesummary_asimov_adapter-0.1.0a2-py3-none-any.whl

Download URL rift_pesummary_asimov_adapter-0.1.0a2-py3-none-any.whl
Size 11.7 kB
Tags Python 3
SHA-256 checksum
How to use checksums
b7187cc655903768c9f683aeb18fd2b8b5961f9b3e8d973f7fbe543131dab00c
BLAKE2b-256 checksum
How to use checksums
ac456a89258a5aabcd4e1e1cf31543625fd9c009f2c8c0a2fb81b92cf9547019
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 17, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.0a2 This release

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page