Re: mpb + output to a file-> strange behaviour (comment)

Dear Steven,

Could it be possible that I did something wrong during the installation 
of MPB? I did it few months ago and I do not recall what I deed exactly. 
   As example, some libraries might be  missing (Guile-devel,...)

The program seems to have a normal behavior when I do not enter in these 
lengthy loops. I have done all the tutorial examples and I get the same 
results as you.

I will try to recompile mpb with the debugging flag and trace it with a 
debugger.

Right know, I am monitoring the memory usage with "top" and the load 
seems to be cte at ~30Mb. The process does not seems to present a memory 
leak.

thanks
Stef



As exemple
Steven G. Johnson a écrit :
> On Mon, 1 May 2006, stephane chatigny wrote:
>> With these new settings the simulation stops after 4616 iterations (on 
>> my computer Athlon 2Gb memory). Some how, the bug seems to be related 
>> to these parameters (presumably via the memory usage).
> 
> I've noticed that if you perform large numbers of runs from within a 
> single .ctl file under Linux it sometimes eventually runs out of memory. 
> I haven't been able to find any memory leak in MPB, so my best guess is 
> that there is one in Guile.
> 
> A workaround is, when you have simple parameter-sweep loop, to put the 
> loop outside MPB (i.e. launch a new MPB process for each loop 
> iteration). e.g. in the bash shell under Linux, do:
> 
>     for x in `seq a dx b`; do program x=$x myfile.ctl; done
> 
> See also
> 
>     http://ab-initio.mit.edu/wiki/index.php/Guile_and_Scheme_links
> 
> Cordially,
> Steven G. Johnson