What upgrade outputs get delivered to URBANopt?

daniel-thom commented 2 years ago

The current plan is to deliver upgrade_summary.json back to URBANopt. It has summary information of violations and costs.

We are also planning to report locations of DISCO-generated .dss files that define the upgraded network, which will allow users to load the new network in OpenDSS.

The following files have information that is potentially interesting to end users. Do we want to do anything with these other than leave them in the output directory?

feeder_stats.json
VoltageUpgrades/voltage_upgrades.json
ThermalUpgrades/transformer_upgrades.json
ThermalUpgrades/line_upgrades.json
UpgradeCosts/thermal_upgrade_costs.json
UpgradeCosts/voltage_upgrade_costs.json

daniel-thom commented 2 years ago

Action: Sherin to discuss with Tarek.

ann-sherin commented 2 years ago

Have a json file that is succinct

header names: equipment_type, equipment_name, status, cost, parameter1_name, parameter1_original, parameter1_upgraded, parameter2_name, parameter2_original, parameter2_upgraded

Status can have values: unchanged, replaced, new, setting_changed

flat array: each object would be a dictionary {'objects': [ ] }

example object entry: equipment_type: xfmr, equipment_name: 123, status: replaced, cost: 1000, parameter1_name: kVA, parameter1_original: 25, parameter1_upgraded:75

NREL / disco

What upgrade outputs get delivered to URBANopt? #127