I was not aware of this issue but I can see how this situation may have arisen. I am cc’ing Giacomo/Ganlin to see if they has a quick suggestion. What I would expect we need to do is to introduce the ability to read t_wall through the user-defined tag on the boundary condition and then use this value to see the internal value. I do not think there should be much more that is require than that.

Spencer Sherwin FREng, FRAeS
Head of Aerodynamics Section,
Director of Research Computing Service,
Professor of Computational Fluid Mechanics,
Department of Aeronautics,
South Kensington Campus,

Imperial College London, SW7 2AZ, UK
Phone: +44 (0)20 7594 5052

http://www.imperial.ac.uk/people/s.sherwin/

On 13 Aug 2020, at 02:14, Wang, Zhicheng <zhicheng_wang@brown.edu> wrote:

This email from zhicheng_wang@brown.edu originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list to disable email stamping for this address.

Dear Nektar++ users,

I'm using the CompressibleFlowSolver to simulate nitrogen flow in a square cavity, where there are two isothermal walls with different temperatures, and the rest of the walls are adiabatic. After looking into the manual for quite a while, my understanding is that the wall temperature is uniquely defined by parameter "Twall", there is no straightforward way to set up a different wall temperature in the parameter file. Has anyone run into the same issue before ? Can you give a hint how to implement this?

Best regards

Zhicheng Wang

_______________________________________________
Nektar-users mailing list
Nektar-users@imperial.ac.uk
https://mailman.ic.ac.uk/mailman/listinfo/nektar-users