unicorn team mailing list archive
-
unicorn team
-
Mailing list archive
-
Message #00005
Re: aero_f.dat after chkp restart
-
To:
Johan Jansson <jjan@xxxxxxxxxx>
-
From:
Niclas Jansson <njansson@xxxxxxxxxx>
-
Date:
Tue, 28 Jun 2011 19:55:13 +0200
-
Cc:
unicorn@xxxxxxxxxxxxxxxxxxx
-
In-reply-to:
<BANLkTimhzM5dGjdP9PH4C8xfDBni3Ss1=Q@mail.gmail.com> (Johan Jansson's message of "Tue, 28 Jun 2011 19:38:18 +0200")
-
User-agent:
Gnus/5.1008 (Gnus v5.10.8) Emacs/22.3 (berkeley-unix)
Johan Jansson <jjan@xxxxxxxxxx> writes:
> How about just appending to the file, and then cleaning up the overlap
> after the simulation has completed? We could write a simple Python
> tool which cuts away all lines with times which are not strictly
> increasing.
>
> Best,
> Johan
>
True, we can even do it on the fly. For example, post pone drag
computation until the simulation time is larger then the last sample
in aero_f.dat
While on the subject, we need to rethink aero_f.dat, for example
lustre is not about the small amount of data written every timestep.
Niclas
> On Tue, Jun 28, 2011 at 4:31 PM, Niclas Jansson <njansson@xxxxxxxxxx> wrote:
>>
>> Hi,
>>
>> As it is now, aero_f.dat is overwritten after a checkpoint restart. Any
>> thoughts on how to deal with this in a good way are welcome.
>>
>> Niclas
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~unicorn
>> Post to : unicorn@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~unicorn
>> More help : https://help.launchpad.net/ListHelp
>>
Follow ups
References