Use BlackJAX 1.6 from PyPI

[thomasckng]

Summary

• use the released BlackJAX 1.6 package from PyPI
• remove the temporary Git source, nested-sampling dependency group, and feature guards
• simplify installation, CI, pre-commit, and sampler documentation

Why

Jim previously installed BlackJAX from upstream main because the nested-sampling APIs had not yet been released. BlackJAX 1.6 now provides those APIs through PyPI.

Impact

BlackJAX NS-AW and NSS now install with the normal jimgw dependency set; no separate install group or Git dependency is required.

Validation

• pre-commit run --all-files
• uv lock --check
• uv run --no-sync pytest tests/unit/samplers/test_registry.py tests/unit/samplers/blackjax/test_ns_aw_validation.py
• focused BlackJAX sampler suite: 88 passed

Summary by CodeRabbit

• Updates

  • Updated BlackJAX support to version 1.6 or later.
  • Simplified installation and environment setup by removing separate nested-sampling installation steps.
  • Standardised CI and development tooling around the regular dependency setup.

• Documentation

  • Streamlined sampler and CLI guidance.
  • Updated tutorial instructions for selecting nested samplers and obtaining log-evidence estimates.

• Maintenance

  • Simplified sampler loading and removed obsolete dependency checks and related tests.

[coderabbitai]

Warning

Review limit reached

@thomasckng, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 54 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: ff077880-26e7-4106-8166-48efc67ca6e9

📥 Commits

Reviewing files that changed from the base of the PR and between d4e526f and 5cc322f.

📒 Files selected for processing (1)

• docs/dev/blackjax_followups.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch agent/blackjax-pypi

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

🧹 Nitpick comments (1)

docs/dev/blackjax_followups.md (1)

17-18: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

Use British English spelling for consistency.

Other documentation files in the project use British English spelling (e.g., "normalised"). You may want to update these words to match for consistency.

♻️ Proposed fix

- - Delete the temporary `GW-JAX-Team/blackjax` fork once an organization admin
-   explicitly authorizes that irreversible action.
+ - Delete the temporary `GW-JAX-Team/blackjax` fork once an organisation admin
+   explicitly authorises that irreversible action.

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/dev/blackjax_followups.md` around lines 17 - 18, Update the wording in
the temporary fork deletion note to use British English spelling, changing
“authorizes” to “authorises” while preserving the rest of the sentence.

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Nitpick comments:
In `@docs/dev/blackjax_followups.md`:
- Around line 17-18: Update the wording in the temporary fork deletion note to
use British English spelling, changing “authorizes” to “authorises” while
preserving the rest of the sentence.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b713f16a-5a3b-4838-a947-80efd8816838

📥 Commits

Reviewing files that changed from the base of the PR and between d19b7af and d4e526f.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (15)

• .github/workflows/CI.yml
• .pre-commit-config.yaml
• docs/dev/blackjax_followups.md
• docs/guides/cli.md
• docs/guides/samplers.md
• docs/installation.md
• docs/tutorials/gw150914_cli.md
• pyproject.toml
• src/jimgw/samplers/__init__.py
• src/jimgw/samplers/blackjax/__init__.py
• src/jimgw/samplers/blackjax/_imports.py
• src/jimgw/samplers/blackjax/ns_aw.py
• src/jimgw/samplers/blackjax/nss.py
• tests/unit/samplers/blackjax/test_imports.py
• tests/unit/samplers/test_registry.py

💤 Files with no reviewable changes (6)

• src/jimgw/samplers/blackjax/ns_aw.py
• tests/unit/samplers/blackjax/test_imports.py
• src/jimgw/samplers/blackjax/_imports.py
• src/jimgw/samplers/blackjax/nss.py
• tests/unit/samplers/test_registry.py
• docs/installation.md