[Numpy-discussion] Numpy Benchmarking (original) (raw)
joris at ster.kuleuven.ac.be joris at ster.kuleuven.ac.be
Wed Jun 28 04:14:41 EDT 2006
- Previous message (by thread): [Numpy-discussion] Numpy Benchmarking
- Next message (by thread): [Numpy-discussion] Numpy Benchmarking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Hi,
[TO]: NumPy uses Numeric's old wrapper to lapack algorithms. [TO]: [TO]: SciPy uses it's own f2py-generated wrapper (it doesn't rely on the [TO]: NumPy wrapper). [TO]: [TO]: The numpy.dual library exists so you can use the SciPy calls if the [TO]: person has SciPy installed or the NumPy ones otherwise. It exists [TO]: precisely for the purpose of seamlessly taking advantage of [TO]: algorithms/interfaces that exist in NumPy but are improved in SciPy.
This strikes me as a little bit odd. Why not just provide the best-performing function to both SciPy and NumPy? Would NumPy be more difficult to install if the SciPy algorithm for inv() was incorporated?
Joris
Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
- Previous message (by thread): [Numpy-discussion] Numpy Benchmarking
- Next message (by thread): [Numpy-discussion] Numpy Benchmarking
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]