Grid Convergence Calculator

Check numerical accuracy across three refined grids quickly. Compute order, extrapolation, and uncertainty with clarity. Export results, compare cases, and document your simulations today.

Inputs

Provide three grid spacings and the computed scalar quantity on each grid. The calculator will auto-order grids from fine to coarse.

Used in exports.
Smaller h means finer grid.
Typically h2 ≈ r·h1.
Largest spacing.
Scalar output at h1.
Scalar output at h2.
Scalar output at h3.
Often 1.25 for three grids.
Reset

Convergence preview

Submit inputs to generate an interactive convergence plot. A preview appears here using example values.

Example dataset

This sample resembles a refined simulation where the monitored quantity stabilizes as the grid is refined.

Grid level Grid spacing (h) Quantity (φ) Typical interpretation
Fine0.0101.2384Closest to grid-independent value
Medium0.0141.2310Intermediate resolution
Coarse0.0201.2195Higher discretization error

Formula used

Refinement ratios
For fine (1), medium (2), coarse (3):
  • r21 = h2 / h1
  • r32 = h3 / h2
Apparent order
The apparent order p is estimated iteratively from the three solutions using a common grid-convergence scheme. This captures how the error scales with grid spacing.
Richardson extrapolation
Extrapolated value as the grid spacing approaches zero:
  • φ_ext,21 = φ1 + (φ1 − φ2) / (r21^p − 1)
Grid Convergence Index (GCI)
Estimated discretization uncertainty (reported as %):
  • e_a21 = |(φ1 − φ2) / φ1|
  • GCI21 = F_s · e_a21 / (r21^p − 1)
  • GCI32 = F_s · e_a32 / (r32^p − 1)

How to use this calculator

  1. Run your simulation on three systematically refined grids.
  2. Record a representative grid spacing for each grid (h1, h2, h3).
  3. Enter the same scalar output (φ) measured on each grid.
  4. Press Submit to compute order, extrapolation, and GCI.
  5. Use Download CSV or Download PDF to attach results to reports.

Why grid convergence matters in simulations

Discretization error can dominate total numerical uncertainty. A three-grid study gives evidence of grid independence. Many CFD and FEA teams report GCI to support decisions. Small GCI values reduce risk in design and validation.

Three-grid data you should collect

Record a representative spacing for each grid level. Use consistent physics settings and solver tolerances. Track one scalar output, like drag or peak stress. Save h1, h2, h3 and φ1, φ2, φ3 for each case.

Apparent order improves interpretation

Apparent order p describes how fast the solution converges. Higher p often indicates cleaner asymptotic behavior. Many second-order schemes approach p near 2 in smooth regions. Low p can suggest under-resolution or inconsistent numerics.

GCI turns differences into uncertainty

GCI converts the fine-medium difference into a defensible uncertainty. It scales with the safety factor and refinement ratio. Engineers commonly start with Fs = 1.25 for three grids. Report GCI21 as a percent next to the final predicted value.

Choosing refinement ratios with practical limits

Many studies target r near 1.3 to 2.0 per refinement. Larger r increases separation but may waste coarse resources. Smaller r reduces signal and can hide convergence trends. Keep geometry and boundary layers consistent across grids.

How to report results for stakeholders

Present φ1 with GCI21 as the numerical uncertainty band. Include p, r21, and the extrapolated value for transparency. Add a short table and a convergence plot for readability. Store exports in your project folder for auditing.

FAQs

1) What is a good GCI21 value?

It depends on your acceptance criteria and physics sensitivity. Many teams aim for below 1% for key outputs. Use the same threshold across comparable cases. Always report the value, not just a pass label.

2) Do I need equal refinement ratios?

Equal ratios help, but the method can handle different ratios. Large differences can reduce stability in the order estimate. Try to keep r21 and r32 reasonably close. Consistency improves comparison across projects.

3) Why does the calculator reorder my grids?

The method assumes a clear fine, medium, and coarse sequence. Reordering prevents mistakes when inputs are swapped. The smallest h becomes the fine grid automatically. Your φ values move with their corresponding h values.

4) What if my solution is not monotonic?

Non-monotonic behavior can occur with complex numerics. The apparent order may become unstable or low. Try improving solver convergence and using better refinement. You may also monitor a different, smoother output quantity.

5) Can I use this for time step convergence?

Yes, treat h as the time step Δt instead of grid spacing. Use three refined time steps with the same setup. Interpret the results as temporal discretization uncertainty. Ensure the simulation reaches comparable physical time states.

6) Why can’t extrapolation use h = 0 on the plot?

Log axes cannot display zero. The plot uses a very small positive h for the extrapolated marker. The extrapolated value still represents the zero-spacing limit. Use the numeric table for exact reporting.

Built for engineering-grade reporting and repeatable workflows.

Related Calculators

markov chain monte carlometropolis monte carlokinetic monte carlodiscrete element methodconjugate heat transferquantum monte carlomultibody dynamicsstiff ode solveradaptive mesh refinementparticle in cell

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.