Mailman 3 July 2004 - SciPy-Dev

Conference Schedule Online
by Travis Oliphant July 30, 2004

July 30, 2004

The preliminary conference schedule for SciPy2004 is now online. You can view it at: http://www.scipy.org/wikis/scipy04/ConferenceSchedule See you in Pasadena, -Travis Oliphant

1 0

crash
by Olivier Ravard July 27, 2004

July 27, 2004

Hi everybody, I work on windows XP, python 2.3, scipy 0.3 and Numeric 23.1. The folowing code crash python (without returned error message) : import scipy a=scipy.arange(258168,typecode='F') c=a*a but the two folowing code does not make a crash : import scipy a=scipy.arange(258167,typecode='F') c=a*a import Numeric a=scipy.arange(258168,typecode='F') c=a*a import Numeric a=scipy.arange(10000000,typecode='F') c=a*a I think this is a bug from scipy but how to solve it ? I thaught that scipy use Numeric.array, does not ? can we compile scipy without using LAPACK to test those simple codes ? Thanks. O.R.

2 1

ANN: SciPy04 -- Last day for abstracts and early registration!
by eric jones July 23, 2004

July 23, 2004

Hey Group, Just a reminder that this is the last day to submit abstracts for SciPy04. It is also the last day for early registration. More information is here: http://www.scipy.org/wikis/scipy04 About the Conference and Keynote Speaker --------------------------------------------- The 1st annual *SciPy Conference* will be held this year at Caltech, September 2-3, 2004. As some of you may know, we've experienced great participation in two SciPy "Workshops" (with ~70 attendees in both 2002 and 2003) and this year we're graduating to a "conference." With the prestige of a conference comes the responsibility of a keynote address. This year, Jim Hugunin has answered the call and will be speaking to kickoff the meeting on Thursday September 2nd. Jim is the creator of Numeric Python, Jython, and co-designer of AspectJ. Jim is currently working on IronPython--a fast implementation of Python for .NET and Mono. Presenters ----------- We still have room for a few more standard talks, and there is plenty of room for lightning talks. Because of this, we are extending the abstract deadline until July 23rd. Please send your abstract to abstracts(a)scipy.org. Travis Oliphant is organizing the presentations this year. (Thanks!) Once accepted, papers and/or presentation slides are acceptable and are due by August 20, 2004. Registration ------------- Early registration ($100.00) has been extended to July 23rd. Follow the links off of the main conference site: http://www.scipy.org/wikis/scipy04 After July 23rd, registration will be $150.00. Registration includes breakfast and lunch Thursday & Friday and a very nice dinner Thursday night. Please register as soon as possible as it will help us in planning for food, room sizes, etc. Sprints -------- As of now, we really haven't had much of a call for coding sprints for the 3 days prior to SciPy 04. Below is the original announcement about sprints. If you would like to suggest a topic and see if others are interested, please send a message to the list. Otherwise, we'll forgo the sprints session this year. We're also planning three days of informal "Coding Sprints" prior to the conference -- August 30 to September 1, 2004. Conference registration is not required to participate in the sprints. Please email the list, however, if you plan to attend. Topics for these sprints will be determined via the mailing lists as well, so please submit any suggestions for topics to the scipy-user list: list signup: http://www.scipy.org/mailinglists/ list address: scipy-user(a)scipy.org thanks, eric

1 0

[SPAM] ***UNCHECKED*** RE: Message Notify
by Pearu July 22, 2004

July 22, 2004

1 0

Bugs in scipy.optimize
by Ed Schofield July 21, 2004

July 21, 2004

