Skip to content

Conversation

@TobiKattmann
Copy link
Contributor

@TobiKattmann TobiKattmann commented Nov 19, 2021

Hi,

Comp/Inc/Nemo output all had the same RMS_TKE etc output -> now this is done once in CFlowOutput and Comp/Inc/NemoOutput only call sth like SetHistoryOutput_Turb in their respective SetHistoryOutput.

this is just a cleanup and shouldnt change too much.

I do this in anticipation of addition of Species related output which I dont want to repeat. So #1388 will use the same concept

Related Work

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 the '-Wall -Wextra -Wno-unused-parameter -Wno-empty-body' compiler flags, or simply --warnlevel=2 when using meson).
  • My contribution is commented and consistent with SU2 style.
  • 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.

Comp/Inc/Nemo kept exactly the same output for Turb stuff in their
respective outputs. That is now collected and moved to the parent class.
I hope the accesses to the data is the same between the 3 classes ...
otherwise it wont work
One noticed small downside to this operation is that during the dry run
the turb quantities are written collectively close to the end when the
respective function is called. Before ALL the RMS_RES were listed close
to each other.
@TobiKattmann
Copy link
Contributor Author

TobiKattmann commented Nov 20, 2021

They are not, but I admit I like the residuals close to the residuals and the limiters close to the limiters

I fear, that also applies to the History output (Edit: Done in ff966f0 )

RMS_RES, MAX_RES, BGS_RES, TurbLINSOL are all written in separate
functions.
@pcarruscag
Copy link
Member

But that is processed in groups, it should not have the same problem 🤔

@TobiKattmann
Copy link
Contributor Author

But that is processed in groups, it should not have the same problem 🤔

I mean... it can still stay like that, or should I revert 😬

@pcarruscag
Copy link
Member

It's ok, I'll have a look today or tomorrow to see if there is some way to recover those precious deleted lines.

@TobiKattmann
Copy link
Contributor Author

Or I revert the History split-up and we call it a weekend

Copy link
Member

@pcarruscag pcarruscag left a comment

Choose a reason for hiding this comment

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

Registering the outputs defined the output order, but data can be loaded in any order.

Copy link
Contributor Author

@TobiKattmann TobiKattmann left a comment

Choose a reason for hiding this comment

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

Big Thanks for the extensive update and the research what actually matters for the order! And of course kudos for the additional 🔴 ;)

I have no more comments or updates to make, so in case you're good I guess we can merge

Comment on lines +647 to +649
case TURB_MODEL::NONE:
/*--- Early return if there is no turbulence model in use. ---*/
return;
Copy link
Contributor Author

Choose a reason for hiding this comment

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

nice 👍

@pcarruscag pcarruscag merged commit b140a4d into develop Nov 21, 2021
@pcarruscag pcarruscag deleted the consolidate_output branch November 21, 2021 22:46
@pr-triage pr-triage bot added the PR: merged label Nov 21, 2021
TobiKattmann added a commit that referenced this pull request Nov 22, 2021
A possible idea is to make a collected ScalarResidual etc ... as opposed
to a seperate SpeciesResidual and TurbResidual.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants