Error when using -maxet to limit the runtime of job

rafr894 · February 25, 2024, 10:07

Hi,

I'm running a job on a cluster that requires me to input an estimated overall runtime. In order to preclude the job from aborting without writing a .res file of all the progress made in case the actual runtime exceeds my prediction, I want to limit the run time using the -maxet command. The CLI command I type in is

Code:

cfx5solve -maxet "200 [min]"

But the error thrown reads : -max-elapse-time is not valid unless a configuration has been specified. My understand was that the .cfg file is the mesh file that is defined in the .def file. So, I include the

Code:

-def <def file name>

in the command, but that throws a CFX partitioner exited with a return code 1 error. Alternately, I tried using the

Code:

-use-mesh-from-iv

in the original command, but that doesn't help either. Can anyone tell me what I may be doing wrong here? Thanks.

ghorrocks · February 25, 2024, 16:52

No, you are heading in the wrong direction there.

A much simpler way of getting it to attempt to stop the solver at a defined time is to use the Elapsed Wall Clock Time Control in the solver tab of CFX-Pre. Then no command line options are required.

rafr894 · February 25, 2024, 23:12

Yes, that is an option. However, I want to specifically be able to change it during runtime to give me more flexibility. See, there is an option on the cluster to extend/lower the wall clock time as the run is progressing, and I'd like to adjust my runtime settings accordingly. Hence, I was going the CLI route.

ghorrocks · February 25, 2024, 23:29

Use "edit run in progress" to change it during a run. This is an option in Solver Manager.

And all these functions can be called from the command line if you want.

Opaque · February 26, 2024, 10:01

You have not described your current model workflow in detail.

Are you using a multiconfiguration setup or just a simple analysis?

could you post the exact command line you are using?

February 25, 2024, 10:07	Error when using -maxet to limit the runtime of job	#1
rafr894 New Member KristianRanta Join Date: Oct 2016 Location: Sundsvall Posts: 25 Rep Power: 9	Hi, I'm running a job on a cluster that requires me to input an estimated overall runtime. In order to preclude the job from aborting without writing a .res file of all the progress made in case the actual runtime exceeds my prediction, I want to limit the run time using the -maxet command. The CLI command I type in is Code: cfx5solve -maxet "200 [min]" But the error thrown reads : -max-elapse-time is not valid unless a configuration has been specified. My understand was that the .cfg file is the mesh file that is defined in the .def file. So, I include the Code: -def <def file name> in the command, but that throws a CFX partitioner exited with a return code 1 error. Alternately, I tried using the Code: -use-mesh-from-iv in the original command, but that doesn't help either. Can anyone tell me what I may be doing wrong here? Thanks.

February 25, 2024, 16:52		#2
ghorrocks Super Moderator Glenn Horrocks Join Date: Mar 2009 Location: Sydney, Australia Posts: 17,703 Rep Power: 143	No, you are heading in the wrong direction there. A much simpler way of getting it to attempt to stop the solver at a defined time is to use the Elapsed Wall Clock Time Control in the solver tab of CFX-Pre. Then no command line options are required. __________________ Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.

February 25, 2024, 23:29		#4
ghorrocks Super Moderator Glenn Horrocks Join Date: Mar 2009 Location: Sydney, Australia Posts: 17,703 Rep Power: 143	Use "edit run in progress" to change it during a run. This is an option in Solver Manager. And all these functions can be called from the command line if you want. __________________ Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.

February 26, 2024, 10:01		#5
Opaque Senior Member Join Date: Jun 2009 Posts: 1,804 Rep Power: 32	You have not described your current model workflow in detail. Are you using a multiconfiguration setup or just a simple analysis? could you post the exact command line you are using? __________________ Note: I do not answer CFD questions by PM. CFD questions should be posted on the forum.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
bash script for pseudo-parallel usage of reconstructPar	kwardle	OpenFOAM Post-Processing	41	August 23, 2023 02:48
Duplicate entry alphaContactAngle in runtime selection table fvPatchField	Roesch	OpenFOAM Programming & Development	2	January 12, 2021 03:35
mpirun, best parameters	pablodecastillo	Hardware	18	November 10, 2016 12:36
Problem in3D model processing	mebinitap	OpenFOAM	2	December 12, 2014 04:40
cfd job	Dr. Don I anyanwu	Main CFD Forum	20	May 17, 1999 15:13

February 25, 2024, 23:12		#3
rafr894 New Member KristianRanta Join Date: Oct 2016 Location: Sundsvall Posts: 25 Rep Power: 9	Yes, that is an option. However, I want to specifically be able to change it during runtime to give me more flexibility. See, there is an option on the cluster to extend/lower the wall clock time as the run is progressing, and I'd like to adjust my runtime settings accordingly. Hence, I was going the CLI route.