Mailman 3 July 2009 - SciPy-Dev

ANN: SciPy 2009 early registration ends today
by Jarrod Millman July 22, 2009

July 22, 2009

Today is the last day to register for SciPy 2009 at the early bird rates. Please register (http://conference.scipy.org/to_register ) by the end of the day to take advantage of the reduced early registration rate. The conference schedule is available here: http://conference.scipy.org/schedule The special group rate for the Marriot Hotel is no longer available. However, there are a number of closer and less expensive choices still available: http://admissions.caltech.edu/visiting/accommodations I've been staying at the Vagabond Inn for the last several years: http://www.vagabondinn-pasadena-hotel.com/ It is within easy walking distance of the conference and has just been completely renovated. Rooms at the Vagabond start at $79/night. About the conference -------------------- SciPy 2009, the 8th Python in Science conference, will be held from August 18-23, 2009 at Caltech in Pasadena, CA, USA. The conference starts with two days of tutorials to the scientific Python tools. There will be two tracks, one for introduction of the basic tools to beginners, and one for more advanced tools. The tutorials will be followed by two days of talks. Both days of talks will begin with a keynote address. The first day’s keynote will be given by Peter Norvig, the Director of Research at Google; while, the second keynote will be delivered by Jon Guyer, a Materials Scientist in the Thermodynamics and Kinetics Group at NIST. The program committee will select the remaining talks from submissions to our call for papers. All selected talks will be included in our conference proceedings edited by the program committee. After the talks each day we will provide several rooms for impromptu birds of a feather discussions. Finally, the last two days of the conference will be used for a number of coding sprints on the major software projects in our community. For the 8th consecutive year, the conference will bring together the developers and users of the open source software stack for scientific computing with Python. Attendees have the opportunity to review the available tools and how they apply to specific problems. By providing a forum for developers to share their Python expertise with the wider commercial, academic, and research communities, this conference fosters collaboration and facilitates the sharing of software components, techniques, and a vision for high level language use in scientific computing. For further information, please visit the conference homepage: http://conference.scipy.org. Important Dates --------------- * Friday, July 3: Abstracts Due * Wednesday, July 15: Announce accepted talks, post schedule * Wednesday, July 22: Early Registration ends * Tuesday-Wednesday, August 18-19: Tutorials * Thursday-Friday, August 20-21: Conference * Saturday-Sunday, August 22-23: Sprints * Friday, September 4: Papers for proceedings due Executive Committee ------------------- * Jarrod Millman, UC Berkeley, USA (Conference Chair) * Gaël Varoquaux, INRIA Saclay, France (Program Co-Chair) * Stéfan van der Walt, University of Stellenbosch, South Africa (Program Co-Chair) * Fernando Pérez, UC Berkeley, USA (Tutorial Chair)

1 0

'nuther Goal Met!
by David Goldsmith July 22, 2009

July 22, 2009

dtypes (ufuncs is almost done, but I have a question on how to document the class itself; see discussion there, or Wiki Q & A page). DG

1 0

Reminder: Numpy Doc Summer Marathon Skypecon
by David Goldsmith July 21, 2009

July 21, 2009

Tomorrow (Wednesday, July 22) 19:00 UTC. Please email me agenda items. RSVP appreciated but not necessary. Look forward to talking to you... DG

1 0

spam on wiki
by Darren Dale July 21, 2009

July 21, 2009

How can we remove spam from the wiki? http://www.scipy.org/hosetubingcompany Darren

2 1

ANN: SfePy 2009.3
by Robert Cimrman July 21, 2009

July 21, 2009

I am pleased to announce release 2009.3 of SfePy. Description ----------- SfePy (simple finite elements in Python) is a software, distributed under the BSD license, for solving systems of coupled partial differential equations by the finite element method. The code is based on NumPy and SciPy packages. Mailing lists, issue tracking, git repository: http://sfepy.org Home page: http://sfepy.kme.zcu.cz Highlights of this release -------------------------- Finally, SfePy has a basic support for Windows installation via numpy distutils: - still very experimental! - the tests will not finish if umfpack is not installed, as the default direct solver in scipy cannot handle some problems (see recent sfepy-devel mailing list discussions). Major improvements ------------------ - new scripts: - cylindergen.py: cylindrical mesh generator - updated scripts: - postproc.py: - quite usable now for fast first glance at the results - plots point, cell data of all kinds (scalar, vector, tensor) - Viewer is much more configurable - probe.py: - can probe selected quantities only - isfepy: - Viewer is much more configurable - new tests and terms Applications ------------ - phononic materials: - plotting improved - caching of eigen-problem solution and Christoffel acoustic tensor - schroedinger.py: - choose and call DFT solver via solver interface People who contributed to this release: Vladimir Lukes. For more information on this release, see http://sfepy.googlecode.com/svn/web/releases/2009.3_RELEASE_NOTES.txt Best regards, Robert Cimrman

1 0

Re: [SciPy-dev] ufunc.accumulate bug?
by David Goldsmith July 19, 2009

July 19, 2009

Yup, that was it, thanks again! DG --- On Sun, 7/19/09, Charles R Harris <charlesr.harris(a)gmail.com> wrote: > David Goldsmith <d_l_goldsmith(a)yahoo.com> > wrote: > > Hi! Is this a bug: > > >>> np.multiply.accumulate([2, 3, 5], > dtype='g') > > array([0.0, -2, -3.1050362e+231], dtype=float96) > > >>> np.multiply.accumulate([2, 3, 5], > dtype='G') > > array([0.0+0.0j, -2+0.0j, -3.1050362e+231+0.0j], > dtype=complex192) > > On the other hand, this works for me. What numpy version do > you have? There was a bug like this that got fixed in 1.2. > > Chuck

1 0

Re: [SciPy-dev] ufunc.accumulate bug?
by David Goldsmith July 19, 2009

July 19, 2009

Ah, that would (probably) be it then: >>> np.version.version '1.2.1' I'll update and see... Thanks, Charles! DG --- On Sun, 7/19/09, Charles R Harris <charlesr.harris(a)gmail.com> wrote: > From: Charles R Harris <charlesr.harris(a)gmail.com> > Subject: Re: [SciPy-dev] ufunc.accumulate bug? > To: "SciPy Developers List" <scipy-dev(a)scipy.org> > Date: Sunday, July 19, 2009, 2:55 PM > > > On Sun, Jul 19, 2009 at 3:28 PM, > David Goldsmith <d_l_goldsmith(a)yahoo.com> > wrote: > > > > Hi! Is this a bug: > > > > >>> np.multiply.accumulate([2, 3, 5], > dtype='f') > > array([ 2., 6., 30.], dtype=float32) > > > > >>> np.multiply.accumulate([2, 3, 5], > dtype='g') > > array([0.0, -2, -3.1050362e+231], dtype=float96) > > > > >>> np.multiply.accumulate([2, 3, 5], > dtype='F') > > array([ 2.+0.j, 6.+0.j, 30.+0.j], dtype=complex64) > > > > >>> np.multiply.accumulate([2, 3, 5], > dtype='G') > > array([0.0+0.0j, -2+0.0j, -3.1050362e+231+0.0j], > dtype=complex192) > > > > If not, why not (i.e., what am I missing)? > > > On the other hand, this works for me. What numpy version do > you have? There was a bug like this that got fixed in 1.2. > > Chuck > > > > > -----Inline Attachment Follows----- > > _______________________________________________ > Scipy-dev mailing list > Scipy-dev(a)scipy.org > http://mail.scipy.org/mailman/listinfo/scipy-dev >

1 0

Porting SciPy to Py3k GSOC project
by ross smith July 19, 2009

July 19, 2009

Hello everyone, I am interested in porting SciPy/NumPy to Py3k. I've been working this past school year to port an existing code base to py3k for a research group on campus. A lot of the code relies on SciPy and NumPy but the scope of my project didn't let me work on porting either project, to my dismay. I'd love the opportunity to port a project I use heavily in my own code and gain a better understanding of how it works. We are supposed to contact the group we would be working with, to flesh out the details of our application. I've looked at the application and the only thing I know I'll need significant help with is the Milestones portion. Of course, Any and all suggestions are welcome! thank you, Ross Smith (Gaurdro on Freenode)

2 3

ufunc.accumulate bug?
by David Goldsmith July 19, 2009

July 19, 2009

Hi! Is this a bug: >>> np.multiply.accumulate([2, 3, 5], dtype='f') array([ 2., 6., 30.], dtype=float32) >>> np.multiply.accumulate([2, 3, 5], dtype='g') array([0.0, -2, -3.1050362e+231], dtype=float96) >>> np.multiply.accumulate([2, 3, 5], dtype='F') array([ 2.+0.j, 6.+0.j, 30.+0.j], dtype=complex64) >>> np.multiply.accumulate([2, 3, 5], dtype='G') array([0.0+0.0j, -2+0.0j, -3.1050362e+231+0.0j], dtype=complex192) If not, why not (i.e., what am I missing)? DG

2 2

Re: [SciPy-dev] bool8 link returns bool_ docstring
by David Goldsmith July 18, 2009

July 18, 2009

Once again I believe I've answered my own question (I need to have more faith in my research abilities and not cry for help so quickly): Figure 2.2 in "Guide To Numpy" illustrating the hierarchy of scalar types - the names used there are the "base" names, any equivalent is considered an "alias," yes? Oh, but this doesn't answer my first question: is the fact that the Wiki returns the same docstring for equivalent types a bug or a feature? (At this point I'm assuming "feature," but confirmation would be appreciated.) Thanks, DG --- On Wed, 7/15/09, David Goldsmith <d_l_goldsmith(a)yahoo.com> wrote: > From: David Goldsmith <d_l_goldsmith(a)yahoo.com> > Subject: bool8 link returns bool_ docstring > To: scipy-dev(a)scipy.org > Date: Wednesday, July 15, 2009, 4:09 PM > Hi! So, now I'm working on the > Scalar Types category; perhaps this is "old news," but when > I click on the link for bool8, I get the docstring for > bool_; similarly for other types (e.g., cfloat and > complex128 both return the docstring for complex128). > Is this a "bug" or a "feature"? If the latter, may I > assume that if link_type_A and link_type_B both return the > docstring for type_A, then type_A is the "base" and type_B > is the "alias"? Thanks! > > DG > > > >

4 3