Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Symmetry boundary condition is not equivalent to full model #1723

Closed
rois1995 opened this issue Jul 25, 2022 · 4 comments · Fixed by #2194
Closed

Symmetry boundary condition is not equivalent to full model #1723

rois1995 opened this issue Jul 25, 2022 · 4 comments · Fixed by #2194

Comments

@rois1995
Copy link
Contributor

Describe the bug
Symmetry boundary condition does not work properly. In particular, the values on the symmetry plane are wrong with respect to a computation performed on the complete mesh. In the images you can see the pressure coefficient and the skin friction coefficient magnitude for both the simulations. For each image, the upper half is the solution on the complete mesh whereas the lower portion is the solution on the halved mesh with the symmetry plane. I am performing an incompressible RANS simulation with SST turbulence model. I am attaching the files needed to perform both the simulations. The branch I used is the develop one. I also tried with the main branch but the error persists.

PressureCoefficient
SFC_Error

To Reproduce
Please find the config and mesh file at the following link.

https://we.tl/t-nmjBv7HJv0

Desktop (please complete the following information):

  • OS: CentOS Linux release 7.6.1810 (Core)
  • C++ compiler and version: gcc 11.2.0
  • MPI implementation and version: OpenMPI 4.0.1
  • SU2 Version: v7.3.1
@rois1995 rois1995 added the bug label Jul 25, 2022
@pcarruscag
Copy link
Member

How many of orders of magnitude are the residuals dropping? And have you tried SA instead of SST?

@rois1995
Copy link
Contributor Author

How many of orders of magnitude are the residuals dropping? And have you tried SA instead of SST?

Residuals drop down by roughly 5 orders of magnitude across the board. I have just tried with SA and the results are the same. I am running a second order starting from a restart of a first order. I can send you a link with all of the results if needed.

@pcarruscag
Copy link
Member

In a vertex centered code it is not trivial to make a symmetry plane perfectly equivalent to the full model. We are computing fluxes for an edge that does not exist in the full model.
Can you try reducing the grid spacing in the normal direction, close to the plane? Or just compare results on globally-refined meshes?
The implementation could certainly be better, for numerous reasons #1125 #1373, but I don't think this particular issue is a bug.
Nevertheless, if you have time to obtain the results above it would help with characterizing the limitations a bit better.

@pcarruscag pcarruscag changed the title Symmetry boundary condition problem Symmetry boundary condition is not equivalent to full model Jul 28, 2022
@rois1995
Copy link
Contributor Author

rois1995 commented Aug 3, 2022

I tried reducing the grid spacing both in normal and in tangential direction to the symmetry plane. It seems that acting only on the tangential direction only worsen the results. The first image reflects this behavior. The upper half is the refined one, whereas the lower one is the reference half mesh solution.

TangRef

Reducing normal spacing, instead, greatly improves the results, but still, the contours of pressure coefficient are not the same wrt the mesh without symmetry plane. This can be seen from the second image, where on the bottom there is the solution on the refined mesh, whereas on the top there is the solution on the whole mesh.

NormRef

I might try further refining along the normal direction to check whether I can reach or not the reference solution.

@stale stale bot added the stale label Nov 2, 2022
@pcarruscag pcarruscag removed the stale label Nov 2, 2022
@su2code su2code deleted a comment from stale bot Nov 2, 2022
@stale stale bot added the stale label Jan 7, 2023
@pcarruscag pcarruscag removed the stale label Jan 7, 2023
@su2code su2code deleted a comment from stale bot Jan 7, 2023
@bigfooted bigfooted linked a pull request Apr 3, 2024 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants