[Nek5000-users] istep

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

Hi Mikael,

It's not a bug - it's a feature.
Typically, I move my fld into a new folder (e.g. run01, run02, ...) to
avoid that my data gets overwritten. Why do you want to get a single
fld-file set for different runs? Anyway, one way to do this is to use
a shell script creating a set of symbolic links. Here an example:

foo.fld01 -> run01/foo.fld01
foo.fld02 -> run01/foo.fld02
foo.fld03 -> run02/foo.fld01
foo.fld04 -> run02/foo.fld02


Hth,
Stefan




On 4/15/11, nek5000-users at lists.mcs.anl.gov
<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
>