On Feb 4, 2008 3:29 PM, Robert Cimrman <cimr...@ntc.zcu.cz> wrote:
I created the account offlist. I am interested in getting sfepy working on all architectures, first I want to try my faster machine with 4 processors, we can also try some parallel solvers in there. And second, later I'd like to get into Debian, when we make it more robust and user friendly and documented. So just having the aim of passing quite strict Debian policies will improve the overall quality of the software.
Yeah, it is good to set high aims.
I am now struggling with a weird thing, trying the code on your 64bit machine:
in C, I have the following declaration of function parameters (rawGraph() in fem.c): .., int32 nRow, int32 nCol, int32 nGr, .. where typedef int int32; is in sfe/fem/extmods/types.h
As I understand it, "int" is 64bit on Quad Core, so int32 is in fact 64bit here, if you use this declaration, isn't it?
A strange thing is, that with shape = nm.array( shape, dtype = nm.int64 ) the call to the swigged C function works, but with nm.int32 does not! This is strange.
Well, int32 above is 64bit as I understand it. So nm.int64 matches it, so it works. nm.int32 doesn't match it, so it doesn't work. No surprise for me.
Why not to use numpy types, instead of doing things on our own (=wrong:)?
Ondrej