Elapsed Wall Clock Time
 

Hi,

Is there a way to tell CFX to stop the simulation after 11 hours of wall clock run time? I submit jobs to a high end computer node, which the maximum allowed run time is 12 hours. Before the computer kicks me out and aborts my job I want to write a results file at the 11th hour.

I thought the "Elapsed Wall Clock Time Control" option might have done this but after reading the CFX Pre guide it seems I'm wrong.

I did a search, and read a comment by ghorrocks in this thread who said
This sounds like what I want. Does anyone know of a way to implement this?

Thank you

I had the same problem a few years ago and as far as I remember, the elapsed wall clock time control was exactly what I needed.

I've had problems getting the elapsed wall clock time control to work, especially if Im using many cores for the simulation. It seems that it never kicks in, even though the wall clock time has expired. If I have to stop a simulation, I just run cfx5stop manually. Im sure there are ways to do it more efficiently, e.g. using cron as mentioned by Glenn.

The elapsed wall clock time is a new(ish) feature which makes it very easy. The alternative using a cron job is the old way of doing it - but the idea of running cfx5stop to stop a job is also useful with other triggers which are not built into CFX.

As for how to use cron: http://www.lmgtfy.com/?q=cron (sorry about the sarcasm but I have been itching to use that link :) )

Excellent. Thanks for your replies. I'll do a bit more digging around using cron, and I'll run a few simple jobs using the command to see if it works.

P.S - Lance. I agree. I've had no luck getting the lapsed wall clock time control to work on 16 cores. I doubt it'll work when I ratchet up the power to 64 or 128 cores!

If I remember correctly I got the control to work using 64 cores, but there was no way that it worked for 128 or more. However, cfx5stop worked fine for the same simulation. I asked Ansys about this a long time ago, but they never addressed the issue.