Power usage metering
SunSolve Power usage is metered in rays, shown as Rays (M) for millions of rays. Your subscription includes an allowance of rays, and each simulation you run draws on it. One usage unit is one million rays traced, so a simulation that traces rays uses Rays (M).
Usage formula
Section link: Usage formulaThe usage estimate shown in the simulation bar is calculated from the inputs of the simulation before it runs. Usage () is calculated as:
where:
- is the number of rays per run
- is the number of runs in the simulation, which depends on the solving mode
A single-solution simulation contains one run, so . Sweeps and optimisations are described below.
Usage inputs
Section link: Usage inputsRays per run, , Rays traced in each run. Set on the Options tab as Rays per run (see Simulation options).
The usage breakdown lists these same inputs, so you can check any estimate against this formula.
Sweeps
Section link: SweepsIn a sweep, each combination of swept values is one run. The number of runs is the product of the steps in each depth that has at least one swept input:
If only one depth is swept, is the number of steps on that depth. A sweep with no swept inputs counts as a single run, and the usage per simulation is .
Optimisations
Section link: OptimisationsAn optimisation runs in generations, and the usage estimate is an upper bound. It is shown as “up to” the estimated usage. The first generation contains runs or runs, whichever is higher, where is the number of grid points per optimised input: for two inputs, for three inputs, and otherwise. The first generation count is:
The maximum usage is then:
The first generation always runs in full, so when is higher than the run limit , the estimate uses runs. Later generations never exceed the run limit. The optimiser can also stop earlier, see Termination conditions, so actual usage is usually lower than the estimate.
Worked examples
Section link: Worked examplesSingle run
Section link: Single runFor a single-solution simulation with and :
The simulation uses Rays (M).
Sweep
Section link: SweepFor a sweep with primary steps, secondary steps, and :
The sweep uses Rays (M), which is Rays (M) per run across runs.
Optimisation with a run limit above the first generation
Section link: Optimisation with a run limit above the first generationFor an optimisation of two inputs with , , and :
The estimate is up to Rays (M).
Optimisation with a first generation above the run limit
Section link: Optimisation with a first generation above the run limitFor the same optimisation with :
The first generation runs in full, so the estimate is up to Rays (M), not Rays (M).
See Simulation options for the ray tracer settings, and Ray count and stochastic error for how the number of rays affects results.