[PYTHON MATRIX-SIG] Structural, etc.

[Paul Barrett]

> If you imagine that the third or fourth "case" comes up, the proposed
> solution becomes absurd.
> import Numerical
> import Structural
> import Gzenoidal
> import FFT_Numerical
> import FFT_Structural
> import FFT_Gzenoidal
> import LAPACK_Numerical
> ...
> etc.

Well, it doesn't become absurd, just annoying.

Many of us may prefer to use ours or others Numerical packages instead
of the Numerical Python default, resulting in the inclusion of similar
Python code anyway in order to differentiation between the two
implementations.   

An example is the FFT, discussion so far has assumed 1-D FFTs, but a
general FFT algorithm would be multi-dimensional.  This would be
faster in the long run, especially for someone that wanted such
behaviour.  To get this I will have to write my own and explicitly
including it everytime in my code.

I like to know and would like others to know explicitly which
algorithm and implementation of code that I am using.  The above few
lines does that.  We are talking precision here, so let's please be
precise. 

 -- Paul

|~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
| Paul Barrett  -  Astrophysicist  -  Universities Space Research Association |
|                 Compton Observatory Science Support Center                  |
| NASA/Goddard SFC     phone: 301-286-1108    "Guk a 'mzimba, sala 'nhliziyo" |
| Code 660.1,          FAX:   301-286-1681    (body grow old, but heart       |
| Greenbelt,MD 20771   barrett@compass.gsfc.nasa.gov           remain behind) |
|             http://lheawww.gsfc.nasa.gov/users/barrett/CV.html              |
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

=================
MATRIX-SIG  - SIG on Matrix Math for Python

send messages to: matrix-sig@python.org
administrivia to: matrix-sig-request@python.org
=================