Hi all, I've uncovered one bug and two "buglets" in scipy.optimize v0.3 ---- BUG 1 ---- Arguments passed as 'args' to fmin_powell() get mangled. The following code illustrates the problem: from Numeric import array from scipy import optimize params = array([3.0, 6.0]) def f(x,params): return (x-params[0])**2 x0 = 0.0 result1 = optimize.fmin(f, x0, args=(params,)) result2 = optimize.fmin_cg(f, x0, args=(params,)) result3 = optimize.fmin_bfgs(f, x0, args=(params,)) result4 = optimize.fmin_powell(f, x0, args=(params,)) The first three routines work without error. The fmin_powell function throws an exception: File ".../optimize/optimize.py", line 1389, in _myfunc return func(*funcargs) TypeError: f() takes exactly 2 arguments (1 given) The argument tuple is unpacked incorrectly. I suggest changing the line in _linesearch_powell() in optimize.py from: extra_args = (func, p, xi) + args to extra_args = (func, p, xi) + (args,) This seems to work. Otherwise a star operator (*args) in the right place might do the job. ---- BUG 2 ---- The output of the fmin() ("result1" above) is a scalar >>> result1 3.0000000000000031 whereas the other outputs result2, result3, and (when it works) result4 are Numeric arrays: >>> result2 array([ 3.]) These ought to be consistent. ---- BUG 3 ---- A line in the docstring comment for fmin_powell() is wrong. Instead of reading: Outputs: (xopt, {fopt, xi, direc, iter, funcalls, warnflag}, {allvecs}) it should read: Outputs: (xopt, {fopt, direc, iter, funcalls, warnflag}, {allvecs}) (No xi parameter is returned.) Best wishes, Ed Schofield

1 0

stats - kstest
by Manuel Metz July 20, 2004

July 20, 2004

Hi, hopefully I'm at the right place to manifest my suggestion. As far as I understand the "kstest" from the book "Numerical recipes in C++" (Chapt. 14.3, Kolmogorov-Smirnov Test) the kstest algorithm is not correctly implementet in SciPy. (or NR ?) I think the error is in the second last line of kstest(): >>> D = max(abs(cdfvals - sb.arange(1.0,N+1)/N)) In comparison from NR: >>> double en = data.size() >>> for( j=0; j<n; j++) { >>> fn = (j+1)/en; >>> ff = func( data[j] ); >>> dt = max( fabs(fo-ff), fabs(fn-ff) >>> if (dt > d) d=dt; >>> fo = fn; >>> } So the main difference is, that in the NR algorithm the "D" is calculated as the maximum distance D = max |S_N(x) - P(x)| by calculating the distances to the upper AND the lower side of P(X) to the step function S_N(x), while in the SciPy routine only the distance to the upper side is calculated. Is my suggestion right, that the error is in the SciPy algorithm? If yes, could anyone correct it with the next release of SciPy? Manuel

3 4

Encrypted document
by Pearu July 17, 2004

July 17, 2004

1 0

ANN: Reminder -- SciPy 04 is coming up
by eric jones July 14, 2004

July 14, 2004

Hey folks, Just a reminder that SciPy 04 is coming up. More information is here: http://www.scipy.org/wikis/scipy04 About the Conference and Keynote Speaker --------------------------------------------- The 1st annual *SciPy Conference* will be held this year at Caltech, September 2-3, 2004. As some of you may know, we've experienced great participation in two SciPy "Workshops" (with ~70 attendees in both 2002 and 2003) and this year we're graduating to a "conference." With the prestige of a conference comes the responsibility of a keynote address. This year, Jim Hugunin has answered the call and will be speaking to kickoff the meeting on Thursday September 2nd. Jim is the creator of Numeric Python, Jython, and co-designer of AspectJ. Jim is currently working on IronPython--a fast implementation of Python for .NET and Mono. Presenters ----------- We still have room for a few more standard talks, and there is plenty of room for lightning talks. Because of this, we are extending the abstract deadline until July 23rd. Please send your abstract to abstracts(a)scipy.org. Travis Oliphant is organizing the presentations this year. (Thanks!) Once accepted, papers and/or presentation slides are acceptable and are due by August 20, 2004. Registration ------------- Early registration ($100.00) has been extended to July 23rd. Follow the links off of the main conference site: http://www.scipy.org/wikis/scipy04 After July 23rd, registration will be $150.00. Registration includes breakfast and lunch Thursday & Friday and a very nice dinner Thursday night. Please register as soon as possible as it will help us in planning for food, room sizes, etc. Sprints -------- As of now, we really haven't had much of a call for coding sprints for the 3 days prior to SciPy 04. Below is the original announcement about sprints. If you would like to suggest a topic and see if others are interested, please send a message to the list. Otherwise, we'll forgo the sprints session this year. We're also planning three days of informal "Coding Sprints" prior to the conference -- August 30 to September 1, 2004. Conference registration is not required to participate in the sprints. Please email the list, however, if you plan to attend. Topics for these sprints will be determined via the mailing lists as well, so please submit any suggestions for topics to the scipy-user list: list signup: http://www.scipy.org/mailinglists/ list address: scipy-user(a)scipy.org thanks, eric

1 0