You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It turns out that our 3D plotting infrastructures has some nice, but undocumented features :
plot3d and friends accept float("NaN") values as value of a plotted function, and leave the corresponding face(s) unplotted : this gives a rectangular hole un the surface ;
the same functions accept a2-element list (or tuple ?) [<point function>, <colormap>]as a value for the color keyword argument ; this allows to compute a color value as a function of the point.
As far as I know, this latter point is documented only for parametric surfaces ; the first one is not documented at all.
The point of this ticket is to document these abilities, thus (hopefully) avoiding to lose them in any future upgrade (somewhat needed...) of our 3D infrastructure, and allowing to write new utilities explicitly using them.
It turns out that our 3D plotting infrastructures has some nice, but undocumented features :
plot3d
and friends acceptfloat("NaN")
values as value of a plotted function, and leave the corresponding face(s) unplotted : this gives a rectangular hole un the surface ;the same functions accept a2-element list (or tuple ?)
[<point function>, <colormap>]
as a value for thecolor
keyword argument ; this allows to compute a color value as a function of the point.As far as I know, this latter point is documented only for parametric surfaces ; the first one is not documented at all.
The point of this ticket is to document these abilities, thus (hopefully) avoiding to lose them in any future upgrade (somewhat needed...) of our 3D infrastructure, and allowing to write new utilities explicitly using them.
Depends on #23696
CC: @egourgoulhon
Component: graphics
Issue created by migration from https://trac.sagemath.org/ticket/24331
The text was updated successfully, but these errors were encountered: