Graceful exit from a batch run with an error

On running in batch mode, any error generated when reading the journal file (e.g., wrong case/data name, no license available, divergence, etc.) causes the batch file to just stop dead. This is only reasonable if you're interactively running the text interface. The appropriate response upon such an error is for the batch run to stop all Fluent processes and give up the licenses. The problem is that, for users who run on machines within a queuing system, if the batch file hangs, it will just sit there spending queue CPU hours, holding licenses, etc. The queued job will not end, until the hanging job ends.

Add the following line at the beginning of the journal file.

(set! *cx-exit-on-error* #t)

For example,

(set! *cx-exit-on-error* #t)

Show Form
No comments yet. Be the first to add a comment!