-
Notifications
You must be signed in to change notification settings - Fork 7
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
Could Not Load Library: The specified module could not be found. #6
Comments
Thank you for reporting this issue. I'm happy to announce that it should soon work. I have a working update in https://github.com/computationalprivacy/CorrectMatch.jl/tree/upgrading-deps that now passes all the tests on Julia 1.7 and macOS (https://github.com/computationalprivacy/CorrectMatch.jl/runs/7675628441) |
Hi @abesolberg, would you be able to test with the new release? This should be fixed now. |
Thanks for looking into this, @cynddl. I am no longer getting the error message, but the individual_uniqueness function is only outputting 0.0. I'm on Windows 10. |
Could this be the normal output to expect for your datasets? The tests pass as usual for |
@cynddl I don't believe so. It's outputting zero for the readme example, and for a number of other datasets I've tested it with. |
We're getting there, I just pushed a new version on the master branch. :) Seems like it now works on some architectures and not others: https://github.com/computationalprivacy/CorrectMatch.jl/actions/runs/2805373612 |
That worked! Thank you so much for sorting this out. Really appreciate it. Thanks again. |
Hi @cynddl, sorry to reopen this, but it looks like the new functions are still a little funky. I have been exploring further using the example script provided in the examples/demonstration-notebook.ipynb folder. Version 1.1 of CorrectMatch appears to be overestimating the individual_uniqueness of the non-unique individual.
I'll add, I'm not 100% sure if I'm doing the shift correctly. Julia syntax appears to have changed a bit since the example was written, so I had to add |
Thanks for the report @abesolberg! I'll try to have a look soon. |
Hello @cynddl and @abesolberg . Trying to get this to run myself. I'm encountering the same behavior mentioned above. Overestimating the individual_uniqueness of the unique individuals. Thanks in advance :) |
Hi @NikolaiKorti, thanks for your message. Could you please share a small reproducible code example for me to check and understand what you were expected from individual_uniqueness(·)? |
Hey. Thanks for the quick reply @cynddl . I've been trying multiple things. First of all re creating the notebook.
The individual_uniqueness for [1,1,1] it outputs is 0.99, which seems incorrect. Should be a very ununique individual. Using julia version 1.6.7 |
Another little note:
I tried the same using julia version 1.7.0 resulting in the same behavior. |
You will get the result you expect using:
Without setting exact_marginal, the code tries to fit whatever distribution works best for each marginal, which is due to fail on such a small dataset. |
Thanks for the quick replay again @cynddl . For the example this worked indeed. I needed to make some adjustments to the code to be able to run it at all. This is what I execute translated to a file:
And this is the output I get:
In your notebook the unlikely individual at the bottom receives a uniqueness score of I tried setting exact_marginal=false as well and tried a fit on data instead of marginals and using the not shifted indiv. Always comming up with a high score for the unlikely unique individual. |
Just leaving it here if anyone else runs into the same problem: |
I am unable to run the individual_uniqueness function, and am getting the error Could not load library "C:\Users\myuser.julia\packages\CorrectMatch\3WzMC\src..\deps\builds\mvndst" the specified module could not be found.
Yet
isfile("C:\Users\myuser\.julia\packages\CorrectMatch\3WzMC\src\..\deps\builds\mvndst")
is true, so the module should be there. I am using Julia Version 1.7.3 and gfortran (GCC) version 11.3.0.Thanks in advance
The text was updated successfully, but these errors were encountered: