search

hemprasad / pythonxy

Automatically exported from code.google.com/p/pythonxy
0 stars 0 forks source link

Possible Sparse Package Bug in SciPy that comes with Python(x,y) 2.7.6.1 #747

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
1. 2.7.6.1
2.I selected the "Full" option when installing Python(x,y)
3. I did not select "Customize installation directories.
4. I installed Python(x,y) in a custom path. On my comp it is D:\pythonxy
6. I installed Python(x,y) for all users.
7. Windows 7
8. I am running a 32 bit OS.
9. I was logged in as a user with administrator rights.
10. I installed by double clicking the installer (so maybe not instsalled as an 
administrator?).
11. I did not do anything to "clean" my computer, I installed Python(x,y) 
without precaution.

What steps will reproduce the problem?
1.  Download the necessary files to build SfePy and run the program 
run_tests.py.  A failure occurs in a file input_stokes_slip_bc.py.  The root 
cause of this is thought to be Scipy handing Sfepy a buggy sparse matrix.

What is the expected output? What do you see instead?
The expected output using GitBash should be an output to the prompt from the 
program stating, "OK".  Instead, python.exe hangs and a windows prompt, 
"Python.exe has stopped working" appears.

After doing some troubleshooting within the SfePy package, the problem was 
isolated to an internal .py file, input_stokes_slip_bc.py.  Individuals working 
on the SfePy project have suggested that in newer versions of SciPy beyond 
0.14.0, that a possible buggy sparse matrix is handed to SfePy causing such an 
error.  It is believed to be a problem with SciPy. versions beyond 0.14.0- 
because SfePy use to operate correctly with older versions of SciPy.

Is it possible to have help in debugging such an issue? Or, should I take this 
elsewhere?

Thank you!

Original issue reported on code.google.com by matthewg...@gmail.com on 26 Jul 2014 at 8:28

GoogleCodeExporter commented 9 years ago 
Can you please try this on a Linux machine with the relevant packages version 
installed?

If the error persists then the scipy issue tracker and/or mailing list is your 
best bet on getting this fixed.

Original comment by grizzly.nyo on 27 Jul 2014 at 7:04

GoogleCodeExporter commented 9 years ago 
found a possible workaround:
https://github.com/scipy/scipy/issues/3908

patched get_edge_graph()

with:
        import numpy as np

        # bug in scipy 0.14.0 - https://github.com/scipy/scipy/issues/3908
        vals = np.array(vals, dtype=np.int)
        rows = np.array(rows, dtype=np.int)
        cols = np.array(cols, dtype=np.int)

Original comment by grizzly.nyo on 4 Nov 2014 at 12:37