Repository navigation
Multiple improvments and fixes for path and simulation modules. - #1378
Merged
chrisjonesBSU merged 31 commits intoOct 20, 2026
Merged
Conversation
… set default box values. All of this information is available by RandomWalkState, add a test to make sure wrapping is being done outside the main RW loop (i.e., in points.py second point)
…o fix-pbcs-points
… prevents over-sampling box corners/diagonals
…y handle table potentials in HOOMD's simulation class
…age convention ensures bonds crossing the periodic boundaries are correctly oriented
… one-at-a-time. Roughly 2x speed up when backmapping large compounds
Resolve conflicts in TargetCoordinate.__call__ by combining the adaptive capture-radius weight with the PBC-aware distance calculation. The capture-radius ramp now also uses minimum-image distance when attached to a walk, consistent with WithinCoordinate. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…nt, rather than always using the default, which could allow for paricle overlaps when angles and/or dihedrals aren't in the path FF
…nge info to warning when no GPU is found in HoomdSimulation and run_on_gpu is True
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1378 +/- ##
===========================================
+ Coverage 82.39% 82.67% +0.28%
===========================================
Files 72 72
Lines 8604 8747 +143
===========================================
+ Hits 7089 7232 +143
Misses 1515 1515 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
added 2 commits
October 19, 2026 11:28
…for subsequent simulation calls
…ild into fix-azimuthal-sampling
added 3 commits
October 19, 2026 11:51
…more robust. Before, scaled forces were cached, so recreating a Simulation class instance on the same compound would carry the last-used ForcesHandler scaling. This perserves the original params throughout, including the cached forces
…dler scaling behavior
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
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.
PR Summary:
Fix azimuthal sampling in random walks, plus PBC, backmapping and HOOMD updates
This started as a fix for biased azimuthal sampling in
hard_sphere_random_walk. A few related fixes ended up on the branch along the way, so it's a bit of a grab bag.Random walks
link-linearwalk.get_second_pointwraps its candidates into the box.points.pynow getpbcandbox_lengths.TargetCoordinatetakes an optionalcapture_radius. Inside it, the bias weight ramps up to 1 as the walk gets close totermination_radius. That radius can come from aWithinCoordinateterminator, andcapture_radius="auto"uses 10x the bond length. If that isn't larger thantermination_radius, the walk raises an error before it starts and says to pass a float.include_compoundis used, biases now see the chain tip ascoordinates[-1]. Before, the second step saw a compound particle there instead. This also fixesTargetDirectionandAvoidDirection, which had the same bug on develop.choicesampler weights, skips zero-weight angles, and stays quiet below 0.5%.Backmapping
boxargument. For a Compound it defaults tosystem.box. Bonds across the boundary are oriented using the minimum image, so fragments point through the boundary instead of across the box.HoomdSimulation
box_updatedoesn't shift the system.nvtandbox_updateacceptkT=[start, finish]and ramp between the two values. A list or array that isn't exactly two values raises aValueError.ForcesHandlerscales tabulated angle and dihedral potentials. Before, they were dropped whenever a handler was used.speedup_by_moltagoption made accessible from mBuild simulation model. It is passed through to gmso.ForcesHandlerdocstring notes that scaling a table down, or the defaultscale_periodic=0, lets those beads overlap.printcalls are nowlogger.info. The GPU fallback message is alogger.warning.PR Checklist