Replace RandomNumbers.jl dependency with direct Random123.jl usage #223
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.
Summary
This PR fixes the issue where Random123 is no longer part of RandomNumbers.jl by replacing the RandomNumbers.jl dependency with direct Random123.jl usage.
Problem
Random123 was previously accessed through RandomNumbers.jl, but is now a separate package. This was causing issues with bridge tests and other functionality that depends on Random123 generators.
Changes Made
Dependencies
Source Code Updates
import RandomNumbers: Xorshifts
andimport RandomNumbers
, kept onlyimport Random123
RandomNumbers.Random123.Threefry4x()
toRandom123.Threefry4x()
RandomNumbers.Random123.set_counter\!
toRandom123.set_counter\!
Test Updates
Xorshifts.Xoroshiro128Plus
withRandom123.Threefry4x
Testing
Benefits
This is a targeted fix that resolves the Random123/RandomNumbers dependency issue without changing the underlying mathematical behavior.