Mailman 3 June 2009 - SciPy-Dev

Mainly for the numpy doc wiki developers
by David Goldsmith June 10, 2009

June 10, 2009

How hard would it be to add a ticket system to the Wiki? DG

2 1

Re: [SciPy-dev] tanh(j*pi/2)
by David Goldsmith June 10, 2009

June 10, 2009

--- On Tue, 6/9/09, Robert Kern <robert.kern(a)gmail.com> wrote: > > I should probably 'Note' this tanh's doc (and other > transcendentals that may exhibit this behavior). > > <shrug> It's generic to all floating point > implementations of > transcendentals. I'd prefer not to clutter up each ufunc's > docs. A > section in the User's Guide about floating point arithmetic > in general > might be worthwhile, though. With a list of numpy-furnished functions to which the "problem" applies. (It's one thing to explain the phenomenon in general, and once this is done the "pedestrian" user may then be alert to the danger in source code, but still forget, or simply not realize, that it applies to library functions as well. Put another way, though one will certainly recognize that their own numerics will be subject to this, they might still expect that standard, furnished mathematical functions will have been written to be more "robust" w/ respect to their exact mathematical properties. I certainly wouldn't have _expected_ this problem w/ good old regular tan - my default assumption would be that N.tan(N.pi/2) would return N.inf or N.nan, not: >>> N.tan(N.pi/2) 16331778728383844.0) :-) DG

2 1

Re: [SciPy-dev] tanh(j*pi/2)
by David Goldsmith June 10, 2009

June 10, 2009

Understood, thanks. Just curious: can N.allclose be used w/ N.inf, or does one need to reciprocate first? DG --- On Tue, 6/9/09, Robert Kern <robert.kern(a)gmail.com> wrote: > From: Robert Kern <robert.kern(a)gmail.com> > Subject: Re: [SciPy-dev] tanh(j*pi/2) > To: d_l_goldsmith(a)yahoo.com, "SciPy Developers List" <scipy-dev(a)scipy.org> > Date: Tuesday, June 9, 2009, 9:56 PM > On Tue, Jun 9, 2009 at 23:51, <d_l_goldsmith(a)yahoo.com> > wrote: > > > >>>> import numpy as N > >>>> N.tanh(N.pi*1j/2) > > 16331778728383844j > > > > Is this the desired behavior? > > It's what floating point arithmetic gives us. N.pi/2 is not > precisely > the real number pi/2 so cos(N.pi/2) is not precisely 0 so > 2/cos(N.pi/2) is not inf or nan. > > -- > Robert Kern > > "I have come to believe that the whole world is an enigma, > a harmless > enigma that is made terrible by our own mad attempt to > interpret it as > though it had an underlying truth." > -- Umberto Eco >

2 1

tanh(j*pi/2)
by d_l_goldsmith＠yahoo.com June 10, 2009

June 10, 2009

>>> import numpy as N >>> N.tanh(N.pi*1j/2) 16331778728383844j Is this the desired behavior? (I.e., why doesn't this return N.inf or N.nan?) DG

2 1

New colors
by David Goldsmith June 9, 2009

June 9, 2009

--- On Tue, 6/9/09, David Goldsmith <d_l_goldsmith(a)yahoo.com> wrote: > --- On Tue, 6/9/09, Bruce Southey <bsouthey(a)gmail.com> > wrote: > > Can you provide the actual colors at the start for : > > * Edit white, light gray, or yellow > > * Don't edit dark gray > > While not color-blind, not all browsers render the > same > > colors on all > > operating systems etc. > > What are you using for light gray or is that meant to > be > > blue. If it is > > 'blue' then what does it mean? > > It appears to be the same color used on the Front Page > to > > say 'Proofed'. > > Yes, by all means, I agree 100% (I'm having the same > problem). :-) In fact, I think (and have thought) that > the light and dark grey and cyan are all too close to each > other - anyone object to me replacing the greys w/ orange > and lavender? Duh, I just realized this too has to be done at the Wiki code level - Wiki Devs? Please? Thanks! DG

1 0

Re: [SciPy-dev] More on Summer NumPy Doc Marathon
by David Goldsmith June 9, 2009

June 9, 2009

Thanks, Ralf. --- On Tue, 6/9/09, Ralf Gommers <ralf.gommers(a)googlemail.com> wrote: > Of this list of categories, there are 14 that are either > completely done or have only one docstring in white / > light-gray. So it is a less intimidating than it looks:) And > I like the size of the categories, many of them are small > enough that you can finish them in a weekend. Yup, sorry I didn't do better QC in this regard before sending this out. > I don't know if there's a need to prioritize, but I > would ask people with in-depth knowledge of numpy to pick > some of the ones that require that knowledge. Some of these Thank _you_ for asking! ;-) DG > are (basically, stuff towards the bottom of the page): > > Numpy internals > Ufuncs > Dtypes > Numarray compatibility > > Numeric compatibility > > Other array subclasses > Scalar base class > > Scalar types > > Cheers, > Ralf > > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Scipy-dev mailing list > Scipy-dev(a)scipy.org > http://mail.scipy.org/mailman/listinfo/scipy-dev >

2 1

Re: [SciPy-dev] More on Summer NumPy Doc Marathon
by David Goldsmith June 9, 2009

June 9, 2009

