Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Fix #2203: Improve Spanwise Section Error Handling in Turbomachinery Simulations#2459

Open
aryan0931 wants to merge1 commit intosu2code:develop
base:develop
Choose a base branch
Loading
fromaryan0931:develop

Conversation

aryan0931
Copy link

@aryan0931aryan0931 commentedMar 3, 2025
edited
Loading

Proposed Changes

Fixes:#2203
This PR aims to:

This PR improves error messages for spanwise section calculations in turbomachinery simulations, addressing user experience

Related Work

Fixes#2203 : Wrong spanwise sections calculation in Turbomachinery simulation.

PR Checklist

Put an X by all that apply. You can fill this out after submitting the PR. If you have any questions, don't hesitate to ask! We want to help. These are a guide for you to know what the reviewers will be looking for in your contribution.

  • I am submitting my contribution to the develop branch.
  • My contribution generates no new compiler warnings (try with --warnlevel=3 when using meson).
  • My contribution is commented and consistent with SU2 style (https://su2code.github.io/docs_v7/Style-Guide/).
  • I used the pre-commit hook to prevent dirty commits and usedpre-commit run --all to format old commits.
  • I have added a test case that demonstrates my contribution, if necessary.
  • I have updated appropriate documentation (Tutorials, Docs Page, config_template.cpp), if necessary.

@joshkellyjak
Copy link
Contributor

This doesn't fix issue#2203 in that the issue of incorrectly determining calculating the spanwise boundary happens because of a bug in SU2, the mesh that is used in this issue is probably fine. I have also encountered this issue and checked the CGNS mesh and it is not malformed. All this PR does is add an additional error catch, please update the description to remove the fix.

@@ -4974,6 +4974,13 @@
max = 0;
SU2_MPI::Allreduce(&MyMin, &min, 1, MPI_DOUBLE, MPI_MIN, SU2_MPI::GetComm());
SU2_MPI::Allreduce(&MyMax, &max, 1, MPI_DOUBLE, MPI_MAX, SU2_MPI::GetComm());
if (nSpan < 2) {

Check warning

Code scanning / CodeQL

Comparison result is always the same Warning

Comparison is always true because nSpan <= 0.
". Found " + to_string(nSpan) + " nodes along the periodic boundary edge from hub to shroud. " +
"At least 2 nodes are required. Check your mesh for correct hub-to-shroud edge definition.",
CURRENT_FUNCTION);
}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This is in the equispaced section of the if statement, it should go with the other error message and run if the automatic section fails to calculate any value of nSpanWiseSections in three dimensions, i.e.

(nSpanWiseSections[INFLOW - 1] == 0 || nSpanWiseSections[OUTFLOW -1] == 0)

buf,
CURRENT_FUNCTION);
string("Turbomachinery simulation requires equal spanwise sections at INFLOW and OUTFLOW. ") + buf +
"\nThis is likely a mesh issue. Ensure that the periodic boundaries from hub to shroud are consistently defined in the mesh.",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

This is not likely a mesh issue, it is a mesh issue!

@aryan0931
Copy link
Author

Thank you sir for review I will do the respective changes as soon as possible.

Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Reviewers

@joshkellyjakjoshkellyjakjoshkellyjak left review comments

At least 1 approving review is required to merge this pull request.

Assignees

@joshkellyjakjoshkellyjak

Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

3 participants
@aryan0931@joshkellyjak@pcarruscag

[8]ページ先頭

©2009-2025 Movatter.jp