2010/3/29 Friedrich Romstedt <friedrichromst...@gmail.com>: > Note that the ticking is a bit weird, there is also a bug in > matplotlib I will report on right after this e-mail, whose bugfix you > will maybe want to apply to get ticking properly working. When you > have insane values for C.min() and C.max() anyway, I'm afraid you have > to retick manually with *ticks* to colorbar(). The ticker.MaxNLocator > is only used when not using the *boundaries* arg to colorbar(), > unfortunately. Otherwise it tries to create maximal many and less > than 11 ticks by using the lowest value and an appropriate step in > *boundaries*. I think the implementation of ticking is cumbersome and > never optimal.
You can get rid of this night mare by giving the kwarg "ticks = matplotlib.ticker.MaxNLocator()" to fig.colorbar(). Then the *boundaries* aren't used for ticking (but still for plotting). Friedrich ------------------------------------------------------------------------------ Download Intel® 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