Thanks, Stefan. The lists you suggest already exist (more or less, depending on the "thing," i.e., list of categories, completely, prioritized list of individual items, sort of, at least w/in the categories) on the Milestones page (that's essentially what the Milestones page is) and the list of individual items is far too long to duplicate here, but for everyone's convenience I'll provide the list of categories (at least those for which the goal has not been, or is not close to being, met, which is most of them): Data type investigation Fourier transforms Linear algebra Error handling Financial functions Functional operations Help routines Indexing Input/Output Logic, comparisons etc. Polynomials Random number generation Other random operations Boolean set operations Searching Sorting Statistics Comparison Window functions Sums, interpolation, gradients, etc Arithmetic + basic functions I Arithmetic + basic functions II Arithmetic + basic functions III Masked arrays Masked arrays, II Masked arrays, III Masked arrays, IV Operations on masks Even more MA functions I Even more MA functions II Numpy internals C-types Other math The matrix library Numarray compatibility Numeric compatibility Other array subclasses Matrix subclass Ndarray Ndarray, II Dtypes Ufunc Scalar base class Scalar types Comments: 0) The number of individual items in each of these categories varies from one to a few dozen or so 1) Omitted are a few "meta-categories," e.g., "Routines," "Basic Objects," etc. 2) IMO, there are still too many of these (at least too many to not be intimidating in the manner Stefan has implied); I had it in mind to try to create an intermediate level of organization, i.e., "meso-categories," but I couldn't really justify it on grounds other than there are simply still too many categories to be unintimidating, so I was advised against usage of time in that endeavor. However, if there's an outpouring of support for me doing that, it would fall on sympathetic ears. As far as prioritizing individual items, my opinion is that team leads should do that (or not, as they deem appropriate) - I wouldn't presume to know enough to do that in most cases. However, if people want to furnish me with suggested prioritizations, I'd be happy to be the one to edit the Wiki to reflect these. DG --- On Tue, 6/9/09, Stéfan van der Walt <stefan(a)sun.ac.za> wrote: > From: Stéfan van der Walt <stefan(a)sun.ac.za> > Subject: Re: [SciPy-dev] More on Summer NumPy Doc Marathon > To: "SciPy Developers List" <scipy-dev(a)scipy.org> > Date: Tuesday, June 9, 2009, 1:34 AM > Hi David > > 2009/6/9 David Goldsmith <d_l_goldsmith(a)yahoo.com>: > > > > Hi again, folks. I have a special request. Part of > the vision for my job is that I'll focus my writing efforts > on the docs no one else is gung-ho to work on. So, even if > you're not quite ready to commit, if you're leaning toward > volunteering to be a team lead for one (or more) categories, > please let me know which one(s) (off list, if you prefer) so > I can get an initial idea of what the "leftovers" are going > to be. Thanks! > > That's a pretty wide question. Maybe you could post a > list of > categories and ask who would be willing to mentor and write > on each? > For the writing, we could decide on a prioritised list of > functions, > publish that list and then document those entries one by > one (i.e. > make the tasks small enough so that people don't run away > screaming). > > Cheers > Stéfan > _______________________________________________ > Scipy-dev mailing list > Scipy-dev(a)scipy.org > http://mail.scipy.org/mailman/listinfo/scipy-dev >

2 1

Re: [SciPy-dev] More on Summer NumPy Doc Marathon
by David Goldsmith June 9, 2009

June 9, 2009

Thanks, Bruce. --- On Tue, 6/9/09, Bruce Southey <bsouthey(a)gmail.com> wrote: > Hi, > Great. > Can you provide the actual colors at the start for : > * Edit white, light gray, or yellow > * Don't edit dark gray > While not color-blind, not all browsers render the same > colors on all > operating systems etc. > What are you using for light gray or is that meant to be > blue. If it is > 'blue' then what does it mean? > It appears to be the same color used on the Front Page to > say 'Proofed'. Yes, by all means, I agree 100% (I'm having the same problem). :-) In fact, I think (and have thought) that the light and dark grey and cyan are all too close to each other - anyone object to me replacing the greys w/ orange and lavender? > What does the 'green' color mean? > The links says 'Reviewed (needs proof)' but how does > one say 'proofed'. Cyan (if I understand you correctly). > Also the milestone link from the Front Page does not go > anywhere: > http://docs.scipy.org/numpy/Front%20Page/#milestones Ooops, accidentally broke that editing the page to make the Milestones link more prominent - I'll fix it imminently. Thanks again, DG > > Bruce > > > > _______________________________________________ > Scipy-dev mailing list > Scipy-dev(a)scipy.org > http://mail.scipy.org/mailman/listinfo/scipy-dev >

2 1

Re: [SciPy-dev] More on Summer NumPy Doc Marathon
by David Goldsmith June 9, 2009

June 9, 2009

> Also the milestone link from the Front Page does not go > anywhere: > http://docs.scipy.org/numpy/Front%20Page/#milestones Fixed. DG

1 0

More on Summer NumPy Doc Marathon
by David Goldsmith June 9, 2009

June 9, 2009

Hi again, folks. I have a special request. Part of the vision for my job is that I'll focus my writing efforts on the docs no one else is gung-ho to work on. So, even if you're not quite ready to commit, if you're leaning toward volunteering to be a team lead for one (or more) categories, please let me know which one(s) (off list, if you prefer) so I can get an initial idea of what the "leftovers" are going to be. Thanks! DG

4 4