Remove numpy np.random.RandomState usage and deprecate random_state parameter
#763
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.
This PR upgrades
smtfrom legacynp.random.RandomStateto new random generatornp.random.Generator.Breaking change: Passing a
np.random.RandomStatedoes not work anymore. The following classes are impacted:LHS,Random,DesignSpaceand all kriging-based surrogate models via"random_state"option.If a
random_stateparameter was used with an integer it still works but is deprecated, the newseedparameter is added to handle passing an integer or anp.random.Generator. Therandom_statewill be removed in future releases, useseedinstead.Breaking change:
EGOandMixedIntegerapplications were directly upgraded, theirrandom_stateoption was replaced by aseedoption.Note:
smtnow requirespyDOE3>= 1.5.0