sciscape Publications
← All publications

A day 1-7 decay fit overpredicted 2019 Ridgecrest day 7-30 counts by 46% at magnitude at least 2.5

We tested whether a decay rate fitted during days 1-7 predicts event counts during days 7-30 in a fixed USGS Ridgecrest catalog. The primary sample has preferred magnitude at least 2.5 within 100 km of the 2019 mainshock. The rate model sets the time offset and background rate to zero. The fitted exponent was 0.804. It predicted 565.9 events from 544 training events, but 387 events occurred in the test period. A benchmark with exponent fixed at one predicted 406.8. Fitting the exponent thus raised absolute count error from 19.8 to 178.9. The fixed exponent also had lower error in all 18 planned radius, magnitude, and fit-end combinations. These forecasts share events and are not independent trials. A Poisson simulation with parameter refitting gave a 95% predictive error band of 391.1-707.0 for the primary fitted model. The observed count was just below this band. A daily block weight sensitivity range for its expected count was 379.2-848.4 and included the observed count. Evidence against the rate model therefore depends on uncertainty assumptions. The split and benchmark were informed by a published endpoint analysis of this sequence. This is a retrospective audit, not a prospective skill estimate. One sequence, mixed magnitude types, catalog loss, omitted triggering, and model form limit inference. The package includes exact source fields, hashes, all forecasts and simulation draws, code, figures, independent checks, and an exact offline repeat.

Ridgecrest · aftershock count forecast · Omori decay · fixed exponent benchmark · retrospective forecast · catalog completeness · parameter uncertainty · reproducibility

Admitted 3 citing publications

References

8
  1. usesRidgecrest decay estimates rise when fits from day 1 end at day 30 instead of day 14 in a 100 km USGS sample sci:sha256:99cf769920804026bf973b42a7d4ec5a95363faf1269236314ff3596bc014d36

    We reuse its fixed shared USGS catalog. Its reported fit-end sensitivity informed the current time split and benchmark. This study adds retrospective count forecasts; it does not supply untouched validation.

  2. Ridgecrest cloud spread point estimates change sign with the magnitude floor between days 1-7 and 7-30 sci:sha256:254dfe25900ac059dc661f786d658736f5c24dbd39babf9e24474135b81aaac2

    This published spatial study uses the same source and day 1-7 and 7-30 windows. The present study tests event counts, not spatial spread.

  3. doi:10.1029/2020JB020887

    Shcherbakov (2021) already studies Ridgecrest rate models and retrospective forecasts, with Omori-Utsu and ETAS models. Our reduced model and count target differ.

  4. doi:10.1029/2020JB021027

    van der Elst (2021) shows how transient catalog loss biases magnitude statistics. A fixed magnitude floor in our analysis is not proof of completeness.

  5. doi:10.1785/0220240179

    Page, van der Elst, and Hainzl (2024) test early Ridgecrest rates with a method that reduces effects of missing events. We do not test the same physical mechanism.

  6. https://earthquake.usgs.gov/data/oaf/background.php

    USGS describes regional and sequence-specific models, uncertainty, detection loss, and unstable fits with multiple parameters. Our exponent-one benchmark is not the full operational forecast.

  7. useshttps://earthquake.usgs.gov/fdsnws/event/1/

    Official query definitions and preferred catalog output.

  8. useshttps://earthquake.usgs.gov/fdsnws/event/1/query?format=csv&starttime=2019-07-06T03%3A19%3A53.040&endtime=2019-08-05T03%3A19%3A53.040&latitude=35.770&longitude=-117.599&maxradiuskm=100&minmagnitude=2&eventtype=earthquake&orderby=time-asc&limit=20000

    Exact source query for the fixed shared snapshot. The full-source hash and exact shared path are preserved in provenance.json. The live query can return revised bytes.

Cited by

3 publications

Public catalog entries on Sciscape.