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

Allow specification of temperature profiles (x,y,z) at isothermal walls #1553

Closed
ChristianBauerEng opened this issue Mar 3, 2022 · 6 comments

Comments

@ChristianBauerEng
Copy link
Contributor

Is your feature request related to a problem? Please describe.
Under high aerothermal loads heat fluxes over walls are an important design aspect of many components. In my specific case a wall temperature distribution is known from experiments. I would like to apply this spacial temperature distribution as boundary condition to one or more isothermal walls. In my case the heat flux is then used for validation purposes.

Describe the solution you'd like
I would like to specify the temperature of an isothermal wall with respect to the x/y/z coordinate. I believe something similar is already possible with the structural load boundaries:
MARKER_DISPLACEMENT = (surface, multiplier, magnitude [m], x component, y component, z component)

For temperature this could possibly look like this:
MARKER_ISOTHERMAL_PROFILE = (surface, temperature[0...N], x[0...N], y[0...N],z[0...N])

In order to keep the config file cleaner a better solution may be to specify an external file, from which the locations and temperatures are read. This seems to be already possible for inlet boundaries:

SU2/config_template.cfg

Lines 812 to 816 in 72b2fa9

% Read inlet profile from a file (YES, NO) default: NO
SPECIFIED_INLET_PROFILE= NO
%
% File specifying inlet profile
INLET_FILENAME= inlet.dat

However, I could not find any example actually using this functionality. If this is implemented, extending the functionality to also work with isothermal walls is probably the least intrusive modification.

Describe alternatives you've considered
A possible, but cumbersome solution could be to split the respective walls into many markers and specify piecewise-constant wall temperatures for each marker.

@pcarruscag
Copy link
Member

This is already possible with the python wrapper, see testcases/py_wrapper/flatPlate_unsteady_CHT_FlatPlate.py
I am against adding any more "profile files" to SU2.

@ChristianBauerEng
Copy link
Contributor Author

I see. The python wrappers are far more powerful than I thought. But I'm still a bit lost with respect to the API of the driver(s). Where's a good place to start reading into that?

@pcarruscag
Copy link
Member

pcarruscag commented Mar 3, 2022

Sadly no, it is one of the main development areas we have identified in #1487, the interface is not very large, you can scroll over python_wrapper_structure.cpp to see the methods that allow modifying things at inputs, and the methods for control flow are in that example I pointed to.
If you join one of our dev meetings we can try to get a working example with what you need.
Wednesdays at 3pm UK - https://meet.jit.si/SU2_DevMeeting

@ChristianBauerEng
Copy link
Contributor Author

If you don't mind I'll leave this question open for now.
I'm planning to provide a simplified example setup later on, once I've had time to properly dive into the wrapper API.

@mutlu-celik
Copy link

I am trying to do the same thing for a loosely coupled cht problem. I have the wall temperature data but cannot implement it to SU2. I have checked the python wrapper code but I think it needs to be updated to be able to work as isothermal wall boundary condition with varying T through x coordinate(or any). Is there any progress about this issue?

@stale
Copy link

stale bot commented Nov 1, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If this is still a relevant issue please comment on it to restart the discussion. Thank you for your contributions.

@stale stale bot added the stale label Nov 2, 2022
@stale stale bot closed this as completed Nov 13, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants