matplotlib-users Mailing List for matplotlib

Dear basemap team!

(I hope this is the right list for posting basemap problems? I reported 
the problem to the EPD list, but they don't have the capacity to test 
it due to the lack of GDAL installations)

There's a fatal (as in crashing Python) library dependency in relation 
with current gdal modules on the Mac. I'm using Kyngchaos' latest 
frameworks for GDAL (1.8.0)

Testcode: testgdal.py from Enthought/Examples/basemap-1.0/ (latest EPD)

This file starts with:

from osgeo import gdal, ogr
from mpl_toolkits.basemap import Basemap, cm

and when I run it like that, Python crashes with this:

Assertion failed: (0), function query, file AbstractSTRtree.cpp, line 286.
Program terminated by uncaught signal #6 after 6.80 seconds (running 
via Textmate, but same thing in ipython)

Because in the past I had some incompatibilities due to different numpy 
versions, which thanks Newton don't exist anymore (or do they?), I was 
trying around 
with the import sequences and found when I inverse these 2 like this:

from mpl_toolkits.basemap import Basemap, cm
from osgeo import gdal, ogr

the file runs perfectly.

I puth the crash report here, in case it helps:

http://dl.dropbox.com/u/139035/Basemap_crash.txt

Best regards,
Michael

On Thu, Feb 17, 2011 at 4:12 AM, Stephan Markus <zw...@we...> wrote:

>
> Small update:
>
> I tried the very same code with MPL 1.0.1 and Python 2.5.0 on Linux 64 and
> Python 2.5.4 on Win32 and it runs w/o throwing any exceptions there!
>
> But: the behaviour is still not that what I expected. Still these issues
> are
> remaining:
> - the smallest magnitude (center magnitude in other words) is 0.1 and I'd
> like to display way smaller values
> - the smallest magnitude doesn't even change when zooming
> - the grid lines and ticks do not show as I'd expect (see my last message)
> when zooming
>
>
> That's why I'd rather stick to a linear scale, doing my own logarithmic
> conversion, limit my data at lowest value I need and just use an offset for
> the scale.
>


I see what you mean.  This problem is almost identical to another thread
going on where we can't seem to correctly do log scale for 3d plots.  The
tick locators are in the wrong positions (the major ticks should be evenly
spaced) and the error message is similar to one I have been encountering in
mplot3d.

I will look a little further into this and see if I can kill two birds with
one stone...

Ben Root

Small update:

I tried the very same code with MPL 1.0.1 and Python 2.5.0 on Linux 64 and
Python 2.5.4 on Win32 and it runs w/o throwing any exceptions there!

But: the behaviour is still not that what I expected. Still these issues are
remaining:
- the smallest magnitude (center magnitude in other words) is 0.1 and I'd
like to display way smaller values
- the smallest magnitude doesn't even change when zooming
- the grid lines and ticks do not show as I'd expect (see my last message)
when zooming


That's why I'd rather stick to a linear scale, doing my own logarithmic
conversion, limit my data at lowest value I need and just use an offset for
the scale.
-- 
View this message in context: http://old.nabble.com/Polar-plot---problem-with-negative-values-for-radius-tp30936638p30948265.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hi all,

It's exactly as said. I am using OS 10.6

If I use ipython -pylab and later try to plot anything, the GUI for plotting launches and I just get a beachball.

However, if I do ipython and then import plot, I can do a plot with no problem. 

I did a search but came up with nothing. I have this problem whether I use apple python or the python2.7 downloaded from python.org. 

I am new to the whole terminal/programming thing. As you can imagine, everything is very difficult. Any help is appreciated

God bless,
Matthias

Ben,

I should have mentioned that I already tried that. When I set the rscale to
'log' the plot crashes when zooming or mpl cannot even create it.

Maybe some example code will help:
----------------
from numpy import arange, sin, pi, cos, ones
from matplotlib.backends.backend_tkagg import FigureCanvasTkAgg,
NavigationToolbar2TkAgg
from matplotlib.figure import Figure
import Tkinter as Tk

