[SciPy-User] many test failures on windows 64

[Bruce Southey]

On 07/06/2010 08:03 AM, Robin wrote:
> On Tue, Jul 6, 2010 at 3:36 AM, Bruce Southey<bsouthey at gmail.com>  wrote:
>    
>> On Mon, Jul 5, 2010 at 5:40 AM, Robin<robince at gmail.com>  wrote:
>>      
>>> Hi,
>>>
>>> I am using Python.org amd64 python build on windows 7 64 bit.
>>>
>>> I am using numpy and scipy builds from here:
>>> http://www.lfd.uci.edu/~gohlke/pythonlibs/
>>>
>>> I get many errors in scipy test (none for numpy). Particularly in
>>> scipy.sparse.linalg which I need to use (and in my code it appears
>>> spsolve is giving incorrect results).
>>>
>>> Is there a better 64 bit windows build to use?
>>>        
>> Under 32-bit Python and the scipy 0.8 rc1 under Windows 7 64bit, I
>> only get the test_boost error the directory removal error (from this
>> test: "test_create_catalog (test_catalog.TestGetCatalog) ...").
>>
>> Some of the errors could be due to Window's lack of support for 64-bit
>> like the "test_complex (test_basic.TestLongDoubleFailure)". However,
>> you probably would have to build your own find out those if no one
>> else has them.
>>      
> I suspect there are more errors because of indices being longs instead
> of ints on Windows.
>    
It would be great to track some of these down. Basically scipy has not 
had the attention that numpy has in this matter eventhough David 
Cournapeau done really incredible work in getting numpy/scipy to work 
under 64-bit Windows.

>> Given all the issues with 64-bit windows, do you really need 64-bit numpy/scipy?
>>      
> Unfortunately I do... it looks like I will now have to port a lot of
> Python code to Matlab. I know Windows isn't very popular in the Scipy
> community, and I try to avoid using it when I can, but it seems
> Windows 7 is a lot better than previous versions.
Windows 7 is a big improvement over Vista but both suffer the 
transisition from 32-bit to x64 64-bit architecture (similar to Linux 
when these x64 cpu's came out). Sure most people do not develop with 
Windows but do not equate that with a lack of interest. The problem is 
that Windows and how the Windows binaries are build just makes it very 
extremely hard to develop for.


> Also>4GB RAM is now
> more or less standard for numerical work so I think 64 bit windows
> really should be supported.
Yes, there are many people who want it but the tools are too complex to 
use by casual people.

>   In my group a large factor in the decision
> to use windows was remote desktop and terminal services... For
> non-command line users there is nothing equivalent that I know of.
> (There is NX for linux but only 2 users is free - with a small tweak
> to windows 7 it is possible to have full terminal server behaviour).
>    
You tried FreeNx?
http://freenx.berlios.de/

While this is really old (and has some big issues including not being 
maintained) but I occasionally use xrdp as you can connect to Linux with 
Windows remote desktop.
"RDP Server - An open source RDP server and X server capable of 
accepting connections from rdesktop and ms terminal server clients."
http://xrdp.sourceforge.net/

> I wonder how enthought get around this problem with 64 bit EPD on windows?
>
> Cheers
>
> Robin
>
>    
Can't comment on those.

Bruce

>    
>> Bruce
>>
>>
>>      
>>>>> scipy.test()
>>>>>            
>> Running unit tests for scipy
>> NumPy version 1.4.1
>> NumPy is installed in E:\Python26\lib\site-packages\numpy
>> SciPy version 0.8.0rc1
>> SciPy is installed in E:\Python26\lib\site-packages\scipy
>> Python version 2.6.3 (r263rc1:75186, Oct  2 2009, 20:40:30) [MSC
>> v.1500 32 bit (Intel)]
>> nose version 0.11.1
>> [snip]
>> ======================================================================
>> FAIL: test_data.test_boost(<Data for arccosh: acosh_data_ipp-acosh_data>,)
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>>   File "E:\Python26\lib\site-packages\nose-0.11.1-py2.6.egg\nose\case.py",
>> line 183, in runTest
>>     self.test(*self.arg)
>>   File "E:\Python26\lib\site-packages\scipy\special\tests\test_data.py",
>> line 205, in _test_factory
>>     test.check(dtype=dtype)
>>   File "E:\Python26\lib\site-packages\scipy\special\tests\testutils.py",
>> line 223, in check
>>     assert False, "\n".join(msg)
>> AssertionError:
>> Max |adiff|: 1.77636e-15
>> Max |rdiff|: 2.44233e-14
>> Bad results for the following points (in output 0):
>>             1.0000014305114746 =>            0.0016914556651292853 !=
>>       0.0016914556651292944  (rdiff         5.3842961637318929e-15)
>>              1.000007152557373 =>            0.0037822080446613874 !=
>>       0.0037822080446612951  (rdiff         2.4423306175913249e-14)
>>             1.0000138282775879 =>            0.0052589439468011612 !=
>>       0.0052589439468011014  (rdiff         1.1380223962570286e-14)
>>             1.0000600814819336 =>             0.010961831992188913 !=
>>        0.010961831992188852  (rdiff         5.5387933059412495e-15)
>>             1.0001168251037598 =>             0.015285472131830449 !=
>>        0.015285472131830425  (rdiff         1.5888373256788015e-15)
>>             1.0003981590270996 =>             0.028218171738655283 !=
>>        0.028218171738655373  (rdiff         3.1967209494023856e-15)
>>
>> ----------------------------------------------------------------------
>> _______________________________________________
>> SciPy-User mailing list
>> SciPy-User at scipy.org
>> http://mail.scipy.org/mailman/listinfo/scipy-user
>>
>>      
> _______________________________________________
> SciPy-User mailing list
> SciPy-User at scipy.org
> http://mail.scipy.org/mailman/listinfo/scipy-user
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.scipy.org/pipermail/scipy-user/attachments/20100706/a9a7fd42/attachment.html>