1. Ergodic Models
An ergodic model assumes that spatial variability in ground motion is equivalent to temporal variability. In other words, it treats the variability of ground motions across different locations as if it represents the variability of ground motions at a single location over time. This assumption allows ground motion prediction equations (GMPEs) to be developed using global datasets from many earthquakes, ignoring site-specific effects.
Key Characteristics of Ergodic Models:
- Use a large dataset from various regions to develop a generalized ground motion model.
- Assume that ground motion variability at one site can be inferred from observations at other sites.
- Do not account for site-specific and path-specific effects, leading to increased uncertainty in ground motion predictions.
- Overestimate variability at a specific site since they include global variations.
Applications of Ergodic Models:
- Traditional ground motion prediction equations (GMPEs).
- Regional seismic hazard assessment.
- Probabilistic seismic hazard analysis (PSHA) for areas with limited local earthquake data.
2. Non-Ergodic Models
A non-ergodic model does not make the assumption that spatial variability can substitute for temporal variability. Instead, it recognizes that each site and each path between a source and a site has unique, repeatable characteristics that affect ground motion. Non-ergodic models account for site-specific and path-specific effects, reducing uncertainty in seismic hazard analysis.
Key Characteristics of Non-Ergodic Models:
- Incorporate local geological and geophysical conditions that influence ground motion.
- Recognize that ground motion at a site is not a random sample from a global dataset but has systematic trends over time.
- Require region-specific or site-specific datasets for calibration.
- Reduce aleatory (random) uncertainty and increase epistemic (knowledge-based) uncertainty since the model relies on localized data.
Applications of Non-Ergodic Models:
- Site-specific seismic hazard analysis for critical infrastructure.
- Urban seismic hazard mapping, considering localized site effects.
- Advanced ground motion modeling, incorporating physics-based simulations and machine learning to refine predictions.
Why Use Non-Ergodic Models?
Traditional ergodic models overestimate variability at a specific site because they include data from many locations, leading to conservative hazard estimates. In contrast, non-ergodic models provide more accurate site-specific predictions by incorporating long-term local seismic behavior, reducing uncertainty.
However, non-ergodic models require significant local data to be properly constrained, which can be a challenge in regions with limited seismic monitoring.
Summary Table:
| Feature | Ergodic Model | Non-Ergodic Model |
|---|---|---|
| Assumption | Spatial variability represents temporal variability | Recognizes site-specific and path-specific effects |
| Data Use | Large dataset from various locations | Site-specific or path-specific data |
| Uncertainty | Higher aleatory uncertainty | Reduced aleatory, higher epistemic uncertainty |
| Application | Regional seismic hazard analysis, GMPEs | Site-specific hazard analysis, infrastructure design |
| Advantage | Works with limited local data | More accurate ground motion predictions |
In recent years, there has been a shift towards non-ergodic models for site-specific seismic hazard assessment, particularly for critical infrastructure projects. Advances in machine learning, physics-based simulations, and high-resolution seismic data have made non-ergodic models more viable for practical applications.
Last reviewed: 2026-07-04
Executive Summary
Earthquake engineering connects ground motion, structural response, performance objectives, instrumentation, and post-event decision support. This article has been expanded as an engineering resource for readers evaluating earthquake engineering concepts, instrumentation choices, and monitoring workflows. The discussion is educational and should be paired with project-specific review by qualified engineers, applicable codes, owner requirements, and equipment documentation.
Key Takeaways
- Define the engineering objective before selecting sensors, test equipment, trigger thresholds, or reporting workflows.
- Use calibrated instrumentation, documented installation practices, time synchronization, and traceable data handling where measurement quality matters.
- Interpret measured data in context: site conditions, structure type, noise environment, sampling rate, bandwidth, and boundary conditions all affect conclusions.
- Use authoritative references and project-specific criteria rather than relying on generic thresholds or unsupported performance claims.
Technical Explanation
In practical earthquake engineering work, the engineering system is more than a sensor or a test platform. A credible workflow includes the measurement objective, instrument selection, mounting or boundary conditions, sampling and timing strategy, data validation, event or response detection, engineering review, and reporting. Weakness in any part of that chain can reduce confidence in the final interpretation.
For monitoring applications, engineers should document sensor orientation, coupling, environmental exposure, dynamic range, frequency bandwidth, data logger configuration, clock synchronization, communications, and maintenance procedures. For testing applications, engineers should document input motion, fixture design, payload properties, control limits, safety interlocks, acceptance criteria, and post-test data review.
Engineering Applications
| Application | Engineering Question | Typical Evidence Needed |
|---|---|---|
| Research and education | How does a structure, component, or sensor respond under controlled conditions? | Test plan, calibrated data, input motion, boundary conditions, and repeatable observations. |
| Critical infrastructure | Is the asset response normal, changing, or potentially unsafe after an event? | Baseline data, event records, thresholds, inspection workflow, and engineering sign-off. |
| Industrial facilities | Can monitoring support operational continuity and response decisions? | Site-specific criteria, reliable telemetry, alarm logic, maintenance records, and documented procedures. |
People Also Ask
What should be specified before buying equipment?
Specify the measurement objective, frequency range, amplitude range, environment, data format, timing needs, installation constraints, reporting requirements, and applicable standards or owner criteria.
Why do references and standards matter?
They provide terminology, acceptance criteria, test methods, and documentation expectations. They do not replace engineering judgment, but they reduce ambiguity and make results easier to review.
How should data quality be checked?
Review calibration status, timing, clipping, sensor orientation, signal-to-noise ratio, environmental artifacts, data completeness, and whether the record supports the engineering decision being made.
Related QuakeLogic Resources
- Essential Data Reporting for Geothermal Seismic Monitoring with Broadband Seismic Stations
- Ensuring Safety and Integrity: Seismic Monitoring of LNG Facilities
- Understanding Lippmann Correction in Seismometers and Its Importance
- 3-Ton and 5-Ton Shake Tables: Advanced Seismic Testing Technology for Precision and Reliability
- Related QuakeLogic products and technologies
- QuakeLogic Engineering Blog topic resources
References
Recommended Diagram or Download
Media placeholder: Add an original diagram showing the measurement chain from sensor or test platform to data acquisition, analysis, engineering interpretation, and reporting. Where this article becomes a buyer guide or application note, create a downloadable PDF version after engineering review.
Discuss a Monitoring or Testing Application
QuakeLogic supports seismic monitoring, earthquake early warning, structural health monitoring, infrasound monitoring, vibration monitoring, data acquisition, and shake table testing applications. For project-specific guidance, contact QuakeLogic with the asset type, measurement objective, site constraints, and required deliverables.
