matplotlib-users Mailing List for matplotlib (Page 6)

Some output using the different settings in the functions I just sent. As you can see the only problem are greek letters and some math symbols. It may be possible to improve this situation using xetex (http://matplotlib.org/users/pgf.html), but I did not try this out yet.
Am 03.05.2013 um 17:38 schrieb Felix Patzelt <fe...@ne...>:
> H, I'm using sfmath, too. I actually wrote a helper function to switch fonts. The preambles are the result of long-term trial and error. Normally, my preambles include some more custom commands which I left out here because they would be distracting. I always wondered why matplotlib doesn't do this kind of font switching out of the box.
> 
> def setfont(font=font_default,unicode=True):
> r"""
> Set Matplotlibs rcParams to use LaTeX for font rendering.
> Revert all changes by calling rcdefault() from matplotlib.
> 
> Parameters:
> -----------
> font: string
> "Helvetica"
> "Times"
> "Computer Modern"
> 
> usetex: Boolean
> Use unicode. Default: False. 
> """
> 
> # Use TeX for all figure text!
> plt.rc('text', usetex=True)
> 
> font = font.lower().replace(" ","")
> if font == 'times':
> # Times
> font = {'family':'serif', 'serif':['Times']}
> preamble = r"""
> \usepackage{color}
> \usepackage{mathptmx}
> """
> elif font == 'helvetica':
> # Helvetica
> # set serif, too. Otherwise setting to times and then
> # Helvetica causes an error.
> font = {'family':'sans-serif','sans-serif':['Helvetica'],
> 'serif':['cm10']}
> preamble = r"""
> \usepackage{color}
> \usepackage[tx]{sfmath}
> \usepackage{helvet}
> """
> else:
> # Computer modern serif
> font = {'family':'serif', 'serif':['cm10']}
> preamble = r"""
> \usepackage{color}
> """
> 
> if unicode:
> # Unicode for Tex
> #preamble = r"""\usepackage[utf8]{inputenc}""" + preamble
> # inputenc should be set automatically
> plt.rcParams['text.latex.unicode']=True
> 
> #print font, preamble
> plt.rc('font',**font)
> plt.rcParams['text.latex.preamble'] = preamble
> 
> 
> Am 03.05.2013 um 16:08 schrieb Juergen Hasch <py...@el...>:
> 
>>> 
>>> The solution I use when I want all sans-serif out of TeX is to use the cmbright package, which can be turned on by adding:
>>> 
>>> rc('text.latex', preamble=r'\usepackage{cmbright}')
>>> 
>>> That may require installing the cmbright LaTeX package if you don't already have it.
>> 
>> I am using the sfmath package for this purpose.
>> 
>> There is a nice comparision of the different approaches to get sans-serif math fonts at the bottom of the sfmath page: 
>> http://dtrx.de/od/tex/sfmath.html
>> 
>> 
>> 
>> ------------------------------------------------------------------------------
>> Get 100% visibility into Java/.NET code with AppDynamics Lite
>> It's a free troubleshooting tool designed for production
>> Get down to code-level detail for bottlenecks, with <2% overhead.
>> Download for free and get started troubleshooting in minutes.
>> http://p.sf.net/sfu/appdyn_d2d_ap2
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 

On Fri, May 3, 2013 at 6:17 AM, Michael Droettboom <md...@st...> wrote:
> On 05/02/2013 03:16 PM, Paul Hobson wrote
>
> I now see that this was more of TeX issue than an MPL configuration
> issue. Your help prompted me to find this solution (similar to yours):
> mpl.rcParams['text.latex.preamble'] = [
> r'\usepackage{siunitx}', # i need upright \micro symbols, but you
> need...
> r'\sisetup{detect-all}', # ...this to force siunitx to actually
> use your fonts
> r'\usepackage{helvet}', # set the normal font here
> r'\usepackage{sansmath}', # load up the sansmath so that math ->
> helvet
> r'\sansmath'] # <- tricky! -- gotta actually tell tex to use!
>
>
> Wow. That's some serious TeX voodoo magic! Want to work that into an
> example that we could include in the docs?
>
> Cheers,
> Mike
>
Gladly. I'll try to find time to cook up PR building off of the existing
example over the weekend.
-paul

>
> The solution I use when I want all sans-serif out of TeX is to use the cmbright package, which can be turned on by adding:
>
> rc('text.latex', preamble=r'\usepackage{cmbright}')
>
> That may require installing the cmbright LaTeX package if you don't already have it.
I am using the sfmath package for this purpose.
There is a nice comparision of the different approaches to get sans-serif math fonts at the bottom of the sfmath page: 
http://dtrx.de/od/tex/sfmath.html

Mike,
On 03/05/2013 15:14, Michael Droettboom wrote:
> FWIW: Matplotlib uses the older buffer interface because that is what 
> the older version of wx used (as well as other GUI toolkits). It 
> would be nice to move to the new memoryview objects, but all of the 
> GUI frameworks will need to move in tandem...
agg.bufferNEW_rgba or something along those lines and then GUI 
frameworks could move when they want/can, or would that create to big of 
an overhead on MPL side.
Werner

On 05/02/2013 03:16 PM, Paul Hobson wrote:
>
> On Thu, May 2, 2013 at 11:19 AM, Michael Droettboom <md...@st... 
> <mailto:md...@st...>> wrote:
>
> I think the confusion here stems from the fact that you're mixing
> TeX and non-TeX font commands.
>
> This turns on TeX mode, so all of the text is rendered with an
> external TeX installation:
>
> rc('text', usetex=True)
>
> In this line, setting it to sans-serif will get passed along to
> TeX, but a specific ttf font name can not be used by TeX, so the
> second part (involving Helvetica) is ignored. And setting the
> default body text in TeX does not (by default) change the math
> font. This is (unfortunately standard TeX behavior).
>
> rc('font',**{'family':'sans-serif','sans-serif':['Helvetica']})
>
> This affects the font set used by matplotlib's internal mathtext
> renderer, and has no effect on TeX:
>
> rc('mathtext', fontset='stixsans')
>
> The solution I use when I want all sans-serif out of TeX is to use
> the cmbright package, which can be turned on by adding:
>
> rc('text.latex', preamble=r'\usepackage{cmbright}')
>
> That may require installing the cmbright LaTeX package if you
> don't already have it.
>
> I know all this stuff is confusing, but providing a flat interface
> over both the internal text rendering and the TeX rendering isn't
> really possible -- they have different views of the world -- and
> I'm actually not sure it's desirable. Though I wonder if we
> couldn't make it more obvious (somehow) when the user is mixing
> configuration that applies to the different contexts.
>
> Mike
>
>
> Mike,
>
> Thanks for the guidance. I know this stuff is complicated and the work 
> everyone has put into it to make it work is fantastic.
>
> I now see that this was more of TeX issue than an MPL configuration 
> issue. Your help prompted me to find this solution (similar to yours):
> mpl.rcParams['text.latex.preamble'] = [
> r'\usepackage{siunitx}', # i need upright \micro symbols, but 
> you need...
> r'\sisetup{detect-all}', # ...this to force siunitx to 
> actually use your fonts
> r'\usepackage{helvet}', # set the normal font here
> r'\usepackage{sansmath}', # load up the sansmath so that math 
> -> helvet
> r'\sansmath'] # <- tricky! -- gotta actually tell tex to use!
Wow. That's some serious TeX voodoo magic! Want to work that into an 
example that we could include in the docs?
Cheers,
Mike

FWIW: Matplotlib uses the older buffer interface because that is what 
the older version of wx used (as well as other GUI toolkits). It would 
be nice to move to the new memoryview objects, but all of the GUI 
frameworks will need to move in tandem...
Mike
On 04/27/2013 06:23 PM, Werner F. Bruhin wrote:
> Hi Michael,
>
> On 26/04/2013 14:40, Michael Droettboom wrote:
>> On 04/26/2013 02:57 AM, Werner F. Bruhin wrote:
>>> Hi,
>>>
>>> Anyone can provide some info on what "agg.buffer_rgba" returns and 
>>> maybe
>>> even some suggestion on how to resolve this issue in the wxagg backend.
>> It returns a Python buffer object on Python 2, though on Python 3 it is
>> a memoryview, since buffer was deprecated. Perhaps wx is also doing
>> something different depending on the version of Python.
> As of Phoenix 2.9.5.81-r73873 matplot works with Phoenix, here is 
> Robin Dunn's comment to the change he did on Phoenix with regards to 
> the buffer handling.
>
> Quote
>
> The new buffer APIs go as far back as 2.6, IIRC, and the memoryview 
> and bytearray object types are available in 2.7 in addition to 3.x and 
> that I what I'm using in Phoenix. I would have expected MPL to do so 
> also since numpy is an integral part of MPL and the new buffer 
> interface was basically designed for and by numpy...
>
> Anyway, while double checking all this I realized that it would not be 
> hard for me to accept old or new buffer objects for source buffers 
> (I'll still use memoryviews or bytearrays when on the producer side of 
> things) so try again after the next snapshot build. My unittests with 
> array.arrrays started working after the change so I expect that MPL's 
> rgba buffer should work too.
>
> EndQuote
>
> Enclosed is the patch for backend_wx.py and for embedding_in_wx5.py 
> which I used for testing, in the later I use wxversion.select to force 
> selection of a particular version - I think the distribution should 
> still just use ensureMinimal.
>
> FYI, documentation for wxPython Phoenix are here:
> http://wxpython.org/Phoenix/docs/html/index.html
>
> And snapshots can be found here:
> http://wxpython.org/Phoenix/snapshot-builds/
>
> I tested only on Python 2.7.2 on Windows 7.
>
> Werner
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Would you mind submitting this as a pull request?
Mike
On 04/27/2013 06:23 PM, Werner F. Bruhin wrote:
> Hi Michael,
>
> On 26/04/2013 14:40, Michael Droettboom wrote:
>> On 04/26/2013 02:57 AM, Werner F. Bruhin wrote:
>>> Hi,
>>>
>>> Anyone can provide some info on what "agg.buffer_rgba" returns and 
>>> maybe
>>> even some suggestion on how to resolve this issue in the wxagg backend.
>> It returns a Python buffer object on Python 2, though on Python 3 it is
>> a memoryview, since buffer was deprecated. Perhaps wx is also doing
>> something different depending on the version of Python.
> As of Phoenix 2.9.5.81-r73873 matplot works with Phoenix, here is 
> Robin Dunn's comment to the change he did on Phoenix with regards to 
> the buffer handling.
>
> Quote
>
> The new buffer APIs go as far back as 2.6, IIRC, and the memoryview 
> and bytearray object types are available in 2.7 in addition to 3.x and 
> that I what I'm using in Phoenix. I would have expected MPL to do so 
> also since numpy is an integral part of MPL and the new buffer 
> interface was basically designed for and by numpy...
>
> Anyway, while double checking all this I realized that it would not be 
> hard for me to accept old or new buffer objects for source buffers 
> (I'll still use memoryviews or bytearrays when on the producer side of 
> things) so try again after the next snapshot build. My unittests with 
> array.arrrays started working after the change so I expect that MPL's 
> rgba buffer should work too.
>
> EndQuote
>
> Enclosed is the patch for backend_wx.py and for embedding_in_wx5.py 
> which I used for testing, in the later I use wxversion.select to force 
> selection of a particular version - I think the distribution should 
> still just use ensureMinimal.
>
> FYI, documentation for wxPython Phoenix are here:
> http://wxpython.org/Phoenix/docs/html/index.html
>
> And snapshots can be found here:
> http://wxpython.org/Phoenix/snapshot-builds/
>
> I tested only on Python 2.7.2 on Windows 7.
>
> Werner
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Hi.
i am using ListedColormap with ScalarMappable, to map data ranges, without
using a norm. But i dont know if what i am doing is a good thing or not.
Here's the snippet:
----------------------------------------------------------------------
from matplotlib import pyplot as plt
from matplotlib import colors, cm
cl = ["#8080FF", #purple
 "#40C0FF", #blue
 "#00FFFF", #cyan
 "#00FF00", #green
 "#FFFF00", #yellow
 "#FF8000", #orange
 "#FF0000"] #red
cmap = colors.ListedColormap(cl)
data = np.array([np.arange(0, 5, 10, 15, 20, 25, 30, 35, 40, 45)])
sm = cm.ScalarMappable(cmap=cmap)
sm.set_clim(vmin=5, vmax=40) #7 colors, max-min=35
rgba = sm.to_rgba(data, bytes=True)
plt.imshow(rgba, interpolation="nearest")
plt.show()
----------------------------------------------------------------------
this produces output (first letters of color list):
"p, p, b, c, g, y, o, r, r, r"
as i intend.
5<=val<10 --> purple,
10<=val<15 --> blue
15<=val<20 -->cyan
....etc
BUT, when the color list is much longer than here, where each specific
color corresponds to some data range, somehow, sometimes the above doesn't
work as expected.
for example, 15<=val<20 --> should be cyan. but in lists with much more
color numbers, value=15 sometimes produces blue. by trial & error, i saw
only when an epsilon is added to 15, say 15.000001, data color becomes cyan.
i reckon this has something to do with color number. when the number of
colors in ListedColormap is not an integer power of 2 (8, 16, 32, 64..etc)
the normalization in set_clim divides 0-1 into sections, which are not
exactly representable in machine float, if the color number is, say, 12,
17, 20..etc. so this small differences in color-change-limits result this
behaviour. so adding one extra dummy color can solve this, as it completes
color number to 8 (2^3 colors).
is this the case or is my guess is completely wrong ?
secondly, i also would like to know the logic behind how matplotlib
corresponds/maps values in whole range like i use above, with colors in
color list. i digged the source but no success. say 4 colors in list and
set_clim(vmin=2, vmax=4).
this yields for values:
below 2 ->color1
2-(2.5) ->color1
2.5-(3) ->color2
3-(3.5) ->color3
3.5 and above ->color4. but how ?
thanks.
-- 
Yasin
"Bismillah, her hayrın başıdır."

I have been working on this problem for the last week and I have finally
started to understand how it should work:
1) Events and plt.show must be running all the time. Indeed, the latter is
designed to be set implemented at the end of the code. The events call
should be just before
2) To change the data on your figures you can use a key event. This post
illustrates the right way to do it and it includes a class for it
http://stackoverflow.com/questions/14347630/using-events-with-matplotlib-in-a-for-loop?rq=1
3) The problem with this structure is that your code must be fragmented in
different methods. You need to make sure to define your variables in the
main code so they can be imported across different methods (I am still
struggling with this... I will post an example code when I am done)
One additional question: When I try to run the cursor widget with the
spanselector widget the widgets glitches in a rather... painful way to the
eye way... Is there anyway to avoid this? I have been playing with the
cursor useblit widget but no luck
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/Widgets-How-to-disconnect-spanselector-once-selection-is-completed-tp40949p40989.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Thu, May 2, 2013 at 11:19 AM, Michael Droettboom <md...@st...> wrote:
> I think the confusion here stems from the fact that you're mixing TeX
> and non-TeX font commands.
>
> This turns on TeX mode, so all of the text is rendered with an external
> TeX installation:
>
> rc('text', usetex=True)
>
> In this line, setting it to sans-serif will get passed along to TeX, but
> a specific ttf font name can not be used by TeX, so the second part
> (involving Helvetica) is ignored. And setting the default body text in TeX
> does not (by default) change the math font. This is (unfortunately
> standard TeX behavior).
>
> rc('font',**{'family':'sans-serif','sans-serif':['Helvetica']})
>
> This affects the font set used by matplotlib's internal mathtext renderer,
> and has no effect on TeX:
>
> rc('mathtext', fontset='stixsans')
>
> The solution I use when I want all sans-serif out of TeX is to use the
> cmbright package, which can be turned on by adding:
>
> rc('text.latex', preamble=r'\usepackage{cmbright}')
>
> That may require installing the cmbright LaTeX package if you don't
> already have it.
>
> I know all this stuff is confusing, but providing a flat interface over
> both the internal text rendering and the TeX rendering isn't really
> possible -- they have different views of the world -- and I'm actually not
> sure it's desirable. Though I wonder if we couldn't make it more obvious
> (somehow) when the user is mixing configuration that applies to the
> different contexts.
>
> Mike
>
Mike,
Thanks for the guidance. I know this stuff is complicated and the work
everyone has put into it to make it work is fantastic.
I now see that this was more of TeX issue than an MPL configuration issue.
Your help prompted me to find this solution (similar to yours):
 mpl.rcParams['text.latex.preamble'] = [
 r'\usepackage{siunitx}', # i need upright \micro symbols, but you
need...
 r'\sisetup{detect-all}', # ...this to force siunitx to actually
use your fonts
 r'\usepackage{helvet}', # set the normal font here
 r'\usepackage{sansmath}', # load up the sansmath so that math ->
helvet
 r'\sansmath'] # <- tricky! -- gotta actually tell tex to use!
