Nodal: Lack of Zonal Reporting
Q: Why don’t I get some zonal output reporting when running a nodal study?
Prior to v12.2, a nodal study in Aurora would report zonal and nodal output tables but the data was quite literally apples and oranges. The zonal output was a result of nodal commitment but zonal dispatch. If you ran just the zonal study, and compared the zonal output tables to the same zonal tables as a result of a nodal study, you would see differences. That was rather confusing so we removed the zonal-only table types from the output.
When we added the new Solution Method of Angles, and later an updated Shift Factor method, we then had a single foundation for both zonal and nodal such that all the constraints modeled (emissions, fuel, etc.) on the zonal side translated over to the nodal solution. As such, some traditionally zonal-type output tables like Resources, Resource Groups, etc., will produce output but will contain data that specifically pertains to the nodal solution. This removes the confusion where previously output tables like Resources would report output of the zonal dispatch while NodalGen output would report the nodal dispatch.
If you want to get zonal prices, e.g., Zone output tables, then disable the nodal and run a zonal only study.
If you want to model a single market as a zonal-only (e.g. Ontario) and others as a full nodal, then do not monitor any branches in Ontario, except for the interconnection branches, and you will have a “hybrid” model.
| Output Tables Not Reported | “Zonal” Output Tables Reporting Nodal Results |
|
FuelbyZone Hub Link MultiLink Pool Zone ZoneEmissions |
Fuel Resource ResourceEmissions ResourceGroup ResourceGroupEmissions |
Nodal: Lack of Zonal Reporting
