Repository navigation
Add sensitivity-weighted distance option to local_weighted POD - #30
Merged
Merged
Conversation
This file contains hidden or 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.
This PR adds a sensitivity-weighted distance option to the local_weighted POD model. The underlying idea is that each design variable affects the solution state to different extents. Therefore taking the raw distances in the parameter space for local_weighted POD does not accurately reflect what is happening to the solution state under the hood. We can approximate the state sensitivity w.r.t. the design variables by instead using the sensitivities of the outputs. These are already being computed, and provide us some form of output-oriented distance measure.
Changes (Check all boxes that apply)