You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot see a way of controlling the seed on a class level. I suppose that the intention is to control the seed globally via the built-in or the numpy random modules since you use both of them in the package. Although, this is not documented in the docstrings or/and in the documentation.
Some things to consider:
Control the seed on class level by passing a seed number or a random state generator object. Document it in the docstrings.
Control the seed globally using a single entry point. Make a note in the documentation.
The text was updated successfully, but these errors were encountered:
I strongly agree with @chkoar 's 2nd point that a single point of entry would be better. E.g. adding a set_seed function to your moead_framework.tool subpackage:
This would allow you to easily switch random implementations later without bothering the user, for example if you switch everything to numpy using the new recommended np.random.Generator interface.
Related: openjournals/joss-reviews#2974
I cannot see a way of controlling the seed on a class level. I suppose that the intention is to control the seed globally via the built-in or the numpy random modules since you use both of them in the package. Although, this is not documented in the docstrings or/and in the documentation.
Some things to consider:
The text was updated successfully, but these errors were encountered: