[Thomasbr]

This is a copy and paste of the .bat file I used:

SET ansyspath="C:\Program Files\ANSYS Inc\v160\CFX\bin\cfx5solve.exe"
 
%ansyspath% -def "U:\Thomas\triplette-test_files\dp0\CFX\CFX\sans viscous work.def" -double
 
%ansyspath% -def "U:\Thomas\triplette-test_files\dp0\CFX-2\CFX\sans viscous work.def" -double
%ansyspath% -def "U:\Thomas\triplette-test_files\dp0\CFX-1\CFX\sans viscous work.def" -double

[ghorrocks]

I can't see why that would not activate double precision.

You can also set double precision in the def file in CFX-Pre or by using CCL.

If you look at the CCL required to set a run to double precision you will find it is only a few lines. So you can write that the the def file using the -cc flag. This way you don't need to regenerate your def files.

[-Maxim-]

mmmh that's strange. I just checked one of my recent out-files and I found the same note in the beginning

Setting up CFX Solver run ...
+--------------------------------------------------------------------+
| |
| CFX Command Language Upgrade |
| |
+--------------------------------------------------------------------+
Added /SIMULATION CONTROL/EXECUTION CONTROL/EXECUTABLE SELECTION/Double
Precision = Off.

But then it follows with

+--------------------------------------------------------------------+
| |
| CFX Command Language for Run |
| |
+--------------------------------------------------------------------+
[.....]
SIMULATION CONTROL:
EXECUTION CONTROL:
EXECUTABLE SELECTION:
Double Precision = Yes

and I checked with "edit run in progress" in the solver manager - double is clearly activated here. I wrote an email to my CFX support guy asking him about that. I'll report back as soon as I have a response.

[Thomasbr]

@ Glenn: thanks for this interesting Information, I'm going to try that and check if there is a difference.

@ Maxim: I have the same thing too: further in the .out file states "Double Precision = Yes". Thanks for the Report.


I might have spoken too fast with the remark on the Duration time, because the 3rd Simulation needed 13 hours, 13124 timesteps and the last timestep was 6,9757e-7s. So it could be that all 3 simulations were performed with Double Precision and that the only parameter that I change has a big impact on the duration time. Apparently disabling the "Viscous Work Term" (which I can understand because the equations become simpler) or enabling the "High Speed Wall Heat Transfer Model" (when Thermal Energy is checked) need much smaller timesteps and therefore smaller calculation time. In the 3rd simulation, Viscous Work Term was enabled and High Speed HT Model was disabled.

[-Maxim-]

so my CFX support (not from Ansys directly but certified support) answered that he had the same 'problem' before but since "double precision" shows up in the CCL and gets activated during the run, he just ignored the first message so far.
I know, it's not the answer we wanted hear... Maybe you ask Ansys support directly?

[Thomasbr]

Hello Maxim,

thanks for the feedback. I think I will make do. Contacting the Support seems a little bit laborious when you don't have any information (log in, password, information on the license, etc.), because I'm only a student in an Institut.

But well if I have time in the oncoming weeks, I could try to do something with the IT guy of the institut to contact Ansys directly.

[cysanghavi]

I want to run two simulations in two different folders.
It works when the folders are same.
I tried the above suggestions and got the error as following:
Backlash found where operator excepted at run.pl line 3, near "user"


My run.pl file reads as follows:
# ! perl -w
cd G:\Softwares\MAGNiTUDE
print "Running the 1st simulation\n";
system "cfx5solve -def Unnamed.def";

cd G:\Fraunhofer\Report
print "Running the 2nd simulation\n";
system "cfx5solve -def Unnamed1.def";

What is that I am doing wrong. ?

[ThalesMachado]

I have a related problem. I’m running a large number of simulations, let’s say 100.
Then I wrote a perl script which I’m able to initialize from CFX prompt. It works fine.

However, now, I’m willing to run these simulations on a bigger cluster which allows me only to initialize the simulation with a shell script. For instance, now I have to specify the number of cores on my shell script.
Does any of you know how to run my perl script through a shell script?
On my perl, I was specifying the number of cores, simulations and so on.

[leee]

Originally Posted by ghorrocks

I can't see why that would not activate double precision.

You can also set double precision in the def file in CFX-Pre or by using CCL.

If you look at the CCL required to set a run to double precision you will find it is only a few lines. So you can write that the the def file using the -cc flag. This way you don't need to regenerate your def files.

Hi. The same problem araised for me. I activated the double precision through CFX-Pre. But the real problem for me is, when I try to run the cfx solver in interactive mode using the .bat file, the solver manager opens up , but the run is not executed .
Please do help me out from this

[tchavdarov]

How to write different *def files? - Within Workbench or out of it. In Workbench if I clone the model I still have only one *.def file prior execution of the cloned models.
Is there any simple way to change a number in the *.def file. For example the mass flow rate?

Please ignore this question. I found the way via CFX Solver Manager/Edit CFX Solver File browse and open the *def file.

[Gert-Jan]

Outside Workbench. Use the CFX-launcher.
Open the case in Pre and write as many definition files as you can.
Then run them manually using the solver manager or automatically using a batch file.

[elia_l]

Hi all,
I just noted that launching .bat file through CFXlauncher (Tools > Command line) cfx5solver runs all .def files one by one, but in background. Could be possible do the same, but opening also the usual solver window showing monitors and logs?! Possibly writing some command line in batch file or cmd window...


Thanks to all in advance

[-Maxim-]

open solver manager and use option "monitor run in progress". Select the .dir directory where your current simulation is running. That should give you all the monitors and the out file

[elia_l]

Thanks a lot MAXIM. It was simpler then I thought