Menu

#223 adjustableTime outputControl fails for parallel runs if also adjustTime step is selected

new
None
normal
minor
Always
minor-fix
latest git
other
2014-08-28
2014-07-08
No

In the latest swak4foam version a new time sampling option is available in the libsampling.so, adjustableTime, which allows you to specify the time interval between two sample instead of the number of itterations. This is particularly handy when also the adjustTimeStep option is used for the simulation, because a fixed time interval with equidistance time spacing between the planes can be obtained.

However, it appears that for parallel run, the adjustTimeStep option fails when the adjustTimeStep option is on; the run crashes with the following message:

[2]
[2]
[2] --> FOAM FATAL IO ERROR:
[2] error in IOstream "IOstream" for operation operator>>(Istream&, List<T>&) : reading first token
[2]
[2] file: IOstream at line 0.
[2]
[2] From function IOstream::fatalCheck(const char*) const
[2] in file db/IOstreams/IOstreams/IOstream.C at line 114.
[2]
FOAM parallel run exiting
[2]


MPI_ABORT was invoked on rank 2 in communicator MPI_COMM_WORLD
with errorcode 1.

NOTE: invoking MPI_ABORT causes Open MPI to kill all MPI processes.
You may or may not see output from other processes, depending on
exactly when Open MPI kills them.



mpirun has exited due to process rank 2 with PID 20210 on
node herpc17666m exiting improperly. There are two reasons this could occur:

  1. this process did not call "init" before exiting, but others in
    the job did. This can cause a job to hang indefinitely while it waits
    for all processes to call "init". By rule, if one process calls "init",
    then ALL processes must call "init" prior to termination.

  2. this process called "init", but exited without calling "finalize".
    By rule, all processes that call "init" MUST call "finalize" prior to
    exiting or it will be considered an "abnormal termination"

This may have caused other processes in the application to be
terminated by signals sent by mpirun (as reported here).

For a serial run the same case can run when adjustTimeStep in controlDict is combined with the adjustableTimeStep.

A sample case has been included based on the pimpleFoam tutorial pitzDaily in which Allrun can be started. The sample plane settings are given in the planeVTKDict. In case the adjustableTimestep is selected, the parallel run will crash if also adjustTimeStep is selected.

Since the major benefit of the adjustableTimeStep is for the non-uniform time stepping, it would be great if you could fix this problem

1 Attachments

Discussion


Log in to post a comment.

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.