hkroeger
commented
1 month ago Dear Julien,
yes, this is the right place. The 1000 iterations is the hard coded argument for set_endTime. You can change it and then recompile. I should better add some convergence monitoring for the forces. I have thought about this already but did not find the time yet to implement a good approach...
You can also manually intervene:
- set things up and then launch the analysis by clicking "Run"
- while the solver is running, edit the file "system/controlDict" in the case directory and change the value for "endTime" there.
- Then save the file. The solver detects the change and runs for longer.
Alternatively, if the analysis has already stopped after 1000 iterations, you can also edit the "controlDict" and increase "endTime". Then manually restart the solver:
- change to the case directory
- load the OpenFOAM environment, e.g. by executing "of2112" is you had selected OFesi2112 as "OFEname"
- execute the solver either by executing "simpleFoam" if a serial run was configured or "mpirun -np
simpleFoam -parallel" in case of a parallel run - once the solver has sufficiently advanced, run only the evaluation step from the workbench: therefore set the parameter run/evaluateonly to true and re-run the analysis by clicking "Run". Then preprocessing and solver execution will be skipped and only the evaluation step and report compilation will be performed.
Hope this helps.
Regards, Hannes
Hi, First, thanks for the software
Is it possible to customize the number of iterations for the Numerical Wind Tunnel ? I have a case where 1000 is not enough
Not sure this is the right place in numericalwindtunnel.cpp:createCase << cm.insert(new steadyIncompressibleNumerics(cm, steadyIncompressibleNumerics::Parameters() .set_writeInterval(100.0) .setpurgeWrite(0) .setendTime(1000.0) .set_deltaT(1) ));
Regards, Julien