Describe the bug
Since cc9e452, SU2_CFD writes the MAXIMUM_HEATFLUX history field with the header maxHF (and d[maxHF], tavg[maxHF], dtavg[maxHF] for the derived fields), but SU2_PY/SU2/io/historyMap.py expects MaxHF. read_history matches headers exactly, so MAXIMUM_HEATFLUX cannot be used as an objective or constraint from the Python scripts.
To Reproduce
Run TestCases/navierstokes/flatplate/lam_flatplate.cfg with HISTORY_OUTPUT= (ITER, RMS_RES, HEAT) for a few iterations, then
import SU2
h = SU2.io.read_history("history.csv")
print("TOTAL_HEATFLUX" in h, "MAXIMUM_HEATFLUX" in h)
prints True False.
Expected behavior
MAXIMUM_HEATFLUX is found like TOTAL_HEATFLUX.
A fix is proposed in #2906.
Bug report checklist
Desktop (please complete the following information):
- OS: Windows 11
- C++ compiler and version: MSVC 19.44 (Visual Studio 2022 Build Tools)
- MPI implementation and version: Microsoft MPI 10.1
- SU2 Version: develop
Describe the bug
Since cc9e452,
SU2_CFDwrites theMAXIMUM_HEATFLUXhistory field with the headermaxHF(andd[maxHF],tavg[maxHF],dtavg[maxHF]for the derived fields), butSU2_PY/SU2/io/historyMap.pyexpectsMaxHF.read_historymatches headers exactly, soMAXIMUM_HEATFLUXcannot be used as an objective or constraint from the Python scripts.To Reproduce
Run
TestCases/navierstokes/flatplate/lam_flatplate.cfgwithHISTORY_OUTPUT= (ITER, RMS_RES, HEAT)for a few iterations, thenprints
True False.Expected behavior
MAXIMUM_HEATFLUXis found likeTOTAL_HEATFLUX.A fix is proposed in #2906.
Bug report checklist
Desktop (please complete the following information):