Data structures in Julia to enable power systems analysis. Part of the Scalable Integrated Infrastructure Planning Initiative at the National Renewable Energy Lab.
CostCurve and FuelCurve keep track of power_units::UnitSystem. Also, FuelCurve has a fuel_cost, which is sometimes a scalar. It would be useful to have built-in support for
Conversion of CostCurves and FuelCurves from one UnitSystem to another
Conversion from FuelCurve to CostCurve if the fuel_cost is scalar
as we are currently doing both of these things manually ad hoc.
For 1, an easy approach would involve a function that takes the CostCurve/FuelCurve, the desired units, and a component reference or some other way to look up the relevant conversion factors. That might be a good first issue. Depending on how https://github.com/NREL-Sienna/PowerSystems.jl/issues/1134 is resolved, a cleaner solution might be possible later.
For 2, the converter function (or overloaded constructor — CostCurve(fuel_curve)) is trivial, also a good first issue.
CostCurveandFuelCurvekeep track ofpower_units::UnitSystem. Also,FuelCurvehas afuel_cost, which is sometimes a scalar. It would be useful to have built-in support forCostCurves andFuelCurves from oneUnitSystemto anotherFuelCurvetoCostCurveif thefuel_costis scalaras we are currently doing both of these things manually ad hoc.
For 1, an easy approach would involve a function that takes the
CostCurve/FuelCurve, the desired units, and a component reference or some other way to look up the relevant conversion factors. That might be agood first issue. Depending on how https://github.com/NREL-Sienna/PowerSystems.jl/issues/1134 is resolved, a cleaner solution might be possible later.For 2, the converter function (or overloaded constructor —
CostCurve(fuel_curve)) is trivial, also agood first issue.