[Numpy-discussion] NumPy Glossary: a request for review
zpincus at stanford.edu
Fri Feb 10 22:41:01 CST 2006
The "broadcasting" entry is somewhat unclear in terms of what
"conforming" array shapes are. Perhaps "compatible shapes" would be
better, coupled with an example or two of "compatible" shapes, and/or
a precise definition of how compatibility is determined.
Program in Biomedical Informatics and Department of Biochemistry
Stanford University School of Medicine
On Feb 10, 2006, at 9:55 PM, Gary Ruben wrote:
> David Cooke corrected my misconceptions, so the glossary all looks
> good to me.
> Gary R.
> Sasha wrote:
>> On 2/11/06, Gary Ruben <gruben at bigpond.net.au> wrote:
>>> Stride isn't the distance in bytes is it? Isn't it just the index
>>> increment or alternatively the distance in terms of the
>>> multiplier of
>>> the word length of the contained type.
>> Unfortunately it is in bytes and Travis convinced me that there is no
>> way to change it.
>>> Also, a slight typo: concecutive -> consecutive.
>> I've changed that. In the future, please just edit the wiki for
>> obvious misspellings. Spell check does not work for me on that wiki
>> and English is not my first language, so any spelling/grammar
>> corrections are more than welcome.
>>> A composite element of an array similar to C struct.
>>> This implies that you can contain different types in a record,
>>> which I
>>> think is only true if you have an object array.
>> Record arrays is a new feature in numpy. I think what I wrote is
>> correct, but this entry will definitely benefit from a review by
>> someone familiar with record arrays since I am not.
> This SF.net email is sponsored by: Splunk Inc. Do you grep through
> log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD
> Numpy-discussion mailing list
> Numpy-discussion at lists.sourceforge.net
More information about the Numpy-discussion