[quarkz]

Hi,

I am running OF on clusters with a time limit of 24hr. I'm using a modified OF which writes certain info at the end of the simulation. I found that for certain problems, if it stops at the 24hr limit, it will not finish writing the info and hence I'm not able to restart from where it ended.

Hence, I am wondering if I can set something such that OF will end gracefully after 23hr 55 min?

Thanks!

[Bloerb]

writeControl cpuTime; // Writes data every writeInterval seconds of CPU time.
writeControl clockTime; // Writes data out every writeInterval seconds of real time.

if needed coupled with the timeActivatedFileUpdate functionObject. Or simply the abort function object .

[GerhardHolzinger]

Use the abort functionObject to make OpenFOAM gracefully stop, when it detects the presence of a certain file.

Class
    Foam::functionObjects::abort

Description
    Watches for presence of the named file in the $FOAM_CASE directory
    and aborts the calculation if it is present.

    Currently the following action types are supported:
    - noWriteNow
    - writeNow
    - nextWrite

Define a timed creation of the file, abort is watching for, e.g. by a one-time cron job.
See e.g. https://stackoverflow.com/questions/...time-in-future

This way, you retain the ability to write out at fixed intervals, as graceful stopping is independent of writing out the data. However, this is merely a question of personal preference.

[einstein_zee]

Originally Posted by quarkz

Hi,

I am running OF on clusters with a time limit of 24hr. I'm using a modified OF which writes certain info at the end of the simulation. I found that for certain problems, if it stops at the 24hr limit, it will not finish writing the info and hence I'm not able to restart from where it ended.

Hence, I am wondering if I can set something such that OF will end gracefully after 23hr 55 min?

Thanks!

Hi,

I'm just curious to know what happens if your simulation stops due to time limit by the time that 24 hours is reached, and then the next day you try to send the job but this time change the controlDict entry to start from "latestTime"? is there anything wrong with this approach?