Thanks again!
-paul

I think the confusion here stems from the fact that you're mixing TeX 
and non-TeX font commands.
This turns on TeX mode, so all of the text is rendered with an external 
TeX installation:
rc('text', usetex=True)
In this line, setting it to sans-serif will get passed along to TeX, but 
a specific ttf font name can not be used by TeX, so the second part 
(involving Helvetica) is ignored. And setting the default body text in 
TeX does not (by default) change the math font. This is (unfortunately 
standard TeX behavior).
rc('font',**{'family':'sans-serif','sans-serif':['Helvetica']})
This affects the font set used by matplotlib's internal mathtext 
renderer, and has no effect on TeX:
rc('mathtext', fontset='stixsans')
The solution I use when I want all sans-serif out of TeX is to use the 
cmbright package, which can be turned on by adding:
rc('text.latex', preamble=r'\usepackage{cmbright}')
That may require installing the cmbright LaTeX package if you don't 
already have it.
I know all this stuff is confusing, but providing a flat interface over 
both the internal text rendering and the TeX rendering isn't really 
possible -- they have different views of the world -- and I'm actually 
not sure it's desirable. Though I wonder if we couldn't make it more 
obvious (somehow) when the user is mixing configuration that applies to 
the different contexts.
Mike
On 05/02/2013 11:58 AM, Paul Hobson wrote:
> Hey folks,
>
> I'm having trouble getting a consistent sans-serif font in my figures:
> https://gist.github.com/phobson/5503195 (see attached output)
>
> This is pretty much the same issue as this Stack Overflow post:
> http://stackoverflow.com/questions/12322738/how-do-i-change-the-axis-tick-font-in-a-matplotlib-plot-when-rendering-using-lat
>
> But, the end result I'm looking for is to process the whole figure 
> through latex and have sans-serif fonts everywhere, even in math text.
>
> The accepted solution on SO is to manually set the font properties of 
> the ticks for the figure prior to saving.
>
> Is there a configuration-based work around for this? I'd like to avoid 
> having to pick through everywhere that I call fig.savefig and manually 
> set tick font properties if possible.
>
> Thanks,
> -Paul
>
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Sorry for the confusion. The prior attachment was generated with the
solution on SO. (Though you can still see the serif math fonts.)
Here's the correct output from the Gist I included (purely-configuration
based).
-Paul
On Thu, May 2, 2013 at 8:58 AM, Paul Hobson <pmh...@gm...> wrote:
> Hey folks,
>
> I'm having trouble getting a consistent sans-serif font in my figures:
> https://gist.github.com/phobson/5503195 (see attached output)
>
> This is pretty much the same issue as this Stack Overflow post:
>
> http://stackoverflow.com/questions/12322738/how-do-i-change-the-axis-tick-font-in-a-matplotlib-plot-when-rendering-using-lat
>
> But, the end result I'm looking for is to process the whole figure through
> latex and have sans-serif fonts everywhere, even in math text.
>
> The accepted solution on SO is to manually set the font properties of the
> ticks for the figure prior to saving.
>
> Is there a configuration-based work around for this? I'd like to avoid
> having to pick through everywhere that I call fig.savefig and manually set
> tick font properties if possible.
>
> Thanks,
> -Paul
>
>

