matplotlib-devel Mailing List for matplotlib (Page 3)

On Jan 31, 2008 11:35 PM, Johann Cohen-Tanugi <co...@sl...> wrote:
> Actually, it seems that the following thread is also relevant to this
> issue : [matplotlib-devel] merging sympy plotting stuff with matplotlib
> <http://www.mail-archive.com/mat...@li.../msg02276.html>
Yes, but the conclusion is that someone needs to sit down and
implement the 3D stuff, but we seem quite busy, certainly I am.
I am also very interested in extracting the latex rendering engine
into a separate (pure python) package, but also don't have time for
this anytime soon.
Ondrej

Stephane Raynaud wrote:
> Hi,
>
> how about adding the possibility to give a Basemap instance to the
> resolution parameter when creating a new Basemap object, and to
> directly set some of its attributes (like coastsegs, cntrysegs, etc)
> thus preventing from computing them?
> It may be interesting when plotting several equavalent maps with fine
> resolution.
>
> It's easy to do it manually once you now all needed attributes, but it
> would be better to have it natively integrated.
>
>
> 
Stephane: The boundary datasets associated with one Basemap instance 
cannot be used with another (at least not in general). The coordinates 
of the boundaries are transformed to map projection coordinates, and 
clipped to the map projection region. So, if you have been doing this 
successfully, you've been lucky. 
However, you can and should reuse Basemap instances, to make multiple 
plots on the same map projection region. You can even pickle them, to 
reuse in other scripts.
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
325 Broadway Boulder, CO, USA 80305-3328

Hi,
how about adding the possibility to give a Basemap instance to the
resolution parameter when creating a new Basemap object, and to
directly set some of its attributes (like coastsegs, cntrysegs, etc)
thus preventing from computing them?
It may be interesting when plotting several equavalent maps with fine
resolution.
It's easy to do it manually once you now all needed attributes, but it
would be better to have it natively integrated.
-- 
Stephane Raynaud

Jouni K. Seppänen wrote:
> Jörgen Stenarson <jor...@bo...> writes:
> So, IMHO, the pdf backend should use Postscript points in the output for
> compatibility with old software. Since the trunk is supposed to really
> be the bleeding edge now, I'll try to change it, and let Mike fix it if
> it breaks. :-)
I don't see any breakage yet ;)
Your change certainly makes sense. Sorry about that -- I introduced 
that in the major transformations refactoring and thought I was adding 
generality, without really understanding all the issues.
Cheers,
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Darren Dale wrote:
> I have to report two more issues (sorry I'm reporting, not squashing, I'm 
> swamped at work.)
> 
> imshow(rand(100,100))
> colorbar()
> 
> The horizontal alignment of the ticklabels is off, they are centered on the 
> axis rather than being positioned to the right of it. Also, the image appears 
> to be shifted in the axes, to the left and the top by one pixel.
With svn 4935 I have fixed the ticklabel positioning bug, but not the 
image positioning bug.
Eric

Yeah! The code helps me a lot. Thank you! 
 Cong from China
-- 
View this message in context: http://www.nabble.com/pylib-dynamic-plot.-tp13907020p15249839.html
Sent from the matplotlib - devel mailing list archive at Nabble.com.

Jörgen Stenarson <jor...@bo...> writes:
> I get a 800x600 pixel png which is expected for a 8x6in figure
> at 100 dpi. But for the pdf I get 11.11x8.33in as determined from the
> document properties dialog in acrobat reader. Looking at the file
> information on a mac it reports the size as 800x600 for the pdf.
I can reproduce this in the trunk, but not in the 0.91 maintenance
branch. I have been too busy elsewhere to really follow the development
of the transforms branch (which became the trunk), but it seems that the
new code is applying a dpi transformation to the coordinates where the
old version just used Postscript points (1/72 in), and the default dpi
seems to be 100, so all dimensions are enlarged by a factor of 100/72.
> Doing some more digging it turns out acrobat reader reports a correct
> size for the figure if I set dpi=72 when calling savefig. Perhaps
> there is some dpi information that needs to be saved with the pdf
> file?
In PDF versions >= 1.6 the meaning of the user space coordinates can be
modified, so you could change the units from Postscript points to
something else. I think otherwise the output is compatible with PDF 1.4,
so using this feature would require users to upgrade from Acrobat 5.0 to
7.0, or whatever is equivalent in other software. One important piece of
software is pdftex (which can include pdf files) - a quick Googling
didn't reveal the relevant version, but I think it parses PDF with xpdf,
which only supports PDF 1.6 in version 3.02, released in February 2007.
In my experience it takes several years for most people to upgrade their
TeX distributions, so it is unlikely that PDF 1.6 is widely supported.
Also, changing the units should not be really necessary, since PDF is a
vector format. The only place where the dpi setting used to matter in
the pdf backend were bitmap images such as you get from imshow.
(Changing the units is useful if you need a page size larger than 200 by
200 inches, since the maximum is 144000 units.)
So, IMHO, the pdf backend should use Postscript points in the output for
compatibility with old software. Since the trunk is supposed to really
be the bleeding edge now, I'll try to change it, and let Mike fix it if
it breaks. :-)
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On Thu, Jan 31, 2008 at 04:41:41PM +0100, Gael Varoquaux wrote:
> > If this seems like a good organization to you, I'll wait for a new
> > patch and then contribute that.
> Give me a few days, but it will come.
Here is the new patch. I added visual feedback when accumulating points.
I hope the docstrings are clear.
Cheers,
Gaël

