Currently, we use a global seed (in fact, multiple, which might invalidate each other). This is problematic as computation happening outside the software might also set a global seed, which will then invalidate benchmark results). A solution instead is to define a random_state or pass around an RNG object.
Currently, we use a global seed (in fact, multiple, which might invalidate each other). This is problematic as computation happening outside the software might also set a global seed, which will then invalidate benchmark results). A solution instead is to define a random_state or pass around an RNG object.
see e.g. https://docs.astral.sh/ruff/rules/numpy-legacy-random/
This is not a pressing issue; the current performance metric aligns with the third decimal (as far as I am aware and can test)