SOC Criticality Test Calculator

Evaluate event sizes for scale-free power-law behavior quickly. Estimate threshold, exponent, and uncertainty from data. Validate fit using resampled statistics, then interpret criticality evidence.

Calculator Inputs
Examples: avalanche sizes, burst energies, slip areas, acoustic emission energies.
Tail must contain at least this many points.
Use 500–2000 for stronger p-values.
Often 0.05 or 0.10 in practice.
Heuristic bounds, adjust for your system.
Formula Used

Assume the tail follows a continuous power law for x \ge x_{min}:

Maximum-likelihood estimate of the exponent using tail data x_i \ge x_{min}:

\alpha = 1 + \dfrac{n}{\sum_{i=1}^{n} \ln\left(\dfrac{x_i}{x_{min}}\right)}

We select x_{min} by scanning candidates and minimizing the Kolmogorov–Smirnov distance:

D = \max_x |F_{emp}(x) - F_{model}(x)|

The p-value is computed by generating synthetic power-law samples, refitting, and counting how often simulated KS distances exceed the empirical one.

How to Use This Calculator
  1. Collect a list of positive event sizes from your system.
  2. Paste values into the data box using any separators.
  3. Set a minimum tail size to avoid tiny tails.
  4. Choose bootstrap iterations; higher improves reliability.
  5. Click compute and review exponent, KS, and p-value.
  6. Use the CSV or PDF buttons to export results.
Example Data Table
Run Event size (x) Notes
13Small burst
25Moderate burst
38Moderate burst
413Larger event
521Tail candidate
634Tail candidate
755Extreme-like
889Extreme-like
Replace this with measured avalanche sizes, energy releases, or burst areas.
FAQs

1) What does this test actually tell me?

It checks whether the tail of your event sizes is statistically consistent with a power law. A good p-value supports the model, but it does not prove self-organized criticality.

2) Why do we estimate an xmin threshold?

Real data rarely follows a power law at small sizes. The threshold isolates the scaling region, reducing bias from detection limits, discreteness, and noncritical mechanisms.

3) What p-value should I consider “good”?

A common practice is p ≥ 0.10 to avoid false rejections in small samples. Some studies use 0.05. Interpret p together with diagnostics and domain knowledge.

4) How many events do I need for reliable results?

More is better. Hundreds to thousands of events improve stability, especially for bootstrapping. With very small datasets, xmin selection and alpha estimates can vary widely.

5) Can discrete data use this calculator?

It can still provide a useful approximation, but discrete power-law fitting is more exact for integer counts. If your sizes are strictly integer, consider dedicated discrete models too.

6) Does a power law automatically mean SOC?

No. Many mechanisms produce heavy tails. SOC claims usually require additional signatures like finite-size scaling, avalanche shape collapse, time correlations, and robustness across conditions.

7) Why might the calculator reject a power law?

Rejection can come from mixed regimes, censoring, limited dynamic range, or alternative tails like lognormal or stretched exponential. Improve preprocessing and compare competing models.

Related Calculators

Network degree calculatorAverage path length calculatorClustering coefficient calculatorBetweenness centrality calculatorCloseness centrality calculatorEigenvector centrality calculatorPageRank score calculatorKatz centrality calculatorAssortativity coefficient calculatorModularity score calculator

Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.