New release to fix NumPy < 2 issues?

[danielS91]

Once again, thanks for sharing so much of your work.

I stumbled across this project via kiss-slam. Kiss SLAM does not force a specific NumPy version. However, it requires map_closures>=2.0.2, with 2.0.2 being so far the last release and actively forcing numpy < 2. So we always end up in an env with NumPy < 2, which breaks our current pipelines.

I noticed that this issue already was fixed along with an open3d bump in #78. However, there has been no official release since this PR.

Therefore, the question whether you can push a new release? This would avoid installing and building from master, i.e., something like that pip install git+https://github.com/PRBonn/MapClosures#subdirectory=python.

[saurabh1002]

Hi @danielS91, thanks for highlighting this issue.
I am working on handling all dependencies better, with a Dependabot tracker to enable automatic updates. I will soon make a PR, followed by a release, to fix this once and for all.

[kaiyi-zhang-code]

Hello, may I ask you a few questions? I couldn’t find map_closures.tools.gt_closures in the tools. I was able to run pipeline.py successfully, but since I don’t have gt_closures, I’m unable to compute accuracy and recall. Could you please tell me where map_closures.tools.gt_closures is located?
Also, I really like your paper — I think it is very innovative.