matplotlib-users Mailing List for matplotlib

Am 28.02.2013 um 14:31 schrieb Pierre Haessig:
> Hi Thomas,
> 
> Le 27/02/2013 20:59, Thomas Sprinzing a écrit :
>> To sum it up: use the old 7-bit equivalent for the degree sign, not any fancydancy UTF-8 character that is commonly not included in ye olde style postscript standard font embedded into your laser printer waaaay back then in the last millenium... 
> Just out of curiosity, I looked at the list of ASCII printable
> characters
> (http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters) and
> didn't find the degree sign. However, I found it in the so-called "8
> bits extensions", which I believe is just the same as the Unicode U+00B0
confirmed by looking at
http://www.adobe.com/type/browser/info/charsets.html
Adobe western 2 has the same info.
Alt-0179 or U+00B0
So, best is to use the degree sign.
If you're not sure, what's present at rendering time, maybe try to force the generator to convert fonts to ps paths. 
But i donÄt know if matplotlib has tat optin at all...

Okay, fair enough.
But do you have any ideas, how to force the PS creator to use a different
font?
Say -> font Times-Bold
On Wed, Feb 27, 2013 at 12:59 PM, Thomas Sprinzing <
spr...@hd...> wrote:
> I'd say it's got nearly nothing to do with matplotlib.
>
> The question is: will the font be included in the .ps and in the .pdf?
>
> If not, which is most likely, it's upon the renderer to decide what to do
> if the requested glyph in the requested font is present or not in the
> system.
>
> pdf is more likely to have the fonts / glyphs used also embeded in the
> pdf. One reason for them to be bigger than .ps. Ps, on the other hand, most
> of the times relys on the renderer to have the exact same font, referenced
> by name, pre-loaded in the system. Go figure.
>
> To sum it up: use the old 7-bit equivalent for the degree sign, not any
> fancydancy UTF-8 character that is commonly not included in ye olde style
> postscript standard font embedded into your laser printer waaaay back then
> in the last millenium...
>
> Am 26.02.2013 um 21:26 schrieb Gökhan Sever:
>
> >
> >
> > On Tue, Feb 26, 2013 at 8:29 AM, Pierre Haessig <
> pie...@cr...> wrote:
> > Le 26/02/2013 14:38, Gökhan Sever a écrit :
> >>
> >> Could you test my outputs if they look fine on your side?
> >>
> >> http://atmos.uwyo.edu/~gsever/data/matplotlib/test.pdf
> >> http://atmos.uwyo.edu/~gsever/data/matplotlib/test.ps
> >>
> > Good idea !
> >
> > * your PDF file looks fine with Okular
> > * your PS indeed has the problem you describe (again Okular) :
> > - "°" (degree sign) is fine
> > - but "0" (zero superscript) is replaced by "?"
> >
> > In case it may explain the difference : I'm using mpl 1.1.1rc2 from
> Debian testing
> > and I have the following line in my matplotlibrc (is it relevant ???)
> >
> > font.sans-serif : DejaVu Sans, sans-serif
> >
> > Best,
> > Pierre
> >
> > My matplotlib is a git clone of a couple weeks old.
> >
> > There is this line in the PS file (opening via vim)
> >
> > %%BeginResource: font KDYSTE+NewCenturySchlbk-Roman
> >
> > don't know where it gets this.
> >
> > #font.serif : DejaVu Serif, Bitstream Vera Serif, New Century
> Schoolbook, Century Schoolbook L, Utopia, ITC Bookman, Bookman, Nimbus
> Roman No9 L, Times New Roman, Times, Palatino, Charter, serif
> > font.sans-serif : DejaVu Sans, Bitstream Vera Sans, Lucida Grande,
> Verdana, Geneva, Lucid, Arial, Helvetica, Avant Garde, sans-serif
> >
> > PS uses that even I choose to use fot.sans-serif.
> >
> > Dont see any font specification in the PDF file.
> >
> >
> >
> > --
> > Gökhan
> ------------------------------------------------------------------------------
> > Everyone hates slow websites. So do we.
> > Make your web apps faster with AppDynamics
> > Download AppDynamics Lite for free today:
> >
> http://p.sf.net/sfu/appdyn_d2d_feb_______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
> ------------------------------------------------------------------------------
> Everyone hates slow websites. So do we.
> Make your web apps faster with AppDynamics
> Download AppDynamics Lite for free today:
> http://p.sf.net/sfu/appdyn_d2d_feb
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
-- 
Gökhan

Hi,
Le 27/02/2013 10:01, Sudheer Joseph a écrit :
> I was checking the plt.xcorr and it calls the np.correlate in side it.
> It calls np.correlate(ts1,ts2, mode=2).
Just as a side note, mode=2 is the old fashioned way to specify
mode='full' [1]. This may help in reading the numpy.correlate doc.
This being said, I'm really unfamiliar with cross-correlations. I just
kind of know the usual 95% confidence interval for autocorrelation at
1.96/sqrt(n). Just as a quick check, this is what R uses by default, but
there are options like ci.type get more appropriate intervals for an MA
series
(http://stat.ethz.ch/R-manual/R-patched/library/stats/html/plot.acf.html)
best,
Pierre
[1] https://github.com/numpy/numpy/blob/master/numpy/core/numeric.py#L678

Hi,
I need to set the frame off for my plots, so that I can have axes only on the sides I want, rather than on all four sides.
I do it this way:
from pylab import *
fig = figure(figsize=(3,2),dpi=300,facecolor='w')
ax = fig.add_subplot(111,frameon=False)
ax.add_artist(Line2D((0, 0), (0, 1),color='k',linewidth=0.5))
ax.add_artist(Line2D((1, 1), (0, 1),color='k',linewidth=0.5))
ax.set_yticks([0,1])
ax.set_xticks([0,1])
show()
Unfortunately, now the ticks and axes-lines are misaligned, as seen in the screenshots attached. In the second screenshot, I've panned the plot, so the misalignment is even more visible.
matplotlib.__version__ gives '1.1.1rc'
matplotlib.get_backend() gives 'TkAgg'
-------
If I use 'WX' backend by adding these two line before the above code (before pylab import):
import matplotlib
matplotlib.use('WX')
then the misalignment still appears to be there, but that is because the Line2Ds are clipped in their width, but the ticks are not. This is seen by panning the plot.
I can set the clipping of the Line2Ds off by doing:
l1 = ax.add_artist(Line2D((0, 0), (0, 1),color='k',linewidth=0.5))
l1.set_clip_on(False)
l2 = ax.add_artist(Line2D((1, 1), (0, 1),color='k',linewidth=0.5))
l2.set_clip_on(False)
So, WX backend is fine.
Backend 'GTK' doesn't even have the above clipping problem.
-------
But any workarounds for the TkAgg backend? Because my production machine doesn't have either wx or pygtk installed, so I can only use TkAgg.
Thanks,
Aditya.

That did it, Ben!
Many thanks,
Chad
________________________________
 From: Benjamin Root <ben...@ou...>
To: CAB <ca...@ya...> 
Cc: Matplotlib Users <mat...@li...> 
Sent: Thursday, February 28, 2013 8:19 AM
Subject: Re: [Matplotlib-users] getting matplotlib to recognize a new font
 
On Thu, Feb 28, 2013 at 8:40 AM, CAB <ca...@ya...> wrote:
Hi, All,
>
>
>I am using matplotlib 1.2.0 under Windows 7 64-bit.
>
>
>I am trying to get matplotlib to recognize a new font that I downloaded (Arimo, for the curious). I put the .ttf files in the matplotlib ttf font directory (...\\fonts\\ttf\\ArimoRegularLatin.ttf, etc.), where Bitstream Vera Sans, STIX, etc. live. But matplotlib does not recognize the new font, and defaults to Vera Sans. If I load the font_manager and do a findfont, it does not find the new font and defualts to Vera Sans.
>
>
>I also tried putting the ttf files in the system font location, with the same results. When I do this, other programs like Word can see and use the font.
>
>
>Is there some trick that I'm missing, here?
>
>
>Thanks,
>Chad
>
Most likely, you need to clear out matplotlib's font cache. How to do that for windows, I don't know, but for Linux, it is as simple as "rm ~/.matplotlib/fontList.cache". Maybe there is a similar file somewhere on your system. After getting rid of that file, at the next import of matplotlib, it will recognize that that file is gone and rebuild it.
Cheers!
Ben

Hi Thomas,
Le 27/02/2013 20:59, Thomas Sprinzing a écrit :
> To sum it up: use the old 7-bit equivalent for the degree sign, not any fancydancy UTF-8 character that is commonly not included in ye olde style postscript standard font embedded into your laser printer waaaay back then in the last millenium... 
Just out of curiosity, I looked at the list of ASCII printable
characters
(http://en.wikipedia.org/wiki/ASCII#ASCII_printable_characters) and
didn't find the degree sign. However, I found it in the so-called "8
bits extensions", which I believe is just the same as the Unicode U+00B0
character.
best,
Pierre

On Thu, Feb 28, 2013 at 8:40 AM, CAB <ca...@ya...> wrote:
> Hi, All,
>
> I am using matplotlib 1.2.0 under Windows 7 64-bit.
>
> I am trying to get matplotlib to recognize a new font that I downloaded
> (Arimo, for the curious). I put the .ttf files in the matplotlib ttf font
> directory (...\\fonts\\ttf\\ArimoRegularLatin.ttf, etc.), where Bitstream
> Vera Sans, STIX, etc. live. But matplotlib does not recognize the new
> font, and defaults to Vera Sans. If I load the font_manager and do a
> findfont, it does not find the new font and defualts to Vera Sans.
>
> I also tried putting the ttf files in the system font location, with the
> same results. When I do this, other programs like Word can see and use the
> font.
>
> Is there some trick that I'm missing, here?
>
> Thanks,
> Chad
>
>
Most likely, you need to clear out matplotlib's font cache. How to do that
for windows, I don't know, but for Linux, it is as simple as "rm
~/.matplotlib/fontList.cache". Maybe there is a similar file somewhere on
your system. After getting rid of that file, at the next import of
matplotlib, it will recognize that that file is gone and rebuild it.
Cheers!
Ben

Hi, All,
I am using matplotlib 1.2.0 under Windows 7 64-bit.
I am trying to get matplotlib to recognize a new font that I downloaded (Arimo, for the curious). I put the .ttf files in the matplotlib ttf font directory (...\\fonts\\ttf\\ArimoRegularLatin.ttf, etc.), where Bitstream Vera Sans, STIX, etc. live. But matplotlib does not recognize the new font, and defaults to Vera Sans. If I load the font_manager and do a findfont, it does not find the new font and defualts to Vera Sans.
I also tried putting the ttf files in the system font location, with the same results. When I do this, other programs like Word can see and use the font.
Is there some trick that I'm missing, here?
Thanks,
Chad