Do not ouptut individual load parameters if not in original network #112
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
wperkins
added
bug
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.
Merge request type
Relates to
This MR updates
Summary
Load shedding parameters can be individually by each load using the
mpc.loadcostfield in the MATPOWER network. These individual load loss parameters were added to the output even if they were never specified or used. This fixes that. Individual load shedding parameters are output only if they were read from the input network. Closes #109.If load shedding parameters are not read from the input network, they are initialized with the OPFLOW blanket cost (
-opflow_loadloss_penality), but only if needed (-opflow_include_loadloss_variables).