make random state argument handling more consistent - #166
Conversation
ilan-gold
left a comment
There was a problem hiding this comment.
How is this not a breaking change for reproducibility given that you're changing the default? If you didn't set the random seed by default now in each of these, you're setting it every time now to 0. I think handling random state this way is a separate issue
d4e91a1 to
e06e875
Compare
|
We already weren't reproducible before, unless someone set their global random seed at the very beginning of the analysis, which very few people do. I would think this improves reproducibility. But I guess we can defer that change to muon 0.2 or something, with an explicit warning in the release notes. |
|
Up to you! If the goal is to just "fix the issue" I think checking |
e06e875 to
c4cd19a
Compare
c4cd19a to
6ef77e0
Compare
|
Maybe worth fully adhering to https://scientific-python.org/specs/spec-0007/ while you are at it? |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #166 +/- ##
=======================================
Coverage 26.27% 26.27%
=======================================
Files 16 16
Lines 2299 2299
=======================================
Hits 604 604
Misses 1695 1695
🚀 New features to boost your workflow:
|
yeah, that was my thought as well. |
|
@grst turns out we can't adhere to SPEC007 yet: muon itself does not do any random sampling, the |
|
I see, thanks for investigating! |
Uh oh!
There was an error while loading. Please reload this page.