Yield usage metering
SunSolve Yield usage is metered in module years. One module year is the usage of simulating one simple module, at 1× fidelity, over one year of weather data. Your subscription includes an allowance of module years, and each simulation you run draws on it.
Usage formula
Section link: Usage formulaYield usage () is calculated for each simulation as:
where:
- is the number of modules in the unit system
- is the complexity multiplier applied when complex modules are used
- is the fidelity multiplier
- is the number of years, with and the number of weather timesteps in the simulated date range
The optical solve for each module is performed once, so complexity and fidelity are counted once, on the first year. Each additional year only repeats the electrical time-stepping, so it adds a flat one module year per module.
Usage inputs
Section link: Usage inputsComplexity multiplier, , for complex modules and for simple modules (for example a module loaded from a PAN file).
Fidelity multiplier, , / / / / as set by the fidelity level.
A module loaded from a SunSolve Power file is a complex module. A module loaded from a PAN file or datasheet is a simple module. See Module — Simple vs complex for how the two types differ.
The usage estimate in the yield calculator and the usage breakdown in your subscription transaction history list these same inputs, so you can check any usage against this formula.
Years and timestep cadence
Section link: Years and timestep cadenceA year is counted as timesteps, which is one leap year (366 days) of hourly data. Using a leap year rather than hours means that a full year of hourly data, leap year or not, always counts as a single year. Any part year is rounded up to a whole year.
counts timesteps, not hours. Weather data with a finer cadence therefore produces more years for the same date range:
Rounding
Section link: RoundingThe final result is rounded up to a whole number of module years. Rounding is applied to each simulation, so a simulation never uses less than one module year.
Analyses
Section link: AnalysesAn analysis runs several simulations, shown by the simulations required counter. Each simulation is metered separately using the formula above. When every simulation shares the same inputs, the analysis uses the number of simulations required multiplied by .
When the allowance runs out
Section link: When the allowance runs outA simulation will not start if your remaining module-year allowance is not enough to cover it. To run it, reduce its usage (for example by lowering the fidelity level, using a simple module or shortening the date range) or add module years to your subscription.
Each simulation in an analysis is checked against your remaining allowance separately. If the allowance runs out partway through an analysis, the simulations that have already run are still metered, and the remaining simulations will not start. Before running an analysis, check that your remaining allowance covers the full estimate shown in the yield calculator.
Worked examples
Section link: Worked examplesSimple module, one year of hourly weather
Section link: Simple module, one year of hourly weatherFor a simple module simulation with , , , and :
The simulation consumes module years.
Complex module, two years of hourly weather and higher fidelity
Section link: Complex module, two years of hourly weather and higher fidelityFor a complex module simulation with , , , and :
The simulation consumes module years.
Simple module, 15-minute weather data
Section link: Simple module, 15-minute weather dataFor a simple module simulation with , , , and one 365-day year of 15-minute data, :
The simulation consumes module years, four times the usage of the same simulation with hourly data.
Rounding at low fidelity
Section link: Rounding at low fidelityFor a simple module simulation with , , , and :
The simulation consumes module years.
Analysis
Section link: AnalysisAn analysis with simulations required, each matching the first example above, consumes module years.
See Yield simulation options for the fidelity settings that drive , and Analysis options for the simulations an analysis runs.