From tjlahey at mud.cgl.uwaterloo.ca Wed Aug 1 19:09:41 2001 From: tjlahey at mud.cgl.uwaterloo.ca (Tim Lahey) Date: Wed, 1 Aug 2001 19:09:41 -0400 Subject: [SciPy-dev] Splines in SciPy Message-ID: <20010801231139.YWP4521.tomts13-srv.bellnexxia.net@localhost> All, Getting the new version of SciPy from CVS I was happy to see the inclusion of splines support. However, it is split between interpolate and signal. I personally would prefer a separate splines module. Some of us use splines for neither of the above. I've been using B-splines as a basis for a finite element method. The SLATEC library on Netlib has an set of excellent spline codes based upon de Boor's code. The only problem is that it doesn't support 2-D. I've written a set of F90 wrappers around the code to support some stuff in 2-D and provide a more object-oriented api, but I don't need interpolation so, I've been ignoring that part. I've been planning a port to Python and I'd be happy to help in the development of the splines part of scipy. Thoughts? Cheers, Tim Lahey From eric at scipy.org Thu Aug 2 08:30:42 2001 From: eric at scipy.org (eric jones) Date: Thu, 2 Aug 2001 08:30:42 -0400 Subject: Fw: [SciPy-dev] Splines in SciPy Message-ID: <024e01c11b4e$f5510050$7600a8c0@ericlaptop> Hey Tim, I just noticed this addition too. Travis Oliphant is the man to talk to about this. I doubt he has thought to hard about its location in scipy and will be open to suggestion. Also, the SLATEC slant sounds promising. Can you work on it as a side project and we can integrate it into SciPy later. Right now we need to work the existing kinks out of the code and get a binary release out the door. (It should been out last week) One thing though -- no F90 code. Sorry, but its harder to wrap in Python and there aren't any OS compilers around that handle it yet (give th gnu folks another few years though...) F77 code is acceptable, but we smile bigger when handed C/C++ and Python. Then again, Travis O. might not smile at all if its C++... see ya, eric > > ----- Original Message ----- > From: "Tim Lahey" > To: > Sent: Wednesday, August 01, 2001 7:09 PM > Subject: [SciPy-dev] Splines in SciPy > > > > All, > > > > Getting the new version of SciPy from CVS I was happy to see the > > inclusion > > of splines support. However, it is split between interpolate and > > signal. I > > personally would prefer a separate splines module. Some of us use splines > > for neither of the above. I've been using B-splines as a basis for a > > finite > > element method. The SLATEC library on Netlib has an set of excellent > > spline codes based upon de Boor's code. The only problem is that it > > doesn't > > support 2-D. > > > > I've written a set of F90 wrappers around the code to support some stuff > > in 2-D and provide a more object-oriented api, but I don't need > > interpolation > > so, I've been ignoring that part. I've been planning a port to Python > > and I'd > > be happy to help in the development of the splines part of scipy. > > > > Thoughts? > > > > Cheers, > > > > Tim Lahey > > _______________________________________________ > > Scipy-dev mailing list > > Scipy-dev at scipy.net > > http://www.scipy.net/mailman/listinfo/scipy-dev > From oliphant at ee.byu.edu Thu Aug 2 17:55:24 2001 From: oliphant at ee.byu.edu (Travis Oliphant) Date: Thu, 2 Aug 2001 15:55:24 -0600 (MDT) Subject: [SciPy-dev] Spline module In-Reply-To: <200108021700.f72H03D17694@scipy.org> Message-ID: > > Getting the new version of SciPy from CVS I was happy to see the > inclusion > of splines support. However, it is split between interpolate and > signal. I > personally would prefer a separate splines module. Some of us use splines > for neither of the above. I've been using B-splines as a basis for a > finite > element method. The SLATEC library on Netlib has an set of excellent > spline codes based upon de Boor's code. The only problem is that it > doesn't > support 2-D. I'm not necessarily opposed to a separate splines module. But, splines do get used in a number of different ways --- and the algorithms used in each domain do tend to differ. Perhaps your spline code would be better in a finite-element package, rather than a spline module. > > I've written a set of F90 wrappers around the code to support some stuff > in 2-D and provide a more object-oriented api, but I don't need > interpolation > so, I've been ignoring that part. I've been planning a port to Python > and I'd > be happy to help in the development of the splines part of scipy. > > Thoughts? Love to have more help with scipy... > I just noticed this addition too. Travis Oliphant is the man to talk to > about this. I doubt he > has thought to hard about its location in scipy and will be open to > suggestion. Also, > the SLATEC slant sounds promising. Can you work on it as a side project and > we > can integrate it into SciPy later. Right now we need to work the existing > kinks out > of the code and get a binary release out the door. (It should been out last > week) > > One thing though -- no F90 code. Sorry, but its harder to wrap in Python > and there aren't > any OS compilers around that handle it yet (give th gnu folks another few > years though...) > F77 code is acceptable, but we smile bigger when handed C/C++ and Python. > Then again, Travis O. might not smile at all if its C++... > I don't mind f77 code (but then again I haven't dealt with the Windows headaches as much as eric :-) ). -Travis From eric at scipy.org Thu Aug 2 22:36:09 2001 From: eric at scipy.org (eric jones) Date: Thu, 2 Aug 2001 22:36:09 -0400 Subject: [SciPy-dev] Spline module References: Message-ID: <00e601c11bc5$0dbea630$c300a8c0@ericlaptop> I'm no splines expert, but I'd hope there was a way to factor out the splines code so that we only have one set of spline code to maintain. The smaller SciPy's code base the better. If different disciplines use splines in different ways, then they can put a different interface over the top of the splines module. If the disciplines use splines in ways that requires different underlying code, or if different implementations of splines are faster/better for different problem sets, then multiple libraries *might* be a good idea. It have to be a lot faster (2x) or a lot better to make the larger code base worth while though. eric ----- Original Message ----- From: "Travis Oliphant" To: Sent: Thursday, August 02, 2001 5:55 PM Subject: [SciPy-dev] Spline module > > > > > Getting the new version of SciPy from CVS I was happy to see the > > inclusion > > of splines support. However, it is split between interpolate and > > signal. I > > personally would prefer a separate splines module. Some of us use splines > > for neither of the above. I've been using B-splines as a basis for a > > finite > > element method. The SLATEC library on Netlib has an set of excellent > > spline codes based upon de Boor's code. The only problem is that it > > doesn't > > support 2-D. > > I'm not necessarily opposed to a separate splines module. But, splines do > get used in a number of different ways --- and the algorithms used in each > domain do tend to differ. > > Perhaps your spline code would be better in a finite-element package, > rather than a spline module. > > > > > I've written a set of F90 wrappers around the code to support some stuff > > in 2-D and provide a more object-oriented api, but I don't need > > interpolation > > so, I've been ignoring that part. I've been planning a port to Python > > and I'd > > be happy to help in the development of the splines part of scipy. > > > > Thoughts? > > Love to have more help with scipy... > > > I just noticed this addition too. Travis Oliphant is the man to talk to > > about this. I doubt he > > has thought to hard about its location in scipy and will be open to > > suggestion. Also, > > the SLATEC slant sounds promising. Can you work on it as a side project and > > we > > can integrate it into SciPy later. Right now we need to work the existing > > kinks out > > of the code and get a binary release out the door. (It should been out last > > week) > > > > > One thing though -- no F90 code. Sorry, but its harder to wrap in Python > > and there aren't > > any OS compilers around that handle it yet (give th gnu folks another few > > years though...) > > F77 code is acceptable, but we smile bigger when handed C/C++ and Python. > > Then again, Travis O. might not smile at all if its C++... > > > > I don't mind f77 code (but then again I haven't dealt with the Windows > headaches as much as eric :-) ). > > -Travis > > > _______________________________________________ > Scipy-dev mailing list > Scipy-dev at scipy.net > http://www.scipy.net/mailman/listinfo/scipy-dev From tjlahey at mud.cgl.uwaterloo.ca Fri Aug 3 14:56:28 2001 From: tjlahey at mud.cgl.uwaterloo.ca (Tim Lahey) Date: Fri, 3 Aug 2001 14:56:28 -0400 (EDT) Subject: [SciPy-dev] Re: Splines module In-Reply-To: <200108031700.f73H01D31118@scipy.org> from "scipy-dev-request@scipy.org" at Aug 03, 2001 12:00:01 PM Message-ID: <200108031856.OAA29753@mud.cgl.uwaterloo.ca> > > Date: Thu, 2 Aug 2001 15:55:24 -0600 (MDT) > From: Travis Oliphant > To: > Subject: [SciPy-dev] Spline module > > > I'm not necessarily opposed to a separate splines module. But, splines do > get used in a number of different ways --- and the algorithms used in each > domain do tend to differ. > > Perhaps your spline code would be better in a finite-element package, > rather than a spline module. > > Love to have more help with scipy... > > I don't mind f77 code (but then again I haven't dealt with the Windows > headaches as much as eric :-) ). > > -Travis Well, I base my code on some general B-spline code (written in F77) from the SLATEC library in Netlib. I only use less than a half dozen functions from the library, but it does include: BINT4 - interpolates with splines of order 4 BINTK - interpolates with splines of order k BSQAD - integrates the B-representation on subintervals PPQAD - integrates the PP-representation BFQAD - integrates the product of a function F and any spline derivative in the B-representation PFQAD - integrates the product of a function F and any spline derivative in the PP-representation BVALU - evaluates the B-representation or a derivative PPVAL - evaluates the PP-representation or a derivative INTRV - gets the largest index of the knot to the left of x BSPPP - converts from B- to PP-representation BSPVD - computes nonzero basis functions and derivatives at x BSPDR - sets up difference array for BSPEV BSPEV - evaluates the B-representation and derivatives BSPVN - called by BSPEV, BSPVD, BSPPP and BINTK for function and derivative evaluations where PP-representation is piecewise polynomial representation, and B-representation is B-spline representation. These are the basic functions the spline toolbox are based off of. From BSPVD one can get the tensor product B-spline form, which is what I do. There are some other routines in Carl de Boor, A Practical Guide to Splines, Applied Mathematics Series 27, Springer-Verlag, New York, 1978. for solving ODEs through co-location. The way I see things is that we can create a base spline module that includes the above functions (save BINT4 and BINTK) and have separate modules for: interpolation, solving ODEs through co-location, and my FEM code (possibly). Thoughts ? Cheers, Tim. From jmr at engineering.uiowa.edu Tue Aug 21 19:19:53 2001 From: jmr at engineering.uiowa.edu (Joe Reinhardt) Date: Tue, 21 Aug 2001 18:19:53 -0500 Subject: [SciPy-dev] RPMs and source distribution In-Reply-To: <87snfmn8o1.fsf@jeeves.blindglobe.net> (rossini@u.washington.edu's message of "23 Jul 2001 23:27:42 -0700") References: <87snfmn8o1.fsf@jeeves.blindglobe.net> Message-ID: <87u1z1j90m.fsf@phantom.ecn.uiowa.edu> Did this debian package ever materialize? As far as I know, there is no bdist_deb, but I have packaged other python packages using "python setup.py build" and dpkg-buildpackage with no trouble. I would be interested in working to get this packaged. Let me know if I can help. - Joe rossini at u.washington.edu (A.J. Rossini) writes: >>>>>> "TO" == Travis Oliphant writes: > > TO> I've been playing for hours and finally have it so that > > TO> python setup.py sdist python setup.by bdist_rpm > > TO> work as expected. > > TO> I have distributions and RPM's that I need to put somewhere. > > So distutils stuff works? > > And are there any plans for a debian package (more "if not, I'll work > at it", than an honest request). > > best, > -tony -- Joseph M. Reinhardt, Ph.D. Department of Biomedical Engineering joe-reinhardt at uiowa.edu University of Iowa, Iowa City, IA 52242 Telephone: 319-335-5634 FAX: 319-335-5631 From eric at scipy.org Tue Aug 21 18:44:15 2001 From: eric at scipy.org (eric jones) Date: Tue, 21 Aug 2001 18:44:15 -0400 Subject: [SciPy-dev] RPMs and source distribution References: <87snfmn8o1.fsf@jeeves.blindglobe.net> <87u1z1j90m.fsf@phantom.ecn.uiowa.edu> Message-ID: <005101c12a92$ce8e2b20$ec88fea9@ericlaptop> Hey Joe, Debian packages would be good. You can definitely help with this. If you get the package built, send it to me, and we'll stick it on scipy.org. Also, can you supply a short description of you to install the package on Debian? Or, another option is for you to put it on your scipy.org member page. This would make it easier for you to maintain until it becomes a part of an automated build process. We can put a link from the download page to your member page. Also, I haven't used Debian and so am not familiar with its packaging (other than everyone acknowledges that its very slick). Can the dpkg-buildpackage stuff be installed and run a on a RH box, or does it require a Debain machine? If it can be done on a RH box and you can provide the scripts to produce the packages, we'll try and set it up so that it is built automatically on our system for the next release. thanks, eric ----- Original Message ----- From: "Joe Reinhardt" To: ; "A.J. Rossini" Sent: Tuesday, August 21, 2001 7:19 PM Subject: Re: [SciPy-dev] RPMs and source distribution > > Did this debian package ever materialize? > > As far as I know, there is no bdist_deb, but I have packaged other > python packages using "python setup.py build" and dpkg-buildpackage > with no trouble. > > I would be interested in working to get this packaged. Let me know if > I can help. > > - Joe > > > rossini at u.washington.edu (A.J. Rossini) writes: > > >>>>>> "TO" == Travis Oliphant writes: > > > > TO> I've been playing for hours and finally have it so that > > > > TO> python setup.py sdist python setup.by bdist_rpm > > > > TO> work as expected. > > > > TO> I have distributions and RPM's that I need to put somewhere. > > > > So distutils stuff works? > > > > And are there any plans for a debian package (more "if not, I'll work > > at it", than an honest request). > > > > best, > > -tony > > -- > Joseph M. Reinhardt, Ph.D. Department of Biomedical Engineering > joe-reinhardt at uiowa.edu University of Iowa, Iowa City, IA 52242 > Telephone: 319-335-5634 FAX: 319-335-5631 > _______________________________________________ > Scipy-dev mailing list > Scipy-dev at scipy.net > http://www.scipy.net/mailman/listinfo/scipy-dev From eric at scipy.org Tue Aug 21 21:31:57 2001 From: eric at scipy.org (eric jones) Date: Tue, 21 Aug 2001 21:31:57 -0400 Subject: [SciPy-dev] AIX isinf, isfinite, etc. Message-ID: <009f01c12aaa$3bee89a0$ec88fea9@ericlaptop> The good news: Almost all of scipy now compiles on AIX 4.x (at least on the SP3) using cc_r and g77. The lone non-ported piece is the vq stuff in cluster. It needs a C++ compiler, and I haven't figured out how to force distutils to use gcc instead of cc_r (or use cc_r for C files and gcc for C++) files. It was good to try this because cc_r found a few portability issues in the C code. (cc_r is the thread-safe standard C compiler on AIX). The bad news: Many of the isinf, isnan, isfinite tests fail on this platform. We new this was gonna be a headache, and it is. No time to explore fixing this now, but will look into the issues as soon as possible. eric From travis at scipy.org Tue Aug 21 23:44:22 2001 From: travis at scipy.org (Travis N. Vaught) Date: Tue, 21 Aug 2001 22:44:22 -0500 Subject: [SciPy-dev] RPMs and source distribution In-Reply-To: <87u1z1j90m.fsf@phantom.ecn.uiowa.edu> Message-ID: We haven't heard anything yet about a working deb package. If anyone were to build one we would certainly like to post it to the SciPy site for all to enjoy :o) Let us know if you are able to come up with something. Thanks, Travis Vaught -----Original Message----- From: scipy-dev-admin at scipy.org [mailto:scipy-dev-admin at scipy.org]On Behalf Of Joe Reinhardt Sent: Tuesday, August 21, 2001 6:20 PM To: scipy-dev at scipy.net; A.J. Rossini Subject: Re: [SciPy-dev] RPMs and source distribution Did this debian package ever materialize? As far as I know, there is no bdist_deb, but I have packaged other python packages using "python setup.py build" and dpkg-buildpackage with no trouble. I would be interested in working to get this packaged. Let me know if I can help. - Joe rossini at u.washington.edu (A.J. Rossini) writes: >>>>>> "TO" == Travis Oliphant writes: > > TO> I've been playing for hours and finally have it so that > > TO> python setup.py sdist python setup.by bdist_rpm > > TO> work as expected. > > TO> I have distributions and RPM's that I need to put somewhere. > > So distutils stuff works? > > And are there any plans for a debian package (more "if not, I'll work > at it", than an honest request). > > best, > -tony -- Joseph M. Reinhardt, Ph.D. Department of Biomedical Engineering joe-reinhardt at uiowa.edu University of Iowa, Iowa City, IA 52242 Telephone: 319-335-5634 FAX: 319-335-5631 _______________________________________________ Scipy-dev mailing list Scipy-dev at scipy.net http://www.scipy.net/mailman/listinfo/scipy-dev From rossini at blindglobe.net Wed Aug 22 08:12:45 2001 From: rossini at blindglobe.net (A.J. Rossini) Date: 22 Aug 2001 05:12:45 -0700 Subject: [SciPy-dev] RPMs and source distribution In-Reply-To: References: Message-ID: <87u1z01ef6.fsf@jeeves.blindglobe.net> >>>>> "TNV" == Travis N Vaught writes: TNV> We haven't heard anything yet about a working deb package. TNV> If anyone were to build one we would certainly like to post TNV> it to the SciPy site for all to enjoy :o) I'm working on it, but slowly. I should be able to send what I've currently got tonight. But please don't let that stop other approaches (I don't claim to have any claims on this, and I definitely don't claim to be the best debian packager...). best, -tony -- A.J. Rossini Rsrch. Asst. Prof. of Biostatistics U. of Washington Biostatistics rossini at u.washington.edu FHCRC/SCHARP/HIV Vaccine Trials Net rossini at scharp.org -------- (wednesday/friday is unknown) -------- FHCRC: M-Tu : 206-667-7025 (fax=4812)|Voicemail is pretty sketchy/use Email UW: Th : 206-543-1044 (fax=3286)|Change last 4 digits of phone to FAX From jmr at engineering.uiowa.edu Wed Aug 22 14:44:24 2001 From: jmr at engineering.uiowa.edu (Joe Reinhardt) Date: Wed, 22 Aug 2001 13:44:24 -0500 Subject: [SciPy-dev] RPMs and source distribution In-Reply-To: <87u1z01ef6.fsf@jeeves.blindglobe.net> (rossini@blindglobe.net's message of "22 Aug 2001 05:12:45 -0700") References: <87u1z01ef6.fsf@jeeves.blindglobe.net> Message-ID: rossini at blindglobe.net (A.J. Rossini) writes: >>>>>> "TNV" == Travis N Vaught writes: > > TNV> We haven't heard anything yet about a working deb package. > TNV> If anyone were to build one we would certainly like to post > TNV> it to the SciPy site for all to enjoy :o) > > I'm working on it, but slowly. I should be able to send what I've > currently got tonight. But please don't let that stop other > approaches (I don't claim to have any claims on this, and I definitely > don't claim to be the best debian packager...). I would be happy to help - send me a note if you want me to take a look at the package when it is ready. - JMR -- Joseph M. Reinhardt, Ph.D. Department of Biomedical Engineering joe-reinhardt at uiowa.edu University of Iowa, Iowa City, IA 52242 Telephone: 319-335-5634 FAX: 319-335-5631