[Ruchi]

Hi Guys,

whenever i try to run the simulation using rotating mesh i get stuck at the following point:

------------------------------ Begin Solver -----------------------------

Setting rotating frame grid velocities for zone 0.
Rotational origin (x, y, z): ( 0, 0, 0 )
Angular velocity about x, y, z axes: ( 0, 0, -10 ) rad/s
[ruchitas-MBP:51188] *** Process received signal ***
[ruchitas-MBP:51188] Signal: Segmentation fault: 11 (11)
[ruchitas-MBP:51188] Signal code: Address not mapped (1)
[ruchitas-MBP:51188] Failing at address: 0x15795
[ruchitas-MBP:51188] *** End of error message ***
Segmentation fault: 11

P.s.: everything runs well with stationary mesh but with rotating there is a problem. please help!

[hlk]

Originally Posted by Ruchi

Hi Guys,

whenever i try to run the simulation using rotating mesh i get stuck at the following point:

------------------------------ Begin Solver -----------------------------

Setting rotating frame grid velocities for zone 0.
Rotational origin (x, y, z): ( 0, 0, 0 )
Angular velocity about x, y, z axes: ( 0, 0, -10 ) rad/s
[ruchitas-MBP:51188] *** Process received signal ***
[ruchitas-MBP:51188] Signal: Segmentation fault: 11 (11)
[ruchitas-MBP:51188] Signal code: Address not mapped (1)
[ruchitas-MBP:51188] Failing at address: 0x15795
[ruchitas-MBP:51188] *** End of error message ***
Segmentation fault: 11

P.s.: everything runs well with stationary mesh but with rotating there is a problem. please help!

Thanks for your question.

Are you able to run the rotating example(s) from the TestCases folder? Note that the mesh files for the testcases are in a separate repository (as described here: https://github.com/su2code/SU2/wiki/Test-Cases).

I am able to run the rotating examples provided in the TestCases, so this problem may be due to some option not being set in your config file. Of course it would be preferable if there were a helpful error message, but you may be able to get somewhere by comparing your config file to the config files provided in the TestCases, and seeing if there is some option that has not been set.
If you do find that fixes the problem, please respond here with which option(s) helped - that information would go a long way towards hunting down a good place to provide some more error checking on rotating cases to prevent this problem.