Skip to content
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

Pointcloud.translate() crashes programm if used with numpy >2.0 #6936

Open
3 tasks done
omagjhreblin opened this issue Aug 28, 2024 · 1 comment
Open
3 tasks done
Labels
bug Not a build issue, this is likely a bug.

Comments

@omagjhreblin
Copy link

Checklist

Describe the issue

I installed open3d via pip and i was installed with numpy 2.1.0. When running the code the translation will silenty crash my python programm. Downgrading to numpy <2.0 resolves the issuse.
If I use the latest dev-wheel it works fine, because the numpy version is <2.0.

Steps to reproduce the bug

import open3d as o3d
import numpy as np
import copy


def main():
    
    armadillo_data = o3d.data.ArmadilloMesh()
    pcd = o3d.io.read_triangle_mesh(
        armadillo_data.path).sample_points_poisson_disk(5000)


    trans_vec = np.array((150.0,0.0,0.0))
    # crashes here if numpy version >= 2.0
    translated_pcd = copy.deepcopy(pcd).translate(trans_vec)

    o3d.visualization.draw_geometries([pcd,translated_pcd],show_ui=True)



if __name__ == "__main__":
    main()

Error message

No response

Expected behavior

Ether bump version of numpy or check numpy version on install.
Also a error msg or an exception would be good for better debug

Open3D, Python and System information

- Operating system: Windows 10 64-bit
- Python version: Python 3.10.11 / output from `import sys; print(sys.version)`
- Open3D version: 0.18.0
- System architecture: x86
- Is this a remote workstation?:  no
- How did you install Open3D?: pip

Additional information

No response

@omagjhreblin omagjhreblin added the bug Not a build issue, this is likely a bug. label Aug 28, 2024
@timohl
Copy link
Contributor

timohl commented Aug 30, 2024

I think this got fixed in #6874 and will be released with 0.19.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Not a build issue, this is likely a bug.
2 participants