headers
Prabhu Ramachandran | 1 Oct 2002 05:00
Picon

Re: atlas/clapack/etc problems.

>>>>> "LC" == Louis Cordier <lcordier <at> dsp.sun.ac.za> writes:

    LC> Hi, I need lots of help, pleeeeeeeease (;

    LC> My goal is to run Python2.2 on a 60 Workstation Cluster
    LC> (Debian3.0), using scipy.cow. However I cant even get scipy to
    LC> work.

Instructions for Debian.

 1. apt-get install lapack-dev blas-dev fftw-dev

 2. Download ATLAS-3.4.x.  Build it and also do this:

    http://math-atlas.sourceforge.net/errata.html#completelp

 3. Download Numeric-22.0.  Debian's python-numeric is old and does
 not have enough.  Build Numeric and install it in /usr/local like so:

    python setup.py install --prefix=/usr/local

 4. cd /usr/include/python2.2/
    mv Numeric Numeric.old
    ln -s /usr/local/include/python2.2/Numeric .

 5. Get scipy cvs (follow instructions on the web).

 6. Then do the following:

    cd scipy
(Continue reading)

Permalink | Reply | 627 comments |
headers
Skip Montanaro | 1 Oct 2002 05:37
Picon
Favicon

Re: atlas/clapack/etc problems.


    Prabhu> export ATLAS=/full/path/to/your/freshly/built/atlas/*.a

Is this correct?  I've never seen any sort of library or library directory
reference like this before.  I don't recall seeing it documented this way.
Looking back at INSTALL.txt I don't see anything specifying the format of
the ATLAS environment variable.

I would have expected a directory reference like

    export ATLAS=/full/path/to/your/freshly/built/atlas

(which is what I've been using) or a pointer to a single library like

    export ATLAS=/full/path/to/your/freshly/built/atlas/libatlas.a

--

-- 
Skip Montanaro - skip <at> pobox.com
"Airplanes don't fly until the paperwork equals the weight of the
aircraft. Same with i18N." - from the "Perl, Unicode and i18N FAQ"
Permalink | Reply | 1 comment |
headers
Prabhu Ramachandran | 1 Oct 2002 07:12
Picon

Re: atlas/clapack/etc problems.

>>>>> "SM" == Skip Montanaro <skip <at> pobox.com> writes:

    Prabhu> export ATLAS=/full/path/to/your/freshly/built/atlas/*.a

    SM> Is this correct?  I've never seen any sort of library or

The example I gave was confusing.  :( To clarify, ATLAS needs to point
to the directory that contains all the libs build by atlas and not to
the libs themselves.  So if that is /src/ATLAS/lib/arch/Linux_PIII/

export ATLAS=/src/ATLAS/lib/arch/Linux_PIII/

    SM> I would have expected a directory reference like

    SM>     export ATLAS=/full/path/to/your/freshly/built/atlas

Yes, it is a directory reference to the directory that contains all
the *.a's.  That is what I meant but gave a lousy example.

cheers,
prabhu
Permalink | Reply | 0 comments |
headers
eric jones | 1 Oct 2002 10:47

RE: about using python class in weave


> -----Original Message-----
> From: scipy-user-admin <at> scipy.net [mailto:scipy-user-admin <at> scipy.net]
On
> Behalf Of Jing (George) Cao
> Sent: Monday, September 23, 2002 3:32 PM
> To: scipy-user <at> scipy.net
> Subject: RE: [SciPy-user] about using python class in weave
> 
> I am now want to make SWIG and python work together, so I guess I met
the
> same problem.
> 
> Dave told me weave works fine with previous version of SWIG, and I
also
> found a directory named swig in WEAVE. Is there any document about
what
> you've done to make weave and previous SWIG works together and where
can
> I find it?

The documentation on the weave site is about all there is right now.
The CVS version is significantly changed from this, and the code is much
cleaner.  There is a weave/wx_spec.py file that defines the wx
converter.  For now, you'll need to examine this.  The c_spec.py file
may also be useful.

eric

>
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nils Wagner | 2 Oct 2002 15:03
Picon

Latest CVS problems during build

Hi,

There seems to be a problem with the latest cvs-version

This is the output of /usr/local/bin/python setup.py build

Traceback (most recent call last):
  File "setup.py", line 133, in ?
    install_package()
  File "setup.py", line 99, in install_package
    config.extend([get_package_config(x,parent_package)for x in
standard_packages])
  File "setup.py", line 49, in get_package_config
    config = mod.configuration(parent)
  File "linalg/setup_linalg.py", line 33, in configuration
    atlas_info = get_info('atlas')
  File "scipy_distutils/system_info.py", line 127, in get_info
    return cl().get_info()
  File "scipy_distutils/system_info.py", line 224, in __init__
    assert isinstance(self.search_static_first, int)
TypeError: isinstance() arg 2 must be a class or type

Any idea ?

Nils
Permalink | Reply | 2 comments |
headers
Pearu Peterson | 2 Oct 2002 15:44
Picon
Picon
Favicon

Re: Latest CVS problems during build


On Wed, 2 Oct 2002, Nils Wagner wrote:

> Hi,
> 
> There seems to be a problem with the latest cvs-version
> 
> This is the output of /usr/local/bin/python setup.py build
> 
> Traceback (most recent call last):
>   File "setup.py", line 133, in ?
>     install_package()
>   File "setup.py", line 99, in install_package
>     config.extend([get_package_config(x,parent_package)for x in
> standard_packages])
>   File "setup.py", line 49, in get_package_config
>     config = mod.configuration(parent)
>   File "linalg/setup_linalg.py", line 33, in configuration
>     atlas_info = get_info('atlas')
>   File "scipy_distutils/system_info.py", line 127, in get_info
>     return cl().get_info()
>   File "scipy_distutils/system_info.py", line 224, in __init__
>     assert isinstance(self.search_static_first, int)
> TypeError: isinstance() arg 2 must be a class or type
> 
> Any idea ?

Fixed in CVS.

Thanks.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Nils Wagner | 2 Oct 2002 16:08
Picon

scipy.test('fast') failed

Hi,

The result of scipy.test('fast') is an infinite loop.
What is the reason for that ?

Python 2.1.2 (#1, Feb 25 2002, 18:04:21)
[GCC 2.95.3 20010315 (SuSE)] on linux2
Type "copyright", "credits" or "license" for more information.
>>> import scipy
>>> scipy.__version__
'0.2.0_alpha_139.4230'

Nils
Permalink | Reply | 501 comments |
headers
Pearu Peterson | 2 Oct 2002 17:54
Picon
Picon
Favicon

Re: scipy.test('fast') failed


On Wed, 2 Oct 2002, Nils Wagner wrote:

> Hi,
> 
> The result of scipy.test('fast') is an infinite loop.

That's interesting!

> What is the reason for that ?

The reason is irrelevant because AFAIK scipy.test takes only integer
arguments. So, use

  scipy.test(1)

Pearu
Permalink | Reply | 502 comments |
headers
Nils Wagner | 2 Oct 2002 18:05
Picon

Re: scipy.test('fast') failed

Pearu Peterson schrieb:
> 
> On Wed, 2 Oct 2002, Nils Wagner wrote:
> 
> > Hi,
> >
> > The result of scipy.test('fast') is an infinite loop.
> 
> That's interesting!
> 
> > What is the reason for that ?
> 
> The reason is irrelevant because AFAIK scipy.test takes only integer
> arguments. So, use
> 
>   scipy.test(1)
> 
What you may find in installation.txt is 

7. Testing SciPy

    Python comes with some unit tests and the numbers are growing every
day
    (well monthly anyway). To test your installation use
scipy.test('fast') to
    test the quick sub-set of all tests or scipy.test() to run all
available
    tests.  The first should take less than one second, the second will
take
    minutes, depending on your processor speed because it includes the
(Continue reading)

Permalink | Reply | 7 comments |
headers
Pearu Peterson | 2 Oct 2002 18:13
Picon
Picon
Favicon

Re: scipy.test('fast') failed


On Wed, 2 Oct 2002, Nils Wagner wrote:

> Pearu Peterson schrieb:
> > 
> > On Wed, 2 Oct 2002, Nils Wagner wrote:
> > 
> > > Hi,
> > >
> > > The result of scipy.test('fast') is an infinite loop.
> > 
> > That's interesting!
> > 
> > > What is the reason for that ?
> > 
> > The reason is irrelevant because AFAIK scipy.test takes only integer
> > arguments. So, use
> > 
> >   scipy.test(1)
> > 
> What you may find in installation.txt is 

<snip>

Well, these docs are wrong then. Read the source or use
  scipy.test(<int>)

Pearu
Permalink | Reply | 5 comments |

Gmane