Skip to content

Cleaner formatting of Aviary warnings#789

Merged
jkirk5 merged 6 commits intoOpenMDAO:mainfrom
jkirk5:cleanup
Jun 13, 2025
Merged

Cleaner formatting of Aviary warnings#789
jkirk5 merged 6 commits intoOpenMDAO:mainfrom
jkirk5:cleanup

Conversation

@jkirk5
Copy link
Copy Markdown
Contributor

@jkirk5 jkirk5 commented Jun 5, 2025

Summary

Added custom formatting for warning messages Aviary produces based on verbosity level. Currently does not reformat warnings called by other modules, so migrating to a new system such as logging is the long-term solution. QUIET mode does suppress all warnings now though, regardless of which module called them.

New warning format:
Verbosity is 0 (QUIET): warnings are suppressed
Verbosity is 1 (BRIEF): Warning: <warning message> - example: Warning: Missing variable
Verbosity is 2 (VERBOSE): <warning_category>: <warning message> - example: UserWarning: Missing Variable
Verbosity is 3 (DEBUG): default warning message, which includes traceback to filename and line number where warning is triggered

Removed include_landing flag from level2 as it is redundant/conflicting with the already existing include_landing key in phase_info

Related Issues

  • Resolves #

Backwards incompatibilities

None

New Dependencies

None

@jkirk5 jkirk5 merged commit f0c7a5b into OpenMDAO:main Jun 13, 2025
6 checks passed
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.

1 participant