[Nek5000-users] istep

[nek5000-users at lists.mcs.anl.gov]

Hi Mikael,

I'm going to make a note of your request - it's not supported
now, but could be w/ a bit of effort.  The effort would be 
relatively small for the .fld files, a bit more for the .f0000 
files, which is a newer feature.

Generally I handle this issue by changing the name, e.g.,

myrun_1a.rea
myrun_1b.rea
myrun_1c.rea
...

etc.

In /tools/scripts/ the scripts mvv and cpn make it easy
to do this --

    cpn myrun_1a myrun_1b  copies all the requisite files.

    mvv does the same except with move.

Although it seems like a look a good idea to have the feature 
you're asking about, there are some pitfalls - namely, if you 
change the order midstream in a sequence of runs then Visit/postx
will be unhappy processing the sequence.

If I wish to process a long sequence of .fld or .f files, I usually
ln them to a common base name (e.g., "myrun") using a script that
can be cooked up in about 30 seconds.  I then process the lot.


Paul


On Fri, 15 Apr 2011, nek5000-users at lists.mcs.anl.gov wrote:

> Hi,
>
> Just a very short (probably stupid) question. When restarting a case it
> seems to me that the istep parameters is reset to zero, which leads to new
> fld files overwriting the old. For example, if I run 10 timesteps and store
> blah.fld01 - blah.fld10 I then put blah.fld10 like this in the rea
>
>            1 PRESOLVE/RESTART OPTIONS  *****
> blah.fld10
>
> And then I ask for 10 more timesteps by setting p11 to 10 in the .rea file.
> I would expect to get 10 new fld files blah.fld11 - blah.fld20, but instead
> my blah.fld01 - blah.fld10 files are overwritten. Should it be like this? Is
> there some parameter or similar that one has to make sure to specify when
> restarting to avoid this?  Is there a cumulative istep I don't know of?
>
> Thanks and best regards
>
> Mikael
>