root = Tk.Tk()


f = Figure(figsize=(5,4), dpi=100)
ax = f.add_subplot(111, projection='polar')

t = arange(0.0,2*pi,0.01)
s1 = ones(len(t))*10

ax.set_rscale('log')
ax.plot(t,s1)


canvas = FigureCanvasTkAgg(f, master=root)
canvas.show()
canvas.get_tk_widget().pack(side=Tk.TOP, fill=Tk.BOTH, expand=1)
toolbar = NavigationToolbar2TkAgg(canvas, root)
toolbar.update()
canvas._tkcanvas.pack(side=Tk.TOP, fill=Tk.BOTH, expand=1)
Tk.mainloop() 
----------------

Using this code the plot will show up but you can see the 10^-1 and 10^-2
tick labels overlapping in the center. Ok, it shouldn't be a big deal to get
rid of them. The major problem is if you try to zoom out, the tick labels
move away from the center and if you try to zoom into the plot it eventually
throws an exception "ValueError: cannot convert float NaN to integer".
If you try to plot smaller values (e.g. replacing the line 's1 =
ones(len(t))*10' with 's1 = ones(len(t))') mpl also throws an ValueError
exception and does not even create the plot.

Let me know if you need full tracebacks.

Btw: I am using Matplotlib 1.0.1 and Python 2.6.0 on Windows 64.
-- 
View this message in context: http://old.nabble.com/Polar-plot---problem-with-negative-values-for-radius-tp30936638p30947935.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On 2/16/11 9:04 PM, Gui...@cs... wrote:
> Hi folks,
>
> I'm new to this list and first of all I'd like to thank all the matplotlib developers for putting together such a great package!!
>
> I've been using the Basemap toolkit recently and notice that the scale is generated on a zorder=0 layer.
>
> [cid:DCC...@ar...]
>
> I sometimes have to stack different layers and assign them a zorder argument to play with their ranking. This can results in the masking of the scale bar:
>
>
> [cid:A49...@ar...]
>
> As a workaround, I can set a negative zorder for the various features that could overlay the scale on the map, though.
> Still, I think it would be nice to be able to have a supplementary karg added to the class.
>
> Cheers
> Gill

Done (svn revision 8983).  If you don't want to update from svn, you 
just iterate over the list returned by drawmapscale and use the 
'set_zorder' method of each element.

-Jeff

Hi folks,

I'm new to this list and first of all I'd like to thank all the matplotlib developers for putting together such a great package!!

I've been using the Basemap toolkit recently and notice that the scale is generated on a zorder=0 layer.

[cid:DCC...@ar...]

I sometimes have to stack different layers and assign them a zorder argument to play with their ranking. This can results in the masking of the scale bar:


[cid:A49...@ar...]

As a workaround, I can set a negative zorder for the various features that could overlay the scale on the map, though.
Still, I think it would be nice to be able to have a supplementary karg added to the class.

Cheers
Gill

Dr Guillaume Duclaux

Mineral Down Under Flagship & AuScope Grid
CSIRO Earth Science and Resource Engineering

Phone: +61 8 6436 8728  | Fax: +61 8 6436 8559  | Mobile:  +61 422 289 732

gui...@cs...<mailto:gui...@cs...> | www.csiro.au<http://www.csiro.au/> |
Address: Australian Resources Research Centre, 26 Dick Perry Avenue, Kensington WA 6151

PLEASE NOTE
The information contained in this email may be confidential or privileged. Any unauthorised use or disclosure is prohibited. If you have received this email in error, please delete it immediately and notify the sender by return email. Thank you. To the extent permitted by law, CSIRO does not represent, warrant and/or guarantee that the integrity of this communication has been maintained or that the communication is free of errors, virus, interception or interference.

Please consider the environment before printing this email.