Dear experts,
Is it possible to sample a 4D array of numpy at given dimensions
with out writing loops? ie a smart python way?
for example,
I have a data cube with cube=c(x,y,z,t) dimensions which are essentially
latitude longitude depth and time. Is it possible to sample this
On Sun, 2013-06-16 at 14:48 +0800, Sudheer Joseph wrote:
Is it possible to sample a 4D array of numpy at given dimensions with
out writing loops? ie a smart python way?
It's not clear how what you want to do is different from simply indexing
the array...?
Henry
Thank you,
No if the location ( space time or depth) of choice is not
available then the function I was looking for should give an interpolated value
at the choice.
with best regards,
Sudheer
- Original Message -
From: Henry Gomersall h...@cantab.net
To: Discussion
Here is a solution I got.
I think I need to do the rest with loop. Though I am seeing an interpnd I could
not find a documentation on that or example.
http://docs.scipy.org/doc/scipy/reference/generated/scipy.interpolate.RectBivariateSpline.html#scipy.interpolate.RectBivariateSpline
Thank you
With Python 3.3.2 (64 bit), and numpy master:
import numpy as np
np.__version__
'1.8.0.dev-2a5c2c8'
f = np.float64(1.0)
i = 2**65
f*i
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: unsupported operand type(s) for *: 'numpy.float64' and 'int'
Is this the
On Sun, Jun 16, 2013 at 12:56 PM, Warren Weckesser
warren.weckes...@gmail.com wrote:
With Python 3.3.2 (64 bit), and numpy master:
import numpy as np
np.__version__
'1.8.0.dev-2a5c2c8'
f = np.float64(1.0)
i = 2**65
f*i
Traceback (most recent call last):
File stdin, line 1, in
Hi!
I know it is pretty much the same as you did before, but has been useful
for me in the past. Instead of saving each array separately, just create a
dictionary and save the it, something like
d= {put_all_your_arrays_here}
savez_compressed('file.npz', **d)
-- Camilo Jiménez
On Sat, Jun 15,
What is the preferred strategy for handling bug fix PRs? Initial fix on
master, and then a separate PR to backport to v1.7.x? Or the reverse?
It doesn't look like v1.7.x is being merged into master regularly, so
the matplotlib pattern (fix on maintenance, merge maintenance into
master) seems
On Sun, Jun 16, 2013 at 10:57 PM, Eric Firing efir...@hawaii.edu wrote:
What is the preferred strategy for handling bug fix PRs? Initial fix on
master, and then a separate PR to backport to v1.7.x? Or the reverse?
It doesn't look like v1.7.x is being merged into master regularly, so
the
Github issues 611, 629, and 2490 are duplicates. 611 included patches
with a test and a fix, both of which were committed long ago, so all
three issues should be closed.
Please see my comment on 2264 as to why that should be closed.
On 1417, please remove the component:numpy.ma label and add
On Sun, Jun 16, 2013 at 6:40 PM, Eric Firing efir...@hawaii.edu wrote:
Github issues 611, 629, and 2490 are duplicates. 611 included patches
with a test and a fix, both of which were committed long ago, so all
three issues should be closed.
Please see my comment on 2264 as to why that
11 matches
Mail list logo
