#12798: list_plot3d plots extraneous points at z=0 and doesn't take color or
rgbcolor as keywords
-----------------------------------------+----------------------------------
       Reporter:  ppurka                 |         Owner:  jason, was         
           Type:  defect                 |        Status:  needs_work         
       Priority:  major                  |     Milestone:  sage-5.1           
      Component:  graphics               |    Resolution:                     
       Keywords:  list_plot3d, sd40.5    |   Work issues:                     
Report Upstream:  N/A                    |     Reviewers:  Karl-Dieter Crisman
        Authors:  Punarbasu Purkayastha  |     Merged in:                     
   Dependencies:                         |      Stopgaps:                     
-----------------------------------------+----------------------------------
Changes (by kcrisman):

  * status:  needs_review => needs_work
  * reviewer:  => Karl-Dieter Crisman


Comment:

 > > I like this idea, but have a couple questions.
 > >
 > > * The way you have it set up currently has `color` etc. overriding
 `texture`.  Should we be explicit about that?  Is it even desirable?
 (Maybe it is, I just want to ask, as I am not sure.)
 >
 > Actually, `color` and the other keywords will never override `texture`.
 `color` will be used only when `texture` is not present, and `color` is
 present.

 Sorry for the inaccuracy, of course that is what I meant.

 > As it is setup, if `texture` is provided, then the others should be
 ignored. Actually, maybe we should do this explicitly and remove the other
 keywords if they are present. Something like
 > {{{
 > if texture == 'automatic':
 >     if 'color' in kwds:
 >         texture = kwds.pop('color')
 >         if 'rgbcolor' in kwds:
 >             del kwds['rgbcolor']
 >      ...
 > texture = rgbcolor(texture)
 > if 'color' in kwds:
 >     del kwds['color']
 > ...
 > }}}
 > Does that sound reasonable?

 Yes, as long as we document it.  We do similar things lots of other
 places.

 > > * Do you have any idea what the original default `0.0` was supposed to
 have done in the past (say, for an empty plot)?  I'm not suggesting you
 know, and I did read your very sensible post, but I'm just curious for any
 ideas you may have.
 >
 > I have no idea why this was done. Was it some bug in matplotlib earlier?
 Was it just an oversight? For an empty plot, I suppose you would not want
 there to be plot points at 0.0!

 Hmm, looking at your plots from the post, I think I know.  The idea was
 probably to have the `list_plot` cause a list to be plotted and then have
 the plot be zero elsewhere.  Then there is the weird interpolation thing
 going on.  Anyway, this makes things interpretable, though I'm not sure
 the original was really that useful, due to the output.  I wonder who has
 used this in the past...

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/12798#comment:5>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/sage-trac?hl=en.

Reply via email to