So, you need to know what tools to use to read in grib2 data? There are two
particular grib readers that I am familiar with: PyNIO and pygrib2. PyNIO
actually isn't a grib reader, as much as a swiss army knife of file
readers. It is very similar to the netcdf4 interface, so if you are
familiar with
Hi Chris,
Thanks for that tip. I'll give it a try. They are big images (2048 x
2048) so it seems like your suggestion should work.
Jon
On Tue, Oct 14, 2014 at 12:18 PM, Chris Beaumont
wrote:
> I've found that, for big images, the *first* draw is very slow, due to the
> intensity scaling of t
I am happy to announce that I have tagged a release candidate for
1.4.1. This is a bug-fix release which fixes most of the bug that
popped up in 1.4.0 including:
- setup.py does not die when freetype is not installed
- reverts the changes to interactive plotting so `ion` will work as expected
I've found that, for big images, the *first* draw is very slow, due to the
intensity scaling of the image, which happens at full resolution. Panning
and zooming afterwards is fast because the intensity scaling is cached, but
changing the data array or updating the norm kwarg is slow again. I made
M
Only if there are multiple figures (plt.draw() operates on the current
active figure, while fig.draw() explicitly operates upon that figure).
Another possibility is that the bottleneck truly is the IO. Depending on
exactly how fits work, it might be lazily loading data for you, so the test
without
Hmm. I just saw that you suggest fig.draw(). Is there a difference with
plt.draw()?
Jon
On Tue, Oct 14, 2014 at 11:20 AM, Slavin, Jonathan
wrote:
> Hi Ben,
>
> Sorry, in my little example, I left out a few things. I do update first
> after the first call. And I do call draw() after other ca
Hi Ben,
Sorry, in my little example, I left out a few things. I do update first
after the first call. And I do call draw() after other calls. So here is
a more accurate representation of what I do:
first = True
fig = plt.figure()
for file in files:
hdu = fits.open(file)
image = hdu[0].
Also, you aren't updating "first" after the first call, so it is constantly
making new axes and recalling imshow().
Ben Root
On Tue, Oct 14, 2014 at 10:41 AM, Benjamin Root wrote:
> What is happening is that you are not telling the image to redraw, so you
> are only seeing it refresh for other
What is happening is that you are not telling the image to redraw, so you
are only seeing it refresh for other reasons. Try adding a fig.draw() call
prior to the raw_input() call.
Cheers!
Ben Root
On Tue, Oct 14, 2014 at 10:03 AM, Slavin, Jonathan
wrote:
> Hi all,
>
> In my work lately I have o
Hi all,
In my work lately I have often wanted to browse through a series of
images. This means displaying the image(s), looking at it/them and then
continuing. I have coded this in a few different ways, but it is generally
pretty slow -- which is to say that the image display takes more than a
c
10 matches
Mail list logo
