-
Notifications
You must be signed in to change notification settings - Fork 8
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
Jupyter notebook plotting issue with numpy 2.1.1 #218
Comments
I will look into this. |
Did anything else downgrade as well? Or just numpy? Could you provide the package list with versions for the downgraded environment? |
similar to tataratat/splinepy#451 |
I have looked into it a bit. This seems to be a problem with how vedo converts points and lines to k3d. If I change in Specifically the lines 316 onward to: aves = float(ia.average_size() * iap.GetPointSize() / 200)
kobj = k3d.points(
ia.vertices.astype(float),
color=_rgb2int(iap.GetColor()),
colors=kcols,
opacity=iap.GetOpacity(),
shader=settings.k3d_point_shader,
point_size=aves,
name=name,
) and lines from 243 onward aves = float(ia.diagonal_size() * iap.GetLineWidth() / 100)
kobj = k3d.line(
pts.astype(float),
color=_rgb2int(iap.GetColor()),
opacity=iap.GetOpacity(),
shader=settings.k3d_line_shader,
width=aves,
name=name,
) it works again for me. I am not sure why this is just changing its functionality now and not before. Why |
I opened an issue for this on vedo for this marcomusy/vedo#1197 (comment). |
Vedo has pushed the fix I have suggested. I will not make a determination on what vedo version has to be used yet since they have not had a new release. But if you have this issue it should be fixed if you install vedo from source. |
When running the example notebook on a fresh installation, I get a trait error
TraitError: The 'width' trait of a Line instance expected a float or a dict, not the float32 np.float32(0.054083023)."
Downgrading numpy to version 1.26.4 solved the issue for me.
Relevant conda environment specs:
The text was updated successfully, but these errors were encountered: