Skip to content

Stop adding BUFFET_MONITORING to configs written by SU2_PY - #2905

Open
ManasBagul23 wants to merge 1 commit into
su2code:developfrom
ManasBagul23:fix-python-buffet-monitoring
Open

ManasBagul23 wants to merge 1 commit into
su2code:developfrom
ManasBagul23:fix-python-buffet-monitoring

Conversation

@ManasBagul23

Copy link
Copy Markdown

Proposed Changes

BUFFET_MONITORING was removed from CConfig and the buffet sensor is now always evaluated for viscous problems. read_config in SU2_PY/SU2/io/config.py still sets BUFFET_MONITORING= YES when BUFFET is an objective or constraint, and dump_config writes every key, so the config handed to SU2_CFD aborts with:

Line 61 BUFFET_MONITORING: invalid option name. Check current SU2 options in config_template.cfg.

Reproduced by loading a Navier-Stokes config with OPT_OBJECTIVE= BUFFET * 1.0 through SU2.io.Config, dumping it and running SU2_CFD -d on the result. With this change the dumped config parses.

Related Work

None.

PR Checklist

  • I am submitting my contribution to the develop branch.
  • My contribution generates no new compiler warnings (try with --warnlevel=3 when using meson).
  • My contribution is commented and consistent with SU2 style (https://su2code.github.io/docs_v7/Style-Guide/).
  • I used the pre-commit hook to prevent dirty commits and used pre-commit run --all to format old commits.
  • 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.

BUFFET_MONITORING was removed from CConfig, and the buffet sensor is now
always evaluated for viscous problems. read_config still set it to YES
whenever BUFFET was an objective or constraint, and dump_config writes
every key, so SU2_CFD aborted on the generated config with
"BUFFET_MONITORING: invalid option name".
Copilot AI lite review requested due to automatic review settings September 16, 2026 17:00

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

🟡 Changes recommended

The standard template can still cause invalid BUFFET_MONITORING output.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

This PR stops SU2_PY from adding the obsolete BUFFET_MONITORING option to generated configurations.

Changes:

  • Removes automatic insertion for buffet objectives and constraints.
  • The stale template option still needs removal or filtering.
File summaries
File Summary
SU2_PY/SU2/io/config.py Removes obsolete buffet-monitoring option generation.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 1
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment thread SU2_PY/SU2/io/config.py
if "BUFFET" in data_dict["OPT_OBJECTIVE"]:
data_dict["BUFFET_MONITORING"] = "YES"

# hack - twl

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

The stale BUFFET_MONITORING= NO line in config_template.cfg is removed in #2904, together with the other options that no longer parse.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants