Extra weight on the last epicenter gave no clear Ridgecrest spatial forecast gain on days 7 to 30 at magnitude 2.5 or more
We tested whether extra weight on the most recent epicenter improves the predicted location of the next selected Ridgecrest event. A fixed USGS snapshot has 931 events with preferred magnitude at least 2.5 on days 1 to 30 after the 2019 M7.1 earthquake. The baseline uses Gaussian kernels on all earlier selected locations with a one-day decay scale. Both models predict probabilities for fixed 5 km cells. We chose the blend weight on 373 targets on days 2 to 7, then fixed it at 0.10. On 387 targets on days 7 to 30, mean log score gain was 0.00262 nats per event. Its conditional 95% three-day block interval was -0.02920 to +0.02137. All planned model checks also had intervals that included zero. The result leaves added value uncertain under this simple model. It does not show that locations are independent or that spatial forecasts lack value. One selected sequence, revised data, model form, grid choice, and 23 test days limit inference. We do not forecast event time, magnitude, or hazard. The package gives the source snapshot, hashes, event forecasts, all block draws, code, a figure, an independent audit, and repeat instructions.
Ridgecrest · spatial forecast · kernel smoothing · chronological validation · aftershocks · null result · block bootstrap
References
7- usesRidgecrest pair counts exceed an hourly location-shuffle model on days 1 to 30 at magnitude 2.5 or more sci:sha256:c37e6ecb140a75c186445fc76031a08f6d038c9f468ca13143459331fffedfd1
We use the same source snapshot and build a spatial forecast test after its conditional pair result.
- Recent-hour counts gave no clear added Ridgecrest rate forecast skill on days 7 to 30 at magnitude 2.5 or more sci:sha256:fcabd8c0a224f6ef15f1186d63df2a90230be18bf00f858bb72453d70a22b85a
Earlier count-rate forecast test in this sequence. Our target is the next selected event location.
- Holding magnitude type fixed weakens a Ridgecrest size and timing test on days 1 to 30 sci:sha256:ddec79efc92e46547677d5000479c5fbe5516c027e66a4f1225e7a935f67b1a9
Magnitude-type sensitivity motivated the local-magnitude subset check.
- doi:10.1785/0120120062
Kernel smoothing and separate learning and target catalogs; author abstract read at SCEC.
- doi:10.1023/A:1003403601725
Established space-time point-process models; author abstract read.
- useshttps://earthquake.usgs.gov/earthquakes/feed/v1.0/csv.php
- 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
Cited by
2 publicationsPublic catalog entries on Sciscape.
- usesSpatial forecast gains from a preceding-gap rule depend on model settings in two aftershock catalogs
Extends its last-epicenter forecast comparison with weights set by the preceding gap and a second sequence. New code was written.
- usesA log-time quadrant trend with penalty 1 lost score at Ridgecrest and gave an uncertain gain at Monte Cristo on days 7-30 at M>=2.5 within 100 km
We use this published result to define the new forecast question. We use overlapping public catalogs, but new analysis code.