Open
Conversation
Rename function and add note on side-effects.
Portfolio assessments won't have a `--demandFile` assignment, because the individual demand files will be provided in the configuration file.
- Define test-case inputs. Will only include two buildings to keep the problem size manageable and ease validation. - We'll use two HAZUS earthquake fragility curves. One should require auto-population, the other not, to cover both cases. Using available configuration files from the existing examples.
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
1 participant
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.
Portfolio Assessment
This PR is a first attempt to expand the capability of the command line approach to running an assessment, to be able to analyze multiple assets collectively in a single assessment while still being able to auto-populate configuration entries as done previously.
The commits contain a partial implementation, which needs to be reviewed and updated based on feedback before moving on, to minimize backtracking. Here is what is implemented so far:
pelicuncommand as before, but pass a specially formatted configuration file.AIM.jsonfiles, those that were typically used for a single assessment. It also identifies theresponse.csvfile containing demands.AIM.jsonfiles should be auto-populated. This restriction confines the input space and reduces the need to validate the compatibility of all individual configuration files.AIM.jsonfiles, merges the component assignment files and runs the assessment.We would need to discuss the format of the outputs.