New version: AdvancedHMC v0.8.4#155178
Merged
JuliaTagBot merged 1 commit intoMay 11, 2026
Merged
Conversation
Contributor
JuliaRegistrator
commented
May 11, 2026
JuliaRegistrator
commented
- Registering package: AdvancedHMC
- Repository: https://github.com/TuringLang/AdvancedHMC.jl
- Created by: @sunxd3
- Version: v0.8.4
- Commit: 20da2e8493e335d4ccc61e455be22ca10d1b09ed
- Reviewed by: @sunxd3
- Reference: TuringLang/AdvancedHMC.jl@20da2e8#commitcomment-184895241
- Description: Robust, modular and efficient implementation of advanced Hamiltonian Monte Carlo algorithms
UUID: 0bf59076-c3b1-5ca4-86bd-e02cd72cde3d Repo: https://github.com/TuringLang/AdvancedHMC.jl.git Tree: b75e434bd1e3e537586f3f70510dec8c70ce27ad Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
JuliaRegistrator
referenced
this pull request
in TuringLang/AdvancedHMC.jl
May 11, 2026
* Replace OrdinaryDiffEq weakdep with OrdinaryDiffEqSymplecticRK The DiffEqIntegrator extension only ever used the symplectic solvers (VerletLeapfrog and friends) plus the standard `init`/`step!`/ `DynamicalODEProblem` interface. None of that requires the full OrdinaryDiffEq meta-package; everything lives in or is re-exported by OrdinaryDiffEqSymplecticRK. Switching the weakdep from OrdinaryDiffEq → OrdinaryDiffEqSymplecticRK: - Drops the heavy meta-package: users no longer pull in BDF, Rosenbrock, Tsit5, Verner, Default, OrdinaryDiffEqCore, NonlinearSolve, LinearSolve, etc. just to use a leapfrog integrator inside HMC. - Makes the dependency graph honest about what the extension actually uses (symplectic RK methods only). - Sidesteps the OrdinaryDiffEq v6 ↔ v7 compat ratchet entirely: OrdinaryDiffEqSymplecticRK v1 (works against OrdinaryDiffEq v6) and v2 (works against v7) both expose the same surface, so compat is just `"1, 2"`. - Aligns with the v7 ecosystem story: in v7 `VerletLeapfrog` no longer re-exports out of OrdinaryDiffEq itself (it lives in the symplectic sublib), so depending on the sublib directly is the forward-compatible shape. Renames: - weakdep `OrdinaryDiffEq` → `OrdinaryDiffEqSymplecticRK` - extension module `AdvancedHMCOrdinaryDiffEqExt` → `AdvancedHMCOrdinaryDiffEqSymplecticRKExt` - extension file matched Updates `test/runtests.jl`, `test/integrator.jl`, the `register_error_hint` message, and the inline source comment in `src/integrator.jl` to refer to the new package name. Verified locally on Julia 1.10: - AHMC_TEST_GROUP=AdvancedHMC: 5052 tests, exit 0, no errors - Integrator subtests: 35/35 pass - Numerical equivalence: DiffEqIntegrator(VerletLeapfrog()) matches native Leapfrog bit-for-bit over 1000 steps; Hamiltonian drift ~1.7e-5 over the same trajectory. Unblocks downstream Turing v0.45 + SciML stack composition (e.g. SciMLExpectations.jl docs). Co-Authored-By: Chris Rackauckas <accounts@chrisrackauckas.com> * Apply suggestions from code review Co-authored-by: Bagaev Dmitry <bvdmitri@gmail.com> * Remove stale OrdinaryDiffEq compat entry The rename to OrdinaryDiffEqSymplecticRK left an `OrdinaryDiffEq = "6, 7"` line in [compat] without a matching deps/weakdeps/extras entry, which Pkg rejects (`Compat 'OrdinaryDiffEq' not listed`). --------- Co-authored-by: ChrisRackauckas-Claude <accounts@chrisrackauckas.com> Co-authored-by: Xianda Sun <5433119+sunxd3@users.noreply.github.com> Co-authored-by: Bagaev Dmitry <bvdmitri@gmail.com> Co-authored-by: Xianda Sun <sunxdt@gmail.com>
JuliaRegistrator
temporarily deployed
to
stopwatch
GitHub Actions
Inactive
JuliaRegistrator
temporarily deployed
to
stopwatch
GitHub Actions
Inactive
JuliaRegistrator
temporarily deployed
to
stopwatch
GitHub Actions
Inactive
5 tasks
Contributor
|
Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human. 1. AutoMerge Guidelines are all met! ✅Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round (~20 minutes). 2. To pause or stop registrationIf you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text Tip: You can edit blocking comments to add |
JuliaTagBot
deleted the
registrator-advancedhmc-0bf59076-v0.8.4-4aa4bd0e2e
branch
2 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.