Skip to main content
Nodal Data provides detailed, timestep-by-timestep results from PlantPredict energy predictions. These CSV-format exports contain the intermediate and final calculation results at each hierarchical level of a power plant, enabling users to verify, validate, and understand prediction results at different nodes in the calculation chain.

​
Nodal Data Hierarchy

PlantPredict organizes power plant modeling in a hierarchical structure, and Nodal Data exports are available at each level:
  1. DC Field - The most granular level containing module-level irradiance processing, temperature calculations, and DC power output for a group of modules with identical characteristics feeding a single inverter input.
  2. Inverter - Aggregates DC Field outputs and calculates inverter behavior including efficiency, operating regions, voltage/current characteristics, and AC power output.
  3. Array - Combines inverter outputs with AC collection system losses, auxiliary loads, degradation, and transformer losses at the array level.
  4. Block - Aggregates array outputs to represent a logical grouping of arrays within the power plant.
  5. System - The highest level containing site-wide meteorological data, solar geometry, horizontal irradiance processing, and plant-level losses including HV transformers and transmission lines.
  6. Storage - When energy storage is included, provides battery state of charge, charge/discharge power, efficiency losses, and dispatch algorithm results.

​
Enabling Nodal Data Export

Nodal Data must be enabled by the user before running a prediction. Once enabled, the detailed timestep data will be available for download after the prediction completes. Users can select which hierarchical levels to export based on their analysis needs.

​
Using Nodal Data

Nodal Data exports are commonly used for:
  • Validating prediction results against measured data
  • Understanding loss contributions at each stage of the calculation
  • Debugging unexpected prediction results
  • Performing detailed technical due diligence
  • Comparing model behavior across different configurations