-
Notifications
You must be signed in to change notification settings - Fork 228
Unconsistent behaviour of SDML when ussing skggm with fixed seed. #272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I just realized that we had noticed this when refurbishing SDML. See the following link and in particular the last post by jasonlaska: It seems they have not made a new release since then, which is why our doc suggests to install a particular developer version. Doing this should fix this problem. @grudloff can you try and confirm? |
Installed the indicated version and the behavior turns out to be the expected. Maybe the following code could be added to the documentation for ease of installing that version: |
Sure, it could be added in the installation-and-setup part of the doc, feel free to open a PR for this |
Description
I was using SDML_Supervised() for a subsequent 2D visualization with UMAP (Similar to t-sne) and got large differences in the results on every fit instance while using the same data. Fixing the seed doesn't make a difference. I tracked down the problem to the call of quic() done when skggm is installed, reviewing their code I found there is a fixed seed but anyway the results from that function vary in every call.
note: I am using the latest version from Skggm, will try to reproduce later with the version indicated in the documentation.
Steps/Code to Reproduce
Expected Results
The two instances of SDML fit should have the same result, then the printed difference should be zero.
Actual Results
Large numbers in the order of 100 to 300.
Versions
Linux-5.0.0-37-generic-x86_64-with-Ubuntu-18.04-bionic
Python 3.6.9 (default, Nov 7 2019, 10:44:02)
[GCC 8.3.0]
NumPy 1.18.1
SciPy 1.4.1
Scikit-Learn 0.22.1
Metric-Learn 0.5.0
Skggm 0.2.8
The text was updated successfully, but these errors were encountered: