On Wednesday 26 March 2008 19:39, Chris Withers wrote:
Matthias Michler wrote:
My x-axis is time, and as new points are plotted, even though I'm
following the above recipe pretty closely, the x-tick spacing isn't
getting sorted out, so I end up with just a jumble as the tick labels
for
On Wed, Mar 26, 2008 at 10:38 PM, sa6113 [EMAIL PROTECTED] wrote:
I use matplotlib and Backend Agg to draw a plot , I want to show this plot in
my GUI in specific area (Plot area) , I need to have the image object in
[snip]
Is it clear?
Not to me :)
Do you mean that you've already
Forget it. I was putting lat/long instead of long/lat.
Regards,
Kurt
-
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
KURT PETERS wrote:
I'm trying what I thought was a simple test and getting bad results. I am
taking some lat long coords, and feeding it into a map. The conversion is
not giving real values that can be plotted on a map (and actually produces
an error when I use annotate).
I'm including
And, before someone asks, Why are you using h and this line:
h= [seg[0]*0.000278,seg[1]*0.000278]
ax.annotate(seqnum[nshape],h),
I was using this, instead, but tried to experiment with things to try to
make things work right:
ax.annotate(seqnum[nshape],seg)
.
I usually
Matthias Michler wrote:
the above script leads
to a different behaviour on my system.
What is that behaviour and what version of matplotlib are you using?
I think it is the expected behaviour. The number of xtick is aproximately
constant and some tick get sorted out, when the xlimits are
Dear Mailinglist,
Today I tried to change the fontset to sans-serif for a whole plot.
Everything except the ticks could be adjusted.
This is what I tried first:
***
ffont = {'size':'20','family':'sans-serif'}
xticks(**ffont)
Hello Chris,
On Thursday 27 March 2008 12:22, Chris Withers wrote:
Matthias Michler wrote:
the above script leads
to a different behaviour on my system.
What is that behaviour and what version of matplotlib are you using?
I think it is the expected behaviour. The number of xtick is
Gerolf Ziegenhain wrote:
Dear Mailinglist,
Today I tried to change the fontset to sans-serif for a whole plot.
Everything except the ticks could be adjusted.
This is what I tried first:
***
ffont = {'size':'20','family':'sans-serif'}
Have you tryied : ipython -pylab ?
It launch an ipython shell that support mathplotlib gui loop.
-Message d'origine-
De : [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
] De la part de Wolfgang Kerzendorf
Envoyé : mercredi 26 mars 2008 08:31
À : matplotlib-users@lists.sourceforge.net;
[EMAIL
Matthias Michler wrote:
I'm not sure that I understand you correctly. The code I refering is the one
which I attached some mails ago. The following works for me:
Ah, okay, to get the problem I was having, change your script as follows:
More complete:
I tried all permunations of backends. Now I stick to PS, because I use
matplotlib from commandline with scripts. The environment is debian/etch
with a current version of matplotlib (self compiled).
Try this script
from pylab import *
t
Michael Droettboom wrote:
I think the real reason this wasn't done is that its tricky to do at the
C level in a cross-platform way. At present it uses the regular POSIX
fopen in C, which isn't really Unicode aware.
The actual error is from trying to put the filename in a std::string,
but
Ryan Krauss wrote:
I think this line in the rc file is the trick
#savefig.dpi : 100
nope. I think all that does is set the default dpi for savefig. I don't
want any default, I want it to use the same dpi that is being used for
display, and I don't know ahead of time what that is, I
On Thursday 27 March 2008 01:27:28 pm Gerolf Ziegenhain wrote:
More complete:
I tried all permunations of backends. Now I stick to PS, because I use
matplotlib from commandline with scripts. The environment is debian/etch
with a current version of matplotlib (self compiled).
Try this script
I guess you could read the rcParams value that corresponds to the
screen display and set rcParams['savefig.dpi'] to that value (this
might work):
mydpi = rcParams['figure.dpi']
rcParams['savefig.dpi'] = mydpi
But that seems slightly hackish and maybe not much more elegant than
what you are
Ronald Oussoren wrote:
That load command is for LC_UUID. The version of macholib in subversion
should have some support that is (basicly ignoring the entire load
command because macholib won't have to change it), could you test that
(easy_install macholib==dev)?
Yup, that problem is
Quiver doesn't seem to be able to handle begin passed zeros for the
vector lengths. The full error output is below. I'm running Leopard
with macpython 2.5.2 using
matplotlib-0.91.2-py2.5-macosx-10.3-i386.egg
The following code does not work:
rx = numpy.array([0.0,0.0])
ry =
Hello, could someone please help me understand a strange problem, possibly
associated with PYTHONPATH. When I import matplotlib, pylab, or scipy from
any directory other than the root installation directory, it fails. However,
if I'm in the python installation directory there are no errors. Thanks
19 matches
Mail list logo
