#12212: Colormap for implicit_plot3d and parametric_plot3d
-------------------------------------+-------------------------------------
       Reporter:  niles              |        Owner:  jason, was
           Type:  defect             |       Status:  needs_work
       Priority:  major              |    Milestone:  sage-6.5
      Component:  graphics           |   Resolution:
       Keywords:  colormap, plot     |    Merged in:
        Authors:  Joris              |    Reviewers:  Frédéric Chapoton,
  Vankerschaver, Frédéric Chapoton   |  Niles Johnson, Karl-Dieter Crisman,
Report Upstream:  N/A                |  Jonathan Gutow
         Branch:  u/chapoton/12212   |  Work issues:  update documentation
   Dependencies:                     |  and examples
                                     |       Commit:
                                     |  669d270b343da222aa68fcf40147c7cb6d0ad5c8
                                     |     Stopgaps:
-------------------------------------+-------------------------------------

Comment (by kcrisman):

 Sorry, the warning needs to be in `parametric_surface.pyx` too, and
 changed since jmol is sort of working.

 In that file, you say
 > Note that the coloring function should have values between 0 and 1. This
 value is passed to the chosen colormap.
 Is that maybe the problem we are having?  What happens with values outside
 that - is it done 'modulo 1' or something else?

 In implicit_plot I would put the examples of this in the example section,
 maybe after the `smooth=True` example.

 In parametric plot 3d the examples need to be dealt with anyway, and the
 indentation is not right when you view it.
 {{{
     EXAMPLES: We demonstrate each of the four ways to call this
     function.


     #. A space curve defined by three functions of 1 variable:

        ::

            sage: parametric_plot3d( (sin, cos, lambda u: u/10), (0, 20))
            Graphics3d Object

        Note above the lambda function, which creates a callable Python
        function that sends `u` to `u/10`.

     #. Next we draw the same plot as above, but using symbolic
        functions:

        ::

            sage: u = var('u')
            sage: parametric_plot3d( (sin(u), cos(u), u/10), (u, 0, 20))
            Graphics3d Object

     #. We draw a parametric surface using 3 Python functions (defined
        using lambda):

        ::

            sage: f = (lambda u,v: cos(u), lambda u,v: sin(u)+cos(v),
 lambda u,v: sin(v))
            sage: parametric_plot3d(f, (0, 2*pi), (-pi, pi))
            Graphics3d Object

 }}}
 up to here is fine, but
 {{{
     #. The surface, but with a mesh:

        ::

            sage: u, v = var('u,v')
            sage: parametric_plot3d((cos(u), sin(u) + cos(v), sin(v)), (u,
 0, 2*pi), (v, -pi, pi), mesh=True)
            Graphics3d Object
 }}}
 should just be an example later.  This one is the true "fourth way to call
 the function".
 {{{

     #. The same surface, but where the defining functions are
        symbolic:

        ::

            sage: u, v = var('u,v')
            sage: parametric_plot3d((cos(u), sin(u) + cos(v), sin(v)), (u,
 0, 2*pi), (v, -pi, pi))
            Graphics3d Object
 }}}
 Everything after that is indented too far, up until
 {{{
     We call the space curve function but with polynomials instead of
     symbolic variables.
 }}}
 including all the added examples.

--
Ticket URL: <http://trac.sagemath.org/ticket/12212#comment:143>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica, 
and MATLAB

-- 
You received this message because you are subscribed to the Google Groups 
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/d/optout.

Reply via email to