I was just experimenting with Mayavi2 when your mail arrived! Thanks. 
I'll look at it over the weekend
Mathew
Gael Varoquaux wrote:
> On Fri, Feb 01, 2008 at 02:47:21PM -0800, Mathew Yeates wrote:
> 
>> I looked into VTK and it certainly has good performance and good 
>> navigation but .... another steep learning and probably overkill for 
>> interacting with simple 3d plots.
>> 
>
> 
>> Anyone have any thoughts on this?
>> 
>
> We are working on making Mayavi2
> (https://svn.enthought.com/enthought/wiki/MayaVi) suitable for what you
> want to do. You can have a look at http://gael-varoquaux.info/blog/?p=3
> for a demo of the capabilities and the interface. This is only part of
> Mayavi2, as Mayavi2 also provides a fully-fledged visualisation
> application.
>
> Mayavi2 is based upon VTK but strives to make it interactive and to
> provide a simple API. It is still in flux and documentation is sparse (I
> am planning to address this problem this week end). Moreover some people
> find installation painful. We are working on that and in the mean time we
> are very willing to help people if they have difficulties with the
> instructions on the webpage. If you want more info or help of any kind,
> the relevant mailing list is
> https://mail.enthought.com/mailman/listinfo/enthought-dev .
>
> HTH,
>
> Gaël
>
> 

On Fri, Feb 01, 2008 at 02:47:21PM -0800, Mathew Yeates wrote:
> I looked into VTK and it certainly has good performance and good 
> navigation but .... another steep learning and probably overkill for 
> interacting with simple 3d plots.
> Anyone have any thoughts on this?
We are working on making Mayavi2
(https://svn.enthought.com/enthought/wiki/MayaVi) suitable for what you
want to do. You can have a look at http://gael-varoquaux.info/blog/?p=3
for a demo of the capabilities and the interface. This is only part of
Mayavi2, as Mayavi2 also provides a fully-fledged visualisation
application.
Mayavi2 is based upon VTK but strives to make it interactive and to
provide a simple API. It is still in flux and documentation is sparse (I
am planning to address this problem this week end). Moreover some people
find installation painful. We are working on that and in the mean time we
are very willing to help people if they have difficulties with the
instructions on the webpage. If you want more info or help of any kind,
the relevant mailing list is
https://mail.enthought.com/mailman/listinfo/enthought-dev .
HTH,
Gaël

Hi
I want to write an application which includes multidimensional 
visualization. I tried running simple3d.py but it is slowwwwww! Also, 
I'm not sure if the Navigation Toolbar is working properly.
I looked into VTK and it certainly has good performance and good 
navigation but .... another steep learning and probably overkill for 
interacting with simple 3d plots.
Anyone have any thoughts on this?
Mathew

Michael Droettboom skrev:
> Thanks. Fixed in SVN r4929.
> 
That was quick. Thanks.
/Jörgen

Thanks. Fixed in SVN r4929.
Jörgen Stenarson wrote:
> Hi,
> 
> the tickmarks seem to be misaligned when saving figures with the pdf 
> backend. I have attached a screen shot of one of the corners of the 
> figure, the tickmarks do not align with the border of the axes. The 
> figure was generated with the attached script.
> 
> /Jörgen
> 
> 
> 
> ------------------------------------------------------------------------
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Hi,
One annoyance with the TkAgg plotwindow is that it doesn't show the full 
plotarea. Comparing the plot result saved to png in visible-area-tk.png 
to the screen shot of the tkagg window in visible-area-tk-window.png you 
can see that there is a grey border covering some of the area at the edges.
/Jörgen

Hi,
the tickmarks seem to be misaligned when saving figures with the pdf 
backend. I have attached a screen shot of one of the corners of the 
figure, the tickmarks do not align with the border of the axes. The 
figure was generated with the attached script.
/Jörgen

Hi,
using the attached script to generate one pdf and one png of the same 
figure. I get a 800x600 pixel png which is expected for a 8x6in figure 
at 100 dpi. But for the pdf I get 11.11x8.33in as determined from the 
document properties dialog in acrobat reader. Looking at the file 
information on a mac it reports the size as 800x600 for the pdf.
Doing some more digging it turns out acrobat reader reports a correct 
size for the figure if I set dpi=72 when calling savefig. Perhaps there 
is some dpi information that needs to be saved with the pdf file?
/Jörgen

On Thursday 31 January 2008 12:09:03 pm Darren Dale wrote:
> I have to report two more issues (sorry I'm reporting, not squashing, I'm
> swamped at work.)
>
> imshow(rand(100,100))
> colorbar()
>
> The horizontal alignment of the ticklabels is off, they are centered on the
> axis rather than being positioned to the right of it. Also, the image
> appears to be shifted in the axes, to the left and the top by one pixel.
I looked into this some more this morning, and discovered that this tick 
behavior also occurs when yaxis.tick_right() is called. xaxis.tick_top() 
behaves as it should, and the only difference I noticed stepping through a 
script with the debugger is that at the end of set_ticks position, YAxis does 
the following, but XAxis does not:
for t in ticks:
 t.update_position(t._loc)
I don't know what is this blocks purpose, adding it to YAxis didnt seem to 
have any effect.
Darren