Overhaul resilientCommunity and restoration to create and use custom metric Outage Impact Potential (OIP) instead of SVI for greater customization by users #459
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
…l equipment lifetime testfile
…ons in getPowerMeasures() more explicit instead of relying on truthiness
…re readability and easier addition of new file inputs.
…ine with equipment BCS calculation
…nge min value for avgPeakDemand input from 0 to 0.01
…le impact metric called Outage Impact Potential
…th num entry fields for the weight of each contributing variable. Add additional error checking. Correct the name of formerly 'per capita income' variable to 'Avg Aggregate Household Income'
…d from analysis because of 'Not Applicable' data value.
…d readable by replacing repeated elementes with jinja loops
…nctions to ease development and declutter the namespace: reorder and label functions based on usage; remove deprecated functions getCoopData(), getCoopFromList(), coopvcensusDF(), and getAverages_loads(); remove too-short functions createDF and createGeoDF in favor of writing their contents where previously called
…P) instead of SVI and reorganize code for ease of understanding and development
…ty in response to the OIP update for resilientCommunity: make restoration no longer call resilientCommunity directly but instead take output from that model as input. Also add new testfiles for better demo.
…nal" for LCI & LCS metrics.
dpinney-nreca
approved these changes
Nov 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Overhaul resilientCommunity to create and use OIP instead of SVI and subsequently replace CCS/CCI with LCS/LCI (C=Community, L=Locational).
Overhaul how restoration interacts with the outputs from resilientCommunity in turn.