New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Added release notes for 3.31.0 #3138
Conversation
|
||
- Renamed `list_problem_vars` to `list_driver_vars` [#3132](https://github.com/OpenMDAO/OpenMDAO/pull/3132) | ||
|
||
## Backwards Incompatible API Changes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comment regarding PR #3113
- Renamed `list_problem_vars` to `list_driver_vars` [#3132](https://github.com/OpenMDAO/OpenMDAO/pull/3132) | ||
|
||
## Backwards Incompatible API Changes | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The automatic determination of derivative 'mode' is now done separately for the driver vs. a direct call to compute_totals or check_totals with a set of 'of' and 'wrt' variables that differ from the driver responses and design variables. This can modify the keys in the dict return value of check_totals, where for example the dict used to contain a 'J_fwd' key because it ran in fwd mode, it might now contain a 'J_rev' key instead because the best derivative mode was determined to be 'rev' based on the relative sizes of the 'of' and 'wrt' variables passed to check_totals.
Summary
Added release notes for upcoming 3.31.0 release.
Related Issues
None
Backwards incompatibilities
None
New Dependencies
None