On Jul 11, 2015 12:22 PM, "Olivier Grisel" wrote:
>
> 2015-07-10 22:13 GMT+02:00 Carl Kleffner :
>
> > The best technical solution IMHO would be to make an extra
mingwpy.openblas
> > python package to load libopenblaspy.dll into the process space, as this
> > package could be upgraded independant
2015-07-11 19:19 GMT+02:00 Olivier Grisel :
> 2015-07-10 22:13 GMT+02:00 Carl Kleffner :
> >
> >
> > 2015-07-10 19:06 GMT+02:00 Olivier Grisel :
> >>
> >> 2015-07-10 16:47 GMT+02:00 Carl Kleffner :
> >> > Hi Olivier,
> >> >
> >> > yes, this is all explained in
> >> > https://github.com/xianyi/Open
2015-07-10 22:13 GMT+02:00 Carl Kleffner :
>
>
> 2015-07-10 19:06 GMT+02:00 Olivier Grisel :
>>
>> 2015-07-10 16:47 GMT+02:00 Carl Kleffner :
>> > Hi Olivier,
>> >
>> > yes, this is all explained in
>> > https://github.com/xianyi/OpenBLAS/wiki/Faq#choose_target_dynamic as
>> > well.
>> > This seems
2015-07-11 18:30 GMT+02:00 Olivier Grisel :
> 2015-07-10 20:20 GMT+02:00 Carl Kleffner :
>> I could provide you with a debug build of libopenblaspy.dll. The segfault -
>> if ithrown from openblas - could be detected with gdb or with the help of
>> backtrace.dll.
>
> That would be great thanks. Also
2015-07-10 20:20 GMT+02:00 Carl Kleffner :
> I could provide you with a debug build of libopenblaspy.dll. The segfault -
> if ithrown from openblas - could be detected with gdb or with the help of
> backtrace.dll.
That would be great thanks. Also can you give the build options /
instructions you u
2015-07-10 19:06 GMT+02:00 Olivier Grisel :
> 2015-07-10 16:47 GMT+02:00 Carl Kleffner :
> > Hi Olivier,
> >
> > yes, this is all explained in
> > https://github.com/xianyi/OpenBLAS/wiki/Faq#choose_target_dynamic as
> well.
> > This seems to be necessary for CI systems, right?
>
> The auto detecti
2015-07-10 16:47 GMT+02:00 Carl Kleffner :
> Hi Olivier,
>
> yes, this is all explained in
> https://github.com/xianyi/OpenBLAS/wiki/Faq#choose_target_dynamic as well.
> This seems to be necessary for CI systems, right?
The auto detection should work. If not it's a bug and we should find a
minimal
2015-07-10 18:42 GMT+02:00 Olivier Grisel :
>
>> I assume you've already checked that this is a Windows specific issue?
>
> I am starting a rackspace VM with linux to check. Hopefully it will
> also be detected as Barcelona by openblas.
I just built OpenBLAS 0.2.14 and numpy 1.9.2 under Linux on a
2015-07-10 18:31 GMT+02:00 Nathaniel Smith :
> On Jul 10, 2015 10:51 AM, "Olivier Grisel" wrote:
>>
>> I narrowed down the segfault from the scipy tests on my machine to:
>>
>> OPENBLAS_CORETYPE='Barcelona' /c/Python34_x64/python -c"import numpy
>> as np; print(np.linalg.svd(np.ones((129, 129), dt
It looks like all of the numpy failures there are due to a poor
implementation of hypot. One solution would be to force the use of the
hypot code in npymath for this tool chain. Currently this is done in
numpy/core/src/private/npy_config.h for both MSVC and mingw32.
-Eric
On Fri, Jul 10, 2015 a
I could provide you with a debug build of libopenblaspy.dll. The segfault -
if ithrown from openblas - could be detected with gdb or with the help of
backtrace.dll.
Carl
2015-07-10 18:31 GMT+02:00 Nathaniel Smith :
> On Jul 10, 2015 10:51 AM, "Olivier Grisel"
> wrote:
> >
> > I narrowed down th
On Jul 10, 2015 10:51 AM, "Olivier Grisel" wrote:
>
> I narrowed down the segfault from the scipy tests on my machine to:
>
> OPENBLAS_CORETYPE='Barcelona' /c/Python34_x64/python -c"import numpy
> as np; print(np.linalg.svd(np.ones((129, 129), dtype=np.float64))"
>
> Barcelona is the architecture
I narrowed down the segfault from the scipy tests on my machine to:
OPENBLAS_CORETYPE='Barcelona' /c/Python34_x64/python -c"import numpy
as np; print(np.linalg.svd(np.ones((129, 129), dtype=np.float64))"
Barcelona is the architecture detected by OpenBLAS. If I force Nehalem
or if I reduce the mat
Hi Olivier,
yes, this is all explained in
https://github.com/xianyi/OpenBLAS/wiki/Faq#choose_target_dynamic as well.
This seems to be necessary for CI systems, right?
BTW: i just now renewed the numpy-1.9.2 and scipy-0.15.0 wheels for
python-2.6, 2.7, 3.3, 3.4 on anaconda.org. I also added scipy-
I have updated my gist with more test reports when
OPENBLAS_CORETYPE="Nehalem" is fixed as an environment variable.
Note that on this machine, OpenBLAS detects the "Barcelona" core type.
I used the following ctypes based script to introspect the OpenBLAS
runtime:
https://gist.github.com/ogrisel/a
Good news,
The segfaults on scikit-lern and scipy test suites are caused by a bug
in openblas core type detection: setting the OPENBLAS_CORETYPE
environment variable to "Nehalem" can make the test suite complete
without any failure for scikit-learn.
I will update my gist with the new test results
Hi Carl,
Sorry for the slow reply.
I ran some tests with your binstar packages:
I installed numpy, scipy and mingwpy for Python 2.7 32 bit and Python
3.4 64 bit (downloaded from python.org) on a freshly provisionned
windows VM on rackspace.
I then used the mingwpy C & C++ compilers to build the
unfortunately I can't start the hangout. Both Firefox and chrome hangs.
Tried it again and again.
For this reason a short status:
I can now build the mingwpy toolchain as pip installable wheel.
%USERPROFILE%\pydistutils.cfg should be configured to use the mingw
compiler.
With the preliminary mi
On Thu, Jul 2, 2015 at 10:01 PM, Honi Sanders wrote:
> I’m interested in listening in just to see what it’s like, but I have to
> leave after ~15 minutes because I have a meeting at 4:30. Is that too
> disruptive?
>
Don't worry about it, just join as long as you can.
Ralf
>
> > On Jul 2, 20
I’m interested in listening in just to see what it’s like, but I have to leave
after ~15 minutes because I have a meeting at 4:30. Is that too disruptive?
> On Jul 2, 2015, at 3:59 PM, Nathaniel Smith wrote:
>
> Hi all,
>
> Meeting is starting in a few minutes!
>
> Hangouts link:
> https://
Hi all,
Meeting is starting in a few minutes!
Hangouts link:
https://plus.google.com/hangouts/_/gxtuplvm6g7s55abhjexqerll4a
Google doc for agenda and notes:
https://docs.google.com/document/d/11KC2p3cCsbDVjLcQSCehUiWGyWDNCyOunKfrO7Q7m3E/edit?usp=sharing
Wiki page:
https://github.com/nump
I _may_ be able to join -- but don't go setting up an alternative
conferencing system just for me.
But I'm planning on ring in Austin Tues in any case.
-Chris
Sent from my iPhone
> On Jun 29, 2015, at 9:59 PM, Nathaniel Smith wrote:
>
>> On Fri, Jun 26, 2015 at 2:32 AM, Nathaniel Smith wrote
On Tue, Jun 30, 2015 at 1:51 PM, Ralf Gommers wrote:
>
> On Tue, Jun 30, 2015 at 12:16 PM, Jeff Reback wrote:
>>
>> you guys have an agenda?
>
> I'm guessing a subset of what's listed on
> https://github.com/numpy/numpy/wiki/SciPy-2015-developer-meeting
>
> Would indeed be good to make a proper a
On Tue, Jun 30, 2015 at 7:49 AM, Honi Sanders wrote:
> I’m pretty new to Numpy so I won’t be able to contribute much, but I would
> appreciate being able to sit in on this if possible.
You certainly would be welcome.
-n
--
Nathaniel J. Smith -- http://vorpus.org
__
On Tue, Jun 30, 2015 at 12:16 PM, Jeff Reback wrote:
> you guys have an agenda?
>
I'm guessing a subset of what's listed on
https://github.com/numpy/numpy/wiki/SciPy-2015-developer-meeting
Would indeed be good to make a proper agenda, so we can prepare properly
for the meeting at SciPy. There a
I’m pretty new to Numpy so I won’t be able to contribute much, but I would
appreciate being able to sit in on this if possible.
Honi
> On Jun 30, 2015, at 12:58 AM, Nathaniel Smith wrote:
>
> On Fri, Jun 26, 2015 at 2:32 AM, Nathaniel Smith wrote:
>> Hi all,
>>
>> In a week and a half, this
you guys have an agenda?
I can be reached on my cell 917-971-6387
> On Jun 30, 2015, at 12:58 AM, Nathaniel Smith wrote:
>
>> On Fri, Jun 26, 2015 at 2:32 AM, Nathaniel Smith wrote:
>> Hi all,
>>
>> In a week and a half, this is happening:
>>
>>https://github.com/numpy/numpy/wiki/SciPy-2
On Fri, Jun 26, 2015 at 2:32 AM, Nathaniel Smith wrote:
> Hi all,
>
> In a week and a half, this is happening:
>
> https://github.com/numpy/numpy/wiki/SciPy-2015-developer-meeting
>
> It's somewhat short notice (my bad :-/), but I think it would be good
> to have a short video meeting sometime
Any of those times would work for me.
On Mon, Jun 29, 2015 at 3:14 PM, Nathaniel Smith wrote:
> On Mon, Jun 29, 2015 at 9:04 AM, Nathaniel Smith wrote:
> > On Jun 26, 2015 2:32 AM, "Nathaniel Smith" wrote:
> >>
> >> Hi all,
> >>
> >> In a week and a half, this is happening:
> >>
> >> https
On Mon, Jun 29, 2015 at 9:04 AM, Nathaniel Smith wrote:
> On Jun 26, 2015 2:32 AM, "Nathaniel Smith" wrote:
>>
>> Hi all,
>>
>> In a week and a half, this is happening:
>>
>> https://github.com/numpy/numpy/wiki/SciPy-2015-developer-meeting
>>
>> It's somewhat short notice (my bad :-/), but I
On Jun 26, 2015 2:32 AM, "Nathaniel Smith" wrote:
>
> Hi all,
>
> In a week and a half, this is happening:
>
> https://github.com/numpy/numpy/wiki/SciPy-2015-developer-meeting
>
> It's somewhat short notice (my bad :-/), but I think it would be good
> to have a short video meeting sometime thi
Hi all,
In a week and a half, this is happening:
https://github.com/numpy/numpy/wiki/SciPy-2015-developer-meeting
It's somewhat short notice (my bad :-/), but I think it would be good
to have a short video meeting sometime this week as a kind of
"pre-meeting" -- to at least briefly go over t
32 matches
Mail list logo
