Hello, I'm trying to test SU2 tutorial 8 but every time i launch it i get the same error. I'm using windows 7, SU2 v3.0 and Python v 2.7 with numpy and scipy. All environment are set up. All launched in serial. And I have to correct the interface.py in processes condition > 1 instead of 0, cuz when i launch script shape_optimization.py -f inv_ONERAM6.cfg without any parameter -p (btw launch with -p 0 worked without any changes in code) it show me error "could not find an mpi interface".
def build_command( the_Command , processes=0 ):
""" builds an mpi command for given number of processes """
the_Command = base_Command % the_Command
if processes > 1:
if not mpi_Command:
raise RuntimeError , 'could not find an mpi interface'
the_Command = mpi_Command % (processes,the_Command)
this list i get in cmd.exe
----------------------- Volumetric grid deformation ---------------------
Performing the deformation of the volumetric grid.
Traceback (most recent call last):
File "C:\SU2\shape_optimization.py", line 124, in <module>
File "C:\SU2\shape_optimization.py", line 69, in main
File "C:\SU2\shape_optimization.py", line 107, in shape_optimization
File "C:\SU2\SU2\opt\scipy_tools.py", line 102, in scipy_slsqp
epsilon = 1.0e-06 )
File "C:\Python27\lib\site-packages\scipy\optimize\slsqp.py", line 200, in fmi
File "C:\Python27\lib\site-packages\scipy\optimize\slsqp.py", line 354, in _mi
fx = func(x)
File "C:\Python27\lib\site-packages\scipy\optimize\optimize.py", line 281, in
return function(*(wrapper_args + args))
File "C:\SU2\SU2\opt\scipy_tools.py", line 120, in obj_f
obj = project.obj_f(x)
File "C:\SU2\SU2\opt\project.py", line 203, in obj_f
return self._eval(konfig, func,dvs)
File "C:\SU2\SU2\opt\project.py", line 172, in _eval
vals = design._eval(func,*args)
File "C:\SU2\SU2\eval\design.py", line 132, in _eval
vals = eval_func(*inputs)
File "C:\SU2\SU2\eval\design.py", line 230, in obj_f
func = su2func(this_obj,config,state)
File "C:\SU2\SU2\eval\functions.py", line 75, in function
aerodynamics( config, state )
File "C:\SU2\SU2\eval\functions.py", line 148, in aerodynamics
info = update_mesh(config,state)
File "C:\SU2\SU2\eval\functions.py", line 424, in update_mesh
info = su2run.deform(config)
File "C:\SU2\SU2\run\deform.py", line 93, in deform
File "C:\SU2\SU2\run\interface.py", line 136, in MDC
run_command( the_Command )
File "C:\SU2\SU2\run\interface.py", line 279, in run_command
raise Exception , message
Exception: Path = C:\test\oneram6\DESIGNS\DSN_002\DEFORM\,
Command = C:\SU2\SU2_MDC config_MDC.cfg
SU2 process returned error '3'
Help me please :)
I'm trying to use Tutorial 8 for my own wing model and i have some troubles with FFD box deformation. Can anyone give me advise what should i need to change or correct to solve this?
strange error... can you run SU2_MDC on this config manually?
go to DESIGNS/DSN_001/DEFORM and try the command there.
I don't have this folder because I'm using previous version of SU2 (2.0) x64. But i have config_opt_MDC_inv_ONERAM6.cfg so i think it's the same config file for MDC that uses in SU2 v 3.0. And it's proceed success.
My wing mesh converted from ICEM CFD .CGNS to .SU2 format using config file options, so maybe problem in this? And i noticed that when i start SU2_CFD manually the
------------------------- Geometry preprocessing -------------
Setting local point and element connectivity.
Checking the numerical grid orientation.
Identifying edges and vertices.
Computing centers of gravity.
Setting the control volume structure.
Volume of the computational grid: 0.49979.
Searching for closest normal neighbor on the surface.
Searching for sharp corners on the geometry.
Setting the multigrid structure.
CVs of the MG level: 6835. Agglom. rate 1/5.78186. MG level: 1
CVs of the MG level: 1495. Agglom. rate 1/4.57191. MG level: 2
CVs of the MG level: 727. Agglom. rate 1/2.0564. MG level: 3.
Volume of the computational grid: 0.49979. is very small.
Could you please share the output from the portion of the code where the CGNS file is parsed? It should print the number of nodes, elements, boundaries (with marker names), etc. This should help verify whether the conversion process worked. You can also run a single iteration of the solver afterward and view the output solution file to visually verify that the mesh is ok.
|All times are GMT -4. The time now is 02:32.|