Hi,
In a previous email I pointed out that I was having problems with pcolormesh
output as a PDF: the files are really big and impractical even for smallish
arrays (1000x1000 pixels). I don't have that problem using imshow, which
presumably resamples the image or somesuch wizardry :) Here's an example
import pylab
data = pylab.randn((512*512)).reshape((512,512))
#First imshow. I use the dpi keyword "just in case"
pylab.imshow ( data, interpolation='nearest')
pylab.savefig ("/tmp/imshow_72.pdf",dpi=72)
pylab.savefig ("/tmp/imshow.pdf")
#Now pcolormesh
pylab.pcolormesh ( data )
pylab.savefig ("/tmp/pcolor_72.pdf",dpi=72)
pylab.savefig ("/tmp/pcolor.pdf")
This results in the following files:
166K /tmp/imshow_72.pdf
307K /tmp/imshow.pdf
2.6M /tmp/pcolor_72.pdf
2.7M /tmp/pcolor.pdf
So: in the imshow case, the dpi keyword makes a difference (good!), but if you
compare the pcolormesh and imshow filesizes you immediately notice a large
difference. The rendering of the pcolor files is also very slow, line-by-line
sort of thing. I presume that the different patches are stored as vectors,
and that's why there's no change with setting dpi to 300 or to 72.
Is this the expected behaviour?
Thanks,
J
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
