> > AFAIK the bi-cluster test failure is unknown. I cannot reproduce it my >
> > self. which version of scipy are you using? >
Thanks for replying, Olivier. >>> scipy.version.version '0.13.0b1' >>>
numpy.version.version '1.7.0' I am curious is why more than 100 tests were
stopped using the post-installed testing command. From your answer I understant
not every test run in the pre-installation stage are included in the
post-installation test suit. > > 1700+ tests are not enough for you? :) >
Regarding the the number of tests, scipy runs a few more than that:
----------------------------------------------------------------------^ Ran
9902 tests in 895.284s FAILED (KNOWNFAIL=131, SKIP=324, failures=1)
<nose.result.TextTestResult run=9902 errors=0 failures=1> Thus, I was thinking
something was wrong with my installation as I did not follow the standard way
of installing scikit-learn because the atlas I want to use is in STATIC version
and is not in a standard location. To deal with this sort of things scipy/numpy
make use of a "site.cfg" configuration file. Perhaps something similar needs to
be added to scikit-learn installation procedure. Salut, Sergio Message: 4 Date:
Thu, 24 Oct 2013 16:07:17 +0200 From: Olivier Grisel <[email protected]>
Subject: Re: [Scikit-learn-general] On building scikit-learn-0.14.1 with STATIC
ATLAS on non-standard location To: scikit-learn-general
<[email protected]> Message-ID:
<cafve7k5hyi75sqr6dh3t0hyvsdtjg-9soja48k9jp0tb8rh...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8 2013/10/23 Sergio Rojas
<[email protected]>: > Hello everyone, > > I was able to compile
scikit-learn-0.14.1 with STATIC version of ATLAS using > the building command:
> > python setup.py build_ext >
--include-dirs='/home/myacct/myProg/NumLibs64b/include > /
-L/home/srojas/myProg/NumLibs64b/lib -llapack -lcblas -lf77blas -latlas' >
--inplace > > I should mention that I came up with this way to build
scikit-learn after > installing mlpy >
[http://mlpy.sourceforge.net/docs/3.5/install.html#installing-on-nix-from-source
> ]. Interesting, thanks for the reference. > I am curious about the
following: > > The pre-installation test > python nosetests sklearn/ > > ended
with (FULL OUTPUT at [ https://gist.github.com/anonymous/7089302 ] ): > ... >
---------------------------------------------------------------------- > Ran
1860 tests in 137.411s > FAILED (SKIP=14, errors=1, failures=2) > > However,
the post-installation test > nosetests --exe sklearn > > ended with (FULL
OUTPUT at [ https://gist.github.com/anonymous/7124307 ] ): >
---------------------------------------------------------------------- > Ran
1720 tests in 148.112s > FAILED (SKIP=14, errors=1, failures=2) > > Should not
be the same number of test run by both commands? Weird. I think we should
include all the tests in the distribution. FYI: the test_image.py failures are
known: they are caused by a change in recent versions of scipy (after 0.12).
Nobody took the time to investigate though. AFAIK the bi-cluster test failure
is unknown. I cannot reproduce it my self. which version of scipy are you
using? > I executed successfully a few examples from the page >
http://scikit-learn.org/stable/auto_examples/index.html > > Is there any other
way to test the installation of this > module? 1700+ tests are not enough for
you? :) -- Olivier ------------------------------ Message: 5 Date: Thu, 24 Oct
2013 16:11:25 +0200 From: Olivier Grisel <[email protected]> Subject:
Re: [Scikit-learn-general] On building scikit-learn-0.14.1 with STATIC ATLAS on
non-standard location To: scikit-learn-general
<[email protected]> Message-ID:
<CAFvE7K5FTiczZH6aW4OZbB_RV5B1aN1oodMGMaH=10mtubq...@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8 2013/10/24 Olivier Grisel
<[email protected]>: > 2013/10/23 Sergio Rojas <[email protected]>: >>
Hello everyone, >> >> I was able to compile scikit-learn-0.14.1 with STATIC
version of ATLAS using >> the building command: >> >> python setup.py build_ext
>> --include-dirs='/home/myacct/myProg/NumLibs64b/include >> /
-L/home/srojas/myProg/NumLibs64b/lib -llapack -lcblas -lf77blas -latlas' >>
--inplace AFAIK you should not use --include-dirs to pass library link
instructions but rather --libraries and --library-dirs. -- Olivier
http://twitter.com/ogrisel - http://github.com/ogrisel
------------------------------
------------------------------------------------------------------------------
October Webinars: Code for Performance Free Intel webinars can help you
accelerate application performance. Explore tips for MPI, OpenMP, advanced
profiling, and more. Get the most from the latest Intel processors and
coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
------------------------------ _______________________________________________
Scikit-learn-general mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general End of
Scikit-learn-general Digest, Vol 45, Issue 51
****************************************************
------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Scikit-learn-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/scikit-learn-general
