[bgulzar22]

I'm currently working on a Python script for setting customized boundary conditions in an SU2 simulation using the pysu2 module. I've encountered an issue where the simulation fails to run correctly, and I suspect it's related to how I'm handling marker IDs and setting custom temperatures.

Here's a summary of my setup:

I've defined markers in my SU2 configuration file (MARKER_ISOTHERMAL, MARKER_PYTHON_CUSTOM, etc.).
In my Python script, I retrieve the marker tags using GetMarkerTags() and then proceed to set custom temperatures using SetMarkerCustomTemperature().
However, when I run the simulation, I get errors like "The marker 'WALL' does not exist in the simulation" or similar messages for other markers.

I've double-checked my configuration file and script, and everything seems to align correctly. Could someone provide insights or suggestions on how to troubleshoot this issue? Are there common pitfalls or best practices when dealing with marker IDs and customized boundary conditions in SU2 using the pysu2 module?

I am attaching my mesh file , cfg file, PyScript and temperature file here in the link as well.
https://drive.google.com/drive/folde...usp=drive_link
Any help or guidance would be greatly appreciated!

[bgulzar22]

Any Ideas ?

[bgulzar22]

Originally Posted by bgulzar22

I'm currently working on a Python script for setting customized boundary conditions in an SU2 simulation using the pysu2 module. I've encountered an issue where the simulation fails to run correctly, and I suspect it's related to how I'm handling marker IDs and setting custom temperatures.

Here's a summary of my setup:

I've defined markers in my SU2 configuration file (MARKER_ISOTHERMAL, MARKER_PYTHON_CUSTOM, etc.).
In my Python script, I retrieve the marker tags using GetMarkerTags() and then proceed to set custom temperatures using SetMarkerCustomTemperature().
However, when I run the simulation, I get errors like "The marker 'WALL' does not exist in the simulation" or similar messages for other markers.

I've double-checked my configuration file and script, and everything seems to align correctly. Could someone provide insights or suggestions on how to troubleshoot this issue? Are there common pitfalls or best practices when dealing with marker IDs and customized boundary conditions in SU2 using the pysu2 module?

I am attaching my mesh file , cfg file, PyScript and temperature file here in the link as well.
https://drive.google.com/drive/folde...usp=drive_link
Any help or guidance would be greatly appreciated!

Can anyone provide any help , please.