Specify mode for tests that check derivatives #49
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As of OpenMDAO/OpenMDAO#3142, the optimal deriv direction (assuming the user doesn't specify mode manually) is now determined separately for the driver and for any
compute_totalscalls that don't use the driver's design vars and responses asofandwrt. (The optimal direction is determined by the relative sizes of the ofs vs the wrts. If ofs are smaller, fwd mode is used, else rev mode.)Since these tests don't invoke a Driver, we specify the direction as
fwdduringsetupso we get the expected keys fromcheck_totals.