Example -BatchOptions with -Remote (Windows)

In this example, we run a batch HFSS analysis of project file project1.aedt. We want all temporary files and directories to be created in C:\temp\HFSS instead of using the default temporary directory. We decide that the analysis will be done on a remote host, at IP address 12.34.56.78. Because of limited memory on the remote host, we decide to run the analysis using only a single COM engine. Because the remote host has four cores, we decide to use four four processors for of the analysis. We can use the ‑Remote option to specify that there will be a single remote COM engine.

Here is a sample command line for this analysis, where the project file \\somehost\projects\project1.aedt is located in a shared directory specified using a UNC path:

ansysedt -BatchSolve -Remote -Machinelist list=12.34.56.78
-batchoptions "'TempDirectory'='C:/temp/HFSS'
'Desktop/Settings/ProjectOptions/NumberofProcessors'=4"
\\somehost\projects\project1.aedt

An alternative is to use the ‑Distributed command line option. Because the -Machinelist list contains only one host, there is a single remote COM engine in this case also.

ansysedt -BatchSolve -Distributed -Machinelist list=12.34.56.78
-batchoptions "'TempDirectory'='C:\\temp\\HFSS'
'Desktop/Settings/ProjectOptions/NumberofProcessors'=4"
\\somehost\projects\project1.aedt

The second line of the first example shows that you can use the forward slash "/" as a Windows directory separator within option value 'strings'. In this case, it is used in the TempDirectory path. You can also use the customary backslash "\" as a Windows directory separator, but it must be doubled to "\\" because the backslash is also an escape character within parameter strings. This usage is demonstrated in the second line of the second example, again in the TempDirectory path.