Open wingenium-nagesh opened 5 months ago
@wingenium-nagesh Thanks for catching this! If you would like to implement the change yourself, you can fork the repo, make the change on your fork and then open a PR. If you need help with this, let me know.
I got the same error, but luckily I created another venv using Python 3.12.2, numpy 1.26.4 and plotly 5.21.0 and the error disappeared. The original venv (where I got the error) was Python 3.11.6, numpy 1.26.4 and plotly 5.20.0. Maybe this can help. Btw I used the same version of kmapper 2.0.1 in both cases
@wingenium-nagesh Thanks for catching this! If you would like to implement the change yourself, you can fork the repo, make the change on your fork and then open a PR. If you need help with this, let me know.
Several people have already submitted this PR.
@blue-j @catanzaromj : apologies for the delay in responding. I will raise the PR shortly.
you are kind to respond. the PRs are there to approve already. do you have write access? - J
@wingenium-nagesh @blue-j Thank you both for the PRs. The build and deploy process for kepler-mapper is deprecated (notice the tests are only checking with python 3.6 - 3.8 here--and python 3.6 is EOL with no runners available). Give me a week to update the build and release process, and then we can get one of your solutions merged.
@catanzaromj @blue-j - thanks. I understand. I've raised the PR [https://github.com/Wingenium/kepler-mapper/tree/bugfix/issue-252-np-asscalar-error]. Thanks!
Describe the bug During execution of the mapper.visualize() function, it errors out in Visuals.py (line 573 - np.asscalar(object) "Numpy does not support attribute asscalar".
To Reproduce Steps to reproduce the behavior:
mapper.visualize( graph, path_html="breast-cancer.html", title="Wisconsin Breast Cancer Dataset", custom_tooltips=y, )
Expected behavior The expectation is that the visualize function should create a visualization map and stores it as an html file with the given filename
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information): Not applicable
Additional context I believe the issue happens because of a bug in the code in Visuals.py on line 573. The code (between lines 569-573) should be replaced as follows: