The problem is I don't have time for this at the moment, I have to develop my algorithm for my PhD, and if one does not work, I'll try another one, but this is strange because this algorithm worked in the past...
By incentive, I meant incentive for me, not for you :) I think this could be really helpful for other problems if this kind as well.
But as you have the same problems than me ;)
than 150MB, with massif, it goes higher than 2.7GB, and this is before
really hungry process. Using massif with code using a large number of python code is clearly a no no, since it uses so much malloc. Sometimes, you can just stop
BTW, I can't use massif. Although the normal algorithm does not use more the the thing when it is growing up, and watching the resulting graphs. But this is no fun, and if you have no time...
It's manily that it crashes when the second file is loaded into memory, the model that will be used for this data isn't even loaded and thus the value of the result is zero :( Strange though (IMHM) that massif needs to allocate so much memory for this little data. Matthieu