You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
MMSA Testbed example 2 (MMSA: Seismic Functionality and Restoration Analysis for Interdependent Buildings-Water-Power using Restoration Curves) uses local input files that are included in the zip - this should be replaced with IN-CORE datasets.
The text was updated successfully, but these errors were encountered:
Sent the following email to John, Paolo and Milad:
We are trying to update the MMSA example notebooks that you contributed to IN-CORE and we need your help to confirm the best data to use for the water network for both notebooks.
In the MMSA notebook contributed by Paolo’s group, an IN-CORE water network dataset on the IN-CORE service is being used. In the notebook contributed by Milad, local shapefiles are being used for the water network that are based on the same files in the water network dataset used in the other notebook. When comparing the local shapefiles with the shapefiles on the IN-CORE service, there are two notable differences and we would like to use the best available data for both notebooks.
The two differences we found are:
The pipeline shapefiles both have the same geometry, but the local shapefile has an updated "direction" attribute for some of the pipes.
The water facility shapefiles also both have the same geometry, but the local shapefile has an updated facility type field. The dataset files on the service have some of the points marked as Junction and the local shapefile has them marked as PSTAS for the same GUID/location.
The potential solutions to this are:
Merge the changes from the local datasets into the existing network dataset we have on the service so we have a single network dataset used by both notebooks
Create a new water network dataset from the local files with a good description so it’s clear to why there are two water network datasets.
Would someone be able to help review these differences and determine what is the best approach?
Both notebooks use the same power network so Milad's MMSA can remove the local EPN files. Also the interdependency csv can be converted to JSON and uploaded to IN-CORE.
MMSA Testbed example 2 (MMSA: Seismic Functionality and Restoration Analysis for Interdependent Buildings-Water-Power using Restoration Curves) uses local input files that are included in the zip - this should be replaced with IN-CORE datasets.
The text was updated successfully, but these errors were encountered: