On Wed, Nov 4, 2009 at 12:00 AM, Greg Novak wrote:
> Is this the intended behavior? How can I get complete sample lines
> when the legend lies outside the plot area?
No, this is not intended.
It seems to me that wrong clip path is set for those legend handles.
However, your code works fine with
lly great.
>
> I can then fine tune it to my needs.
>
> Thanks Ihab
>
> Jae-Joon Lee wrote:
>>
>> Unfortunately, I don't think something like cone plots can be easily
>> done with current matplotlib.
>>
>> I guess you can define custom projection
On Thu, Nov 5, 2009 at 2:31 PM, Thomas Robitaille
wrote:
> Is there an easy way to add axes to a figure, but specify the 'rect'
> in real rather than relative units? For example, something like:
>
unfortunately no. And I'm not sure if matplotlib will ever going to
support it internally.
However,
On Mon, Nov 9, 2009 at 6:03 PM, Brent Pedersen wrote:
> how can i have the divider account for the room needed
> for the
> labels and ticks?
Doing this automatically is not straight forward. So you need to
manually adjust the area occupied by the axes.
Note that rect is [left, bottom, width, heig
I'm not exactly sure what you're trying to do. but I think what you
want can be easily achieved by simply using the masked array. Is the
example below similar to what you need?
a = np.arange(100).reshape((10,10))
m1 = np.triu(a, 1) > 0
m2 = np.tril(a, -1) > 0
#m2 = ~m1
am1 = np.ma.array(a, mask=
The bar command makes rectangles whose bottom position is 0.
The reason that bars disappear when you set log scale is that bottom
position of the bar become -infinity.
You may
* set log scale before calling the bar
or
* create bar plot but with reasonable (positive) bottom value. Take
a look
On Thu, Nov 12, 2009 at 12:07 PM, per freem wrote:
> ax.axis["xzero"].set_visible(True)
> # make other axis (bottom, top, right) invisible.
The ax.axis["xzero"] is drawn along the y=0 line. Therefore, if you
use logscale, this axis become invisible.
> invisible = ["bottom", "top", "right"]
> for
On Thu, Nov 12, 2009 at 6:32 PM, Geoffrey Ely wrote:
> Thanks for the help. With that I get:
>
> AttributeError: 'function' object has no attribute '__buffer__'
>
>
shape = fig.canvas.get_width_height()[::-1] + (4,)
im = np.frombuffer(fig.canvas.buffer_rgba(0,0),
dtype=np.uint
I think I have said this a few times, but if you're using axes_grid
toolkit, it is likely that most of the ticks, ticklabels and
axis-related command of the original matplotlib may NOT work. And that
is why I recommend you to use the spines instead.
Anyhow, adjusting the pad between axis and the
What backend are you using?
There was a similar report that the "draw" method of the qt4agg
backend does not update the screen immediately but wait until it gets
idle.
See if using other backends makes any change.
-JJ
On Sat, Nov 14, 2009 at 3:21 PM, Brian Blais wrote:
> Hello,
> I was wonde
What version of matplotlib are you using?
With the current svn, your code works okay.
-JJ
On Fri, Nov 13, 2009 at 10:37 AM, per freem wrote:
> hi all,
>
> i am trying to adjust the space (padding) between the tickmarks on an
> axes and the labels. usually, i can do this by setting
> 'xtick.majo
http://matplotlib.sourceforge.net/api/artist_api.html?highlight=fancyarrowpatch#matplotlib.patches.FancyArrowPatch
try to set shrinkA and shrinkB to 0.
Also see below for how arrows are drawn.
http://matplotlib.sourceforge.net/users/annotations_guide.html#annotating-with-arrow
-JJ
On Thu, Nov
One option would be to use a proxy artist, an artist with properties you want.
http://matplotlib.sourceforge.net/users/legend_guide.html#using-proxy-artist
Regards,
-JJ
On Fri, Nov 20, 2009 at 7:01 PM, Zunbeltz Izaola
wrote:
> Hi,
>
> I would like to have a different marker facecolor in the
Maybe this thread is helpful.
http://old.nabble.com/Problem-with-simple-use-of-draw%28%29-in-animations-of-arrays-tt26174627.html#a26175190
I guess your code will work simply by calling "recache()" instead of set_ydata.
Regards,
-JJ
On Sat, Nov 28, 2009 at 4:50 AM, Alastair McKinley
wrote:
>
On Sun, Nov 22, 2009 at 11:16 AM, per freem wrote:
> is there an existing parameter that just controls the distance between
> the xticks and the label?
As you first tried (with your example with axes_grid), labelpad
parameter does what you want.
plt.xlabel("xlabel", labelpad=0)
or
ax.xaxis.lab
This happens because, when the AxesGrid is created, gca() is set to the last
axes, which is the last colobar axes.
If you use axes_grid toolkit, you'd better not use pyplot command that works
on axes. Instead, use axes method directly.
For example, instead of "pyplot.pcolor(..)" , use "ax.pcolor
On Tue, Dec 1, 2009 at 8:48 AM, Jorge Scandaliaris
wrote:
> How difficult would be to extend the Rectangle class so besides its permimeter
> it draws lines showing halfs or thirds of the width and height?
It depends on your mileage.
However, a patch in matplotlib usually means a closed path. If
This would only meaningful if you set contour levels manually.
plt.figure()
levels = [-1, 0, 1]
fmt = {-1.:"-1",
0.:"0",
1.:"+1"}
CS = plt.contour(X, Y, Z, levels)
plt.clabel(CS, inline=1, fontsize=10, fmt=fmt)
Regards,
-JJ
On Wed, Dec 2, 2009 at 6:32 AM, Momme Butenschön wrote:
You need to add the patch to the second axes.
patch = ConnectionPatch((.5, .5), (.7, .3), 'data', 'data',
axesA=ax1, axesB=ax2,
zorder=100, arrowstyle='fancy',
connectionstyle='Angle3',
mutation_scale=1
line 1486 of _backend_agg.cpp says
/* TODO: Support clip paths */
So, it seems that, apparently, clipping with arbitrary path has not
been implemented yet for gouraud shading (pcolormesh will be properly
clipped if shading is not used).
I hope Michael pick this up some time soon.
Meanwhile, yo
some of the labels invisible.
Please post a "complete", but simple, script that reproduces your problem.
Otherwise, it is hard to track down what is wrong.
Also, please report what version of matplotlib you're using. The axes_grid
toolkit is relatively new and some of the feature ma
First of all, unless you're displaying multiple images (with aspect),
there is not much of benefit of using axes_grid toolkit. So I
strongly recommend you to stick to subplot.
axes_grid toolkit uses different kind of artists to draw ticklabels.
Therefore, most of the matplotlib command that try
On Fri, Dec 4, 2009 at 2:49 PM, Ryan Neve wrote:
> Than you for your assistance with AxesGrid.
>
> Concerning the documentation, on this page:
> http://matplotlib.sourceforge.net/mpl_toolkits/axes_grid/users/overview.htmit
> says:
>Name Default Description aspect True aspect of axes
> then
I updated the axes_grid toolkit in the svn, and I hope it is more useful.
Check the example
examples/axes_grid/demo_floating_axes.py
The output is attached.
-JJ
On Wed, Nov 4, 2009 at 9:19 AM, Jae-Joon Lee wrote:
> Are you running svn version of mpl?
> Also, as I said, the example is
but I could not get there.
>
> Can u pass me the link.
>
> Cheers Ihab
>
> On Mon, Dec 7, 2009 at 9:25 PM, Jae-Joon Lee wrote:
>>
>> I updated the axes_grid toolkit in the svn, and I hope it is more useful.
>>
>> Check the example
>>
>> exa
1241378212 13.1241378212 ..., -- -- --]
> ...,
> [-- 12.081481385 12.081481385 ..., 10.3037038589 -- --]
> [-- 11.0882356451 11.0882356451 ..., 9.95714437393 -- --]
> [-- 13.4448273754 13.4448273754 ..., -- -- --]],
> mask =
> [[ True False False ..., False
plot([1,2,3], label="Label 1")
plot([2,1,3], label="Long Label 2")
leg = legend()
# swap_and_right_align_legend
vp = leg._legend_box._children[-1]._children[0]
for c in vp._children:
c._children.reverse()
vp.align="right"
draw()
Does this close to waht you want?
-JJ
On Wed, Dec 9, 2009
On Fri, Dec 11, 2009 at 2:34 PM, Ryan Neve wrote:
> Thank you for your help. I found the problem. It was caused by using
> pyplot.title(). It is working better now.
> I next have to figure out how to do the following within AxesGrid:
>
>1. How to convert the x axis labels from an integer valu
Yes, axes location in mpl, by design, is specified in normalized
figure coordinate.
And, for the colorbar axes to match the height (or width) of the
parent axes always , you need to manually update the location of the
colorbar axes.
There are a few ways to do this. You may use event callbacks, use
There is no automatic way (that are implemented in matplotlib) to
adjust the location of the colorbar axes to match that of the parent
axes. Thus you need to manually do this.
The axes_grid toolkit (which is included in 0.99) provide some helper
function for it though. Check out the function
"demo
On Fri, Dec 18, 2009 at 3:06 AM, Panagiotis Kontaxis wrote:
> I found only the figure.savefig() function that saves figure's image only as
> a filename in the filesystem and not in a local variable.
http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.savefig
savefig can take
I can reproduce this bug with the current svn.
Matthias, can you file a bug on this in the issue tracker?
I think the bug is related with the changes made back in august.
http://old.nabble.com/ginput-default-mouse-configuration-td24924861.html
Attached is a quick fix, so please test it.
I didn'
I just filed a bug related with this.
https://sourceforge.net/tracker/?func=detail&aid=2917758&group_id=80706&atid=560720
I think the possible solution could be
1) we keep the copied version of the input data as a cache, and
provide a api to access the cache.
2) Or forsce set_[x|y]data to alw
set_size_inches method takes a "forward" parameter, which adjusts the
window size if True, which I believe is what you want. However,
according to the documentation, this is only supported in the Gtk and
Wx backend.
So, easy way would be to switch to other backend if possible.
I quickly go through
As far as I can see, this happens when there are obsolete rst files
(related with the Gallery I guess), created during the doc. build with
previous svn checkout.
For example, I recently removed
mpl_examples/axes_grid/demo_fixed_size_axes.py from the svn. But if
you ever have built the documentatio
ax = gca()
ax.yaxis.set_ticks_position("right") # ticks and ticklabels
ax.yaxis.set_label_position("right") # axis label
-JJ
On Thu, Dec 24, 2009 at 8:34 AM, Maximilian Fabricius wrote:
> Hello,
> I apologize if this is the n-th time this question is asked.
> I wondered what the canonical way i
On Thu, Dec 24, 2009 at 3:53 PM, per freem wrote:
> i want it to eliminate the second
> subplot of the first row and instead make the first subplot on the
> first row take up two plots worth of space,
Matpltlib's subplot does not support it as of now.
There a few work around you may try, but it
On Sun, Dec 27, 2009 at 2:37 PM, Eric Firing wrote:
> What are the circumstances under which one would call set_data() and not
> want or need an update?
If you ask me, I'm +1 to update the plot always. But, apparently, the
original author of this code wanted to do some checks to avoid
unnecessary
On Sun, Dec 27, 2009 at 7:31 PM, Eric Firing wrote:
> I don't understand what your script, below, is intended to do or show. I
> haven't run it with mpl prior to my change. With the change, it simply
> draws a single line, or at least that is all I see on the plot.
Before your change, it draws t
On Mon, Dec 28, 2009 at 12:39 AM, Eric Firing wrote:
> So, which way is better? I assume the change is an improvement, because
> the behavior with a list should be the same as with an ndarray.
>
I agree with you.
>
> We could split the recaching up into parts that can be done independently on
On Wed, Dec 30, 2009 at 12:05 PM, Eric Emsellem wrote:
> I have tried with rgba sequences but no luck there. The help of hist
> << color: matplotlib color arg or sequence of rgba tuples >>
>
Based on my quick look at the code, it seems that the documentation is
incorrect. I believe it should be
This is a kind of bug that is quite hard to trace unless we can
reproduce the error.
As far as I know, there has been a report that matplotlib does not
work well with GPL Ghostscript 8.63. And I'm not sure if it is
related.
http://old.nabble.com/Segmentation-fault-with-EPS-output-on-matplotlib->%
http://matplotlib.sourceforge.net/faq/howto_faq.html#automatically-make-room-for-tick-labels
-JJ
On Wed, Dec 30, 2009 at 6:30 AM, Eero Nevalainen
wrote:
> Hi,
>
> I find myself repeatedly manually adjusting subplot params, e.g.
> figure.subplot.left, to remove extra white space on my figures. Is
How about just extending the functionality of the "annotate"? I
believe it should be quite straight forward since "annotate" already
support "offset points". And "points" in matplotlib is dpi
independent.
However, I think calling "annotate" for an offset text is a bit
inconvenient for now.
annota
I think the current method names of Annotation class (originally from
the Text class) is a bit confusing.
And this needs to be fixed.
Anyhow, instead of calling set_position method, you need to set the
"xytext" attribute directly.
this_annotation.xytext = (event.x, event.y)
Regards,
-JJ
On Wed, Jan 6, 2010 at 5:50 AM, Gergely Ungvary
wrote:
> I guess I'm not
> the only one plotting statistical data with manually specified bins.
Yes, and mpl works fine with manually specified bins.
On the other hand, I don't see why you want to change the widths of
the bar. As far as I can see, t
What version of matplotlib are you using?
This may be the bug that already have been fixed.
Neither with the maintenance branch nor the current svn reproduce this problem,
as can be easily seen from the gallery
http://matplotlib.sourceforge.net/examples/axes_grid/demo_parasite_axes2.html
-JJ
On
This is because "legend" creates a legend only in the current axes.
Note that "twinx" creates a separate axes.
You need to manually specify which plot items to show in the legend.
http://matplotlib.sourceforge.net/users/legend_guide.html
Or, you may use axes_grid.parasite_axes which does this jo
On Sun, Jan 3, 2010 at 4:30 PM, per freem wrote:
> is there a way to do this in matplotlib?
With subplots, I believe the answer is no. You may try to fiddle with
anchor positions of individual subplots, but this will only work for
some limited cases.
With axes_grid toolkit, yes.
-JJ
--
I can reproduce this error with the current svn.
I doubt if this is a matplotlib issue, because it works fine if the
number of axes is small.
To me, it seems as some memory error in the ghostscript, but my quick
googling did not show any relevant information.
So, I hope some postscript expert take
On Sat, Jan 9, 2010 at 8:20 AM, Eric Emsellem wrote:
> Hi
> thanks A LOT for taking the time to test this and for the suggestions.
>
> Yes, pcolormesh is needed (or at least I think) because in the "real"
> example (the figures I am trying to make) the pixels are rotated meaning
> that these are p
You code works okay with the current svn.
See if changing the distiller option makes any difference
("ps.usedistiller" in the rc file).
The best would be for you to upgrade to the recent release of
matplotlib if possible.
Regards,
-JJ
On Mon, Jan 11, 2010 at 8:35 AM, John Reid wrote:
> Hi,
>
See this example
http://matplotlib.sourceforge.net/examples/pylab_examples/scatter_hist.html
Or, you're willing to learn something new, you may use axes_grid toolkit.
http://matplotlib.sourceforge.net/examples/axes_grid/scatter_hist.html
-JJ
---
First of all, to use "\color" with TeX, you need to use "color"
package, i.e., you need to modify your latex preamble to include that
package. This can be done by
import matplotlib.pyplot as plt
plt.rcParams["text.latex.preamble"] = r"\usepackage{color}"
I guess the error you encounter is because
On Sat, Jan 9, 2010 at 4:27 PM, Dominik Szczerba wrote:
> When using white over back color scheme the legend() is unreadable, with
> apparently hard-coded white legend background - or is there a way to set
> it in the rc file?
>
Unfortunately no.
I recommend you to manually change the color of th
On Mon, Jan 11, 2010 at 2:38 PM, Dominik Szczerba wrote:
> Hmmm, that property really deserves its own rc param, but if you do not
> like it, it should at least be somewhere automatically set to the
> current background color to be resistant against people like me ;) I
> would be happy to have suc
it only doesn't work when I set
> ps.usedistiller to xpdf. With False or ghostscript it works ok but gives
> me output with different page sizes. AFAIK xpdf is the way to go for
> publication quality graphics. Do you know how I can get it to work? Is
> it worth trying the svn version?
>
Contour will work as expected if the axes is in log scale. See below.
z = np.arange(100).reshape((10,10))
x = np.logspace(0, 4, 10)
y = np.logspace(0, 4, 10)
ax1 = subplot(121)
ax1.contour(np.log10(x), np.log10(y), z)
ax2 = subplot(122)
ax2.set_xscale("log")
ax2.set_yscale("log")
ax2.contour(x,
On Mon, Jan 11, 2010 at 6:49 PM, John Reid wrote:
> Thanks for help so far. Any more ideas? I'll try the svn if it is just a
> case of checking it out and compiling.
>
Please try.
I don't think the current svn version will make any difference. But,
at least I can send you a patch that I think fi
When you check out the svn, please try to apply the patch attached.
patch -p1 < ps_distiller.patch
I hope this solves your problem.
Regards,
-JJ
On Mon, Jan 11, 2010 at 7:25 PM, Jae-Joon Lee wrote:
> On Mon, Jan 11, 2010 at 6:49 PM, John Reid
> wrote:
>> Thanks for help s
On Tue, Jan 12, 2010 at 12:21 PM, dugolo wrote:
> Basically, I would like to put ax1 on both fig1 and fig2 without having to
> repeat all of the code for plots on ax1.
>
The Axes instances in matplotlib can only have one parent figure,
i.e., the axes cannot be shared among different figures.
But
ee if turning that on and off
make any difference.
Regards,
-JJ
On Tue, Jan 12, 2010 at 5:29 AM, John Reid wrote:
>
>
> Jae-Joon Lee wrote:
>> When you check out the svn, please try to apply the patch attached.
>>
>> patch -p1 < ps_distiller.patch
>>
>>
On Mon, Jan 11, 2010 at 3:20 PM, Gökhan Sever wrote:
> Another thing I noted in these images, Qt4Agg produced one looks much
> prettier to my eyes than the PS. What could be causing the jiggly rendering
> in the PS?
>
The rendering quality of the fonts depends on a lot of things.
And I think your
Regards,
-JJ
On Wed, Jan 13, 2010 at 3:16 AM, John Reid wrote:
>
>
> Jae-Joon Lee wrote:
>> I'm afraid that there is not much I can help anymore.
>>
>> Just in case, does the same error occur when my patch is not applied?
>>
>> Is it an error or just a war
On Tue, Jan 12, 2010 at 9:56 PM, Gökhan Sever wrote:
> What could be causing this discrepancy? Is there any way to use an
> alternative PS creator with MPL? or an option to increase e.g. bits per
> pixel option somewhere in the configuration?
>
There can be a lot of things. However, you cannot ju
You may consider to use proxy artists.
plot([1,2,3], "s-")
plot([1,3,2], "d-")
l1 = Line2D([0], [0], marker="s", color="k")
l2 = Line2D([0], [0], marker="d", color="k")
p1 = Rectangle((0, 0), 1, 1, fc="b", ec="none")
p2 = Rectangle((0, 0), 1, 1, fc="g", ec="none")
legend([p1, p2, l1, l2], ["col
The workarounds suggested in this thread does not work?
To me, the ordinal thing is not actually a bug, but you need some
extra caution to avoid this error happening.
The issue with the label roration is a different matter though.
Regards,
-JJ
On Wed, Jan 13, 2010 at 8:16 AM, Rodribat wrote:
On Wed, Jan 13, 2010 at 11:32 AM, Gökhan Sever wrote:
> I printed the PNG and PS file. The result looks same on paper as well. I was
> comparing the two ps file one from IDL one from MPL. IDL looks neat both on
> the screen and printed.
>
Are you saying that the printout of the mpl-created postsc
On Thu, Jan 14, 2010 at 4:38 AM, Mark Bakker wrote:
> Does matplotlib have a routine that can fit a cubic Bezier curve through an
> array of 2D points?
>
> I saw some Bezier routines in Path, but couldn't find what I am looking for.
>
As far as I know, no.
> If matplotlib doesn't have it, does a
This has indeed been fixed.
http://matplotlib.svn.sourceforge.net/viewvc/matplotlib/trunk/matplotlib/lib/matplotlib/ticker.py?r1=7677&r2=7980
Some minor changes may not be listed in the changelog.
Regards,
-JJ
On Thu, Jan 14, 2010 at 12:29 PM, Jeremy Lewi wrote:
> Hello,
>
>
>
> I think I’m
The svn version has a new keyword "bbox_extra_artists", which could be used.
But, there is no easy way for the released version of matplotlib.
Below is a workaround you may use, but it's a bit complicated.
Regards,
-JJ
fig = figure(1)
ax = fig.add_subplot(111)
l1, = ax.plot([1,2,3])
leg = figl
Colorbar axes is a rather special and things need to be set during the
initialization.
Here is a slightly modified version of your script.
While it does not produces error, I'm not sure if the result is correct.
-JJ
import numpy as np
import matplotlib.pyplot as plt
from matplotlib.dates impor
http://matplotlib.sourceforge.net/faq/howto_faq.html#automatically-make-room-for-tick-labels
The above example is for ticklabels, but can be easily adopted for axes title.
Regards,
-JJ
On Mon, Jan 18, 2010 at 12:07 PM, Jeremy Lewi wrote:
> Hi,
>
>
>
> The title for my axes is being cutoff bec
This is the feature that is not properly documented.
You should call annotate with optional keyword
annotation_clip=False,
See below for the details.
http://matplotlib.sourceforge.net/api/artist_api.html?highlight=annotation#matplotlib.text.Annotation.set_annotation_clip
I'll fix the do
On Tue, Jan 19, 2010 at 2:48 AM, Kurt Forrester
wrote:
> I modified the script for the hax. annotate(...) to include the
> annotate_clip=False, however there is no change in the behaviour of the
> arrows.
It should be "annotation_clip" not "annotate_clip", but it may be just a typo.
Anyhow, as f
On Mon, Jan 18, 2010 at 5:16 PM, Damon McDougall
wrote:
> The figure is actually cropped.
Correct.
> Is there another way around this that will get rid of the whitespace and have
> the physical figure be 483.69687pt wide?
Do not use bbox_inches="tight". Instead adjust the position of the
axes
While I don't known much about how table class in matplotlib works
internally, I think it would not be easy (because the legend is quite
a unique object whose position is determined at drawing time).
The current legend implementation is based on the offsetbox module.
While it does not have a tabl
This is generally a very difficult thing to do, as the position and
the extent of the text is determined when the figure is drawn.
The best way, I guess, is to create a customized Text class, but I do
not recommend this unless you're familiar with matplotlib internals.
If you're using svn version
be further modified. I'll take a
look later.
Regards,
-JJ
On Tue, Jan 19, 2010 at 9:47 PM, John Hunter wrote:
> On Tue, Jan 19, 2010 at 4:34 PM, Jae-Joon Lee wrote:
>> This is generally a very difficult thing to do, as the position and
>> the extent of the text is determined wh
On Wed, Jan 20, 2010 at 9:17 AM, Mario Mech wrote:
> cl = cb.ax.get_yticklabels()
>
> results in a list of Text objects like Text(0,0,''). So my problem is more to
> get the TickLabels for vertical colorbars.
>
Can you elaborate why you need to do this?
This is a general behavior of Axes in matp
On Tue, Jan 19, 2010 at 3:08 PM, Kurt Forrester
wrote:
> Additional information that I forgot to supply was that on python
> 2.5/windows/matplotlib 0.98.xxx (my work machine, not accessible at the
> moment for the subversion number) this worked fine and there may have been a
> regression from this
On Wed, Jan 20, 2010 at 12:12 PM, Mario Mech wrote:
> the smallest value (0.0) is labeled with "-0.0". I just want to get rid of
> the minus sign.
>
This is because the actual value is "-9.e-06" (this inherits
from the levels of contour).
While I think we're fixing a wrong problem (the c
On Wed, Jan 20, 2010 at 1:13 PM, Kurt Forrester
wrote:
> I am not too sure what the design behaviour is but it is certainly not doing
> what I expected. I do appreciate your effort in resolving this. Please do
> let me know if there are any further tests I can perform to demonstrate the
> issue or
On Wed, Jan 20, 2010 at 1:36 PM, Eric Firing wrote:
> Second and related advice: don't fiddle directly with tick labels except as
> a *last* resort. Instead, take care in selecting tick values, and if
> necessary, customize the Formatter.
>
Agreed. It was a quick hack.
> The fact that a default
On Wed, Jan 20, 2010 at 2:04 PM, Eric Firing wrote:
> The reason for this fudge in contour is that contourf fills
> lower < z <= upper
> for each consecutive pair of contour levels.
> When the minimum value of z coincides with the lowest level, then regions
> with that minimum are left blank; so t
On Wed, Jan 20, 2010 at 3:07 PM, Kurt Forrester
wrote:
> the output from the script is:
>
> annotation_clip = None
> checking is point is inside the axes : [ 30.875 233. ]
> contains_point = 0
> _check_xy returning False
> exit without drawing due to annotation_clip
>
>
Weird.
How about th
On Thu, Jan 21, 2010 at 9:37 AM, Kurt Forrester
wrote:
> The first one reported None.
> The second one reported False.
And the text is still not drawn with the second example?
-JJ
--
Throughout its 18-year history, RSA
On Thu, Jan 21, 2010 at 12:53 PM, Kurt Forrester
wrote:
> Sorry the text IS drawn in the second example. So the setting of the
> attribute after it is drawn (before it is shown) seems to do the trick.
>
> Kurt
It seems that somehow the annotation_clip parameter is ignored when it
is given during
On Thu, Jan 21, 2010 at 1:16 PM, Andrew Kelly wrote:
> (Part of my confusion stems from the fact that I can access the Tick
> instances on the Axis but when I call Tick.set_label2("New Label") the label
> does not get drawn. Perhaps I am being daft.)
>
http://matplotlib.sourceforge.net/api/axis_
Do you happen to use the svn version?
Regards,
-JJ
On Thu, Jan 21, 2010 at 3:06 PM, Gökhan Sever wrote:
> Possibly a question for JJ:
>
> pary.axis["right"].get_helper()._label_angles["right"]=270
>
> This lines complain in my script when I try to run it:
>
> Traceback (most recent call las
On Thu, Jan 21, 2010 at 4:13 PM, Kurt Forrester
wrote:
> Just to add one more query to the thread, do you consider a point on a
> vertex of the axes to be a candidate for annotation without clipping? That
> is to say if there is a point (0,0) I wish to annotate, and the origin of
> the axes contai
On Thu, Jan 21, 2010 at 2:31 PM, Andrew Kelly wrote:
> Turning label2On = true turned on the labels as directed. However, the
> function label2.set_text("New Tick Label") does not update the
> actual text. I can set_size(), etc and it works, but set_text() does not
> update. Any ideas
On Thu, Jan 21, 2010 at 6:16 PM, Gökhan Sever wrote:
> Yes, it is running from the latest trunk check-out.
The internals of how ticks, ticklables work in the svn version have
significantly changed, which I hope is an improvement. Unfortunately,
"_label_angles" is deprecated and should not be used
ved image: http://img46.imageshack.us/img46/3849/imagevp.png
>
> The code that produces that script:
> http://code.google.com/p/ccnworks/source/browse/trunk/dccn_plot.py
>
> Any ideas?
>
>
> On Thu, Jan 21, 2010 at 5:45 PM, Jae-Joon Lee wrote:
>>
>> On Thu, Jan 21
On Thu, Jan 21, 2010 at 9:24 PM, Eric Firing wrote:
> I changed my mind and decided you are correct in thinking the change should
> be made in contour.py. I now make the bottom boundary adjustment at the
> last possible time, and in such a way that it does not change the levels
> array at all.
On Mon, Jan 25, 2010 at 9:14 AM, Dimitri Linten
wrote:
> What is the best way to do this ?
Please explain what you want and what your issue is.
Do not expect us (developers or other users) to study your code. If
possible, post a small stand-alone example that others can simply run.
As far as the
You mean removing the the axes frame?
subplot(111, frame_on=False)
I'm sorry but it is not clear what you want.
Regards,
-JJ
On Tue, Jan 26, 2010 at 4:18 AM, Michael Cohen wrote:
> Hi all,
> Thanks for the help so far. One more question -
> How do I completely remove the axes?
> I currentl
If you do not mind the output size slightly adjusted, try
savefig("somename.png", bbox_inches="tight")
Regards,
-JJ
On Tue, Jan 26, 2010 at 3:27 PM, John Hunter wrote:
> On Tue, Jan 26, 2010 at 12:00 PM, cwurld wrote:
>>
>> Hi,
>>
>> I am trying to generate some pngs without using the GUI i
ith the tick marks
> disappear.
> What you suggest here does in fact remove the bounding rectangle. Now, how
> can I get rid of the tick marks?
>
> Cheers
> Michael
>
> On 01/26/2010 02:18 PM, Jae-Joon Lee wrote:
>>
>> You mean removing the the axes frame?
>>
*bbox_transform* expects a Transform instance.
ax = subplot(111)
ax2 = inset_axes(ax, width=3, height=2, loc=3,
bbox_to_anchor=(0.1, 0.1),
bbox_transform=ax.figure.transFigure)
Note that, bbox_to_anchor with a tuple of two numbers creates a bbox
with width=heig
201 - 300 of 847 matches
Mail list logo
