I did take a look at it. It looked way heavier than I needed or wanted, plus
last time I looked it didn't support fancy indexing on axes... It does support
indexing on 'ticks' though.
There is a bit of wheel inventing going on, but I think that's OK, since things
should be well worked out an
> along the axis, axis direction, cell vs.node centering, etc.) Subclassing
>> ndarray to hold onto this info is fairly simple, but getting numpy's methods
>> to intelligently modify that information when the array is sliced is
>> something that I'm still trying to figure out
ven ndarray, whether it just be
> a label or some more complex structure, would definitely be something I (and
> likely others) would find useful...
>
> That said, I'd love to know more about how the idx_axes() structure in your
> workaround works...
>
> - Sam
>
: Tue, 12 Jul 2011 16:39:47 -0700
> From: Craig Yoshioka
> Subject: [Numpy-discussion] named ndarray axes
> To: NumPy-Discussion@scipy.org
> Message-ID: <0fc8b43e-26cd-40ed-a6fa-59dd8d641...@me.com>
> Content-Type: text/plain; CHARSET=US-ASCII
>
> I brought up a while ago a
I brought up a while ago about how it would be nice if numpy arrays could have
their axes 'labeled'.= I got an implementation that works pretty well for
me and in the process learned quite a few things, and was hoping to foster some
more discussion on this topic, as I think I have found a si
