Re: [Matplotlib-users] colorbar.Colorbar ticking

2010-03-29 Thread Friedrich Romstedt
2010/3/29 Eric Firing efir...@hawaii.edu:
 It already has this.  You can pass in a custom locator or set of tick
 locations via the ticks kwarg, but if you don't, a locator is chosen
 automatically.  Except in special cases, this will be a MaxNLocator. See the
 ColorbarBase._ticker method.

Ah, thanks, It escaped my notice that there is a toplevel if
self.locator is None: statement ... ok.

 Ah, maybe what you mean is a text option to the ticks kwarg that would
 specify MaxNLocator without requiring one to instantiate a MaxNLocator? I
 don't think this makes sense for the case when boundaries are specified
 explicitly.

No, what I intended is exactly what you pointed out.

Btw, can you tell me what the *values* kwarg's semantic is?  I guess,
it shall be the center values of the values displayed, but then the
implementation for this in ColorbarBase._process_values() would be
broken.

Friedrich

P.S.: I assume you have be caught by the misconfiguration of the
list that the sender is used as the default recipient, so I post back
to the list?

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users


Re: [Matplotlib-users] colorbar.Colorbar ticking

2010-03-29 Thread Eric Firing
Friedrich Romstedt wrote:
 2010/3/29 Eric Firing efir...@hawaii.edu:
 It already has this.  You can pass in a custom locator or set of tick
 locations via the ticks kwarg, but if you don't, a locator is chosen
 automatically.  Except in special cases, this will be a MaxNLocator. See the
 ColorbarBase._ticker method.
 
 Ah, thanks, It escaped my notice that there is a toplevel if
 self.locator is None: statement ... ok.
 
 Ah, maybe what you mean is a text option to the ticks kwarg that would
 specify MaxNLocator without requiring one to instantiate a MaxNLocator? I
 don't think this makes sense for the case when boundaries are specified
 explicitly.
 
 No, what I intended is exactly what you pointed out.
 
 Btw, can you tell me what the *values* kwarg's semantic is?  I guess,
 it shall be the center values of the values displayed, but then the
 implementation for this in ColorbarBase._process_values() would be
 broken.

The ColorbarBase simply makes a strip of colored blocks, with their 
sizes and locations determined by the boundaries kwarg (together with 
the spacing kwarg) and their colors determined from the values kwarg 
via color mapping.  If either or both of these kwargs is None, the 
boundaries and/or values will be generated  in _process_values.  The use 
of the non-default values kwarg is illustrated by the special-case 
handling of colorbars for contouring in the Colorbar class.

Can you give a test case showing a problem with _process_values?

 
 Friedrich
 
 P.S.: I assume you have be caught by the misconfiguration of the
 list that the sender is used as the default recipient, so I post back
 to the list?

The mpl lists have been unusual (at least compared to lists for numpy, 
scipy, and cython) in this respect for years.  Usually I remember to 
reply to all, but you are right--this time I goofed.

Eric

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users


[Matplotlib-users] colorbar.Colorbar ticking

2010-03-28 Thread Friedrich Romstedt
I noticed that colorbar.Colorbar treats segmentation via *boundaries*
as compulsory, i.e., it thinks it must tick at the *boundaries* or
nowhere.  Wouldn't it be useful to have an kwarg which overrides this
and always uses ticker.MaxNLocator()?

Friedrich

--
Download Intel#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users