You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've got a question regarding the usage of SU2_DEF when a prescribed displacement of the surface mesh is assigned.
I saw people using it for 3D cases, where a .dat file containing the new boundary coordinates is parsed to the solver through the configuration file. I tried exactly the same approach for a 2D cases (just an aerofoil being morphed my my own code), with same syntax for the boundary file but weirdly something is not working with all of the coordinates being brought to zero expect for two points (which should be leading and trailing edge) which are moved outside the farfield region.
Is there any difference way in using SU2_DEF between 2D and 3D cases?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello SU2 developers,
I've got a question regarding the usage of SU2_DEF when a prescribed displacement of the surface mesh is assigned.
I saw people using it for 3D cases, where a .dat file containing the new boundary coordinates is parsed to the solver through the configuration file. I tried exactly the same approach for a 2D cases (just an aerofoil being morphed my my own code), with same syntax for the boundary file but weirdly something is not working with all of the coordinates being brought to zero expect for two points (which should be leading and trailing edge) which are moved outside the farfield region.
Is there any difference way in using SU2_DEF between 2D and 3D cases?
Many thanks
Beta Was this translation helpful? Give feedback.
All reactions