Hey folks,
I'm having trouble getting a consistent sans-serif font in my figures:
https://gist.github.com/phobson/5503195 (see attached output)
This is pretty much the same issue as this Stack Overflow post:
http://stackoverflow.com/questions/12322738/how-do-i-change-the-axis-tick-font-in-a-matplotlib-plot-when-rendering-using-lat
But, the end result I'm looking for is to process the whole figure through
latex and have sans-serif fonts everywhere, even in math text.
The accepted solution on SO is to manually set the font properties of the
ticks for the figure prior to saving.
Is there a configuration-based work around for this? I'd like to avoid
having to pick through everywhere that I call fig.savefig and manually set
tick font properties if possible.
Thanks,
-Paul

The code below uses axisartist toolkit.
http://nbviewer.ipython.org/5467593
This is modified from 3rd example from the below example.
http://matplotlib.org/examples/axes_grid/demo_floating_axes.html
I hope this helps.
Regards,
-JJ
On Tue, Apr 23, 2013 at 11:17 PM, Marian Jakubik <mja...@ta...> wrote:
> Hi all,
>
> is there any possibility to show only first quadrant in hammer
> projection? If it is not implemented in matplotlib, have you any trick
> for doing this?
>
> Thanks in advance for your help.
>
> Best,
> Marian
>
>
> ------------------------------------------------------------------------------
> Try New Relic Now & We'll Send You this Cool Shirt
> New Relic is the only SaaS-based application performance monitoring service
> that delivers powerful full stack analytics. Optimize and monitor your
> browser, app, & servers with just a few lines of code. Try New Relic
> and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

You need to create a new handler. I guess the code below is close to what
you want. I hope this helps.
http://nbviewer.ipython.org/5495680
Regards,
-JJ
On Wed, May 1, 2013 at 5:24 AM, mgurling <mag...@gm...> wrote:
> I'm trying to make a legend handle that is half black and half hatched.
> I've
> tried ...
>
> ...
> rpos1 = ax.bar(ind, pos1, width, color='k', label='+1')
> rneg1 = ax.bar(ind, neg1, width, color='w', hatch='///', label='-1')
>
> rpos2 = ax.bar(ind, pos2, width, color='w', label='+2')
> rneg2 = ax.bar(ind, neg2, width, color='w', label='-2')
>
> handles, labels = ax.get_legend_handles_labels()
> ax.legend( ((handles[0], handles[1]), handles[2]) , ('one', 'two') )
> ...
>
> The first handles--handles[0] and handles[1]--are combined but not side by
> side: the hatched rectangle is placed over the top of the black rectangle
> so
> the handle looks like it is just hatched. How might I create this mixed
> handle?
>
>
>
> --
> View this message in context:
> http://matplotlib.1069221.n5.nabble.com/black-and-hatched-legend-handle-tp40979.html
> Sent from the matplotlib - users mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Dear all,
When I start to make the plots for my first publication of my PhD study. I
use the plot command
to make some line and scatter plots, then I find myself want to have some
scatter plot as well,
and I want to change some of the scatter points colors. And probably later
I want bar plots....
So I find it taking me 3 hours to change the underlying code just to change
a plot type of the same
data. Don't know others have the same issue....
Then I started to write some small functions with the idea of like "data
centered plotting", it wraps
some of the maplotlib functions in a STUPID, SIMPLE yet flexible way. The
idea is not for large scale
production purpose, but for a "quick-look" of the data with some
"intermediate-stage of easthetic",
for a rather small amount of data.
So I ended with a small library of which I called Pdata. (short for
PlotData, which means data centered
plotting functions). I don't know if others have similar demand. However I
put it here to just have some
comments from you.
You're invited to spend 5mins on this small ipython notebook:
https://gist.github.com/ChaoYue/5494557
use http://nbviewer.ipython.org/ to check it.
cheers,
Chao
-- 
***********************************************************************************
Chao YUE
Laboratoire des Sciences du Climat et de l'Environnement (LSCE-IPSL)
UMR 1572 CEA-CNRS-UVSQ
Batiment 712 - Pe 119
91191 GIF Sur YVETTE Cedex
Tel: (33) 01 69 08 29 02; Fax:01.69.08.77.16
************************************************************************************