Multi-parameter Receiver Function Modeling: Application to the Subduction Zones of Cascadia and the Central Andes
Bibliographic record
Abstract
Receiver functions are a powerful tool to image lithospheric stratigraphy. For flat lying structures, receiver functions can be stacked azimuthally to achieve high signal-to-noise ratios and h-κ-stacks allow to estimate the depth of interfaces (h) and P-to-S wave velocity ratio of the hanging layers (κ). For dipping layers, characteristic for the slab structure in a subduction zone forearc, these methods fail, because the moveout of phases arriving from different azimuths violates the basic assumptions of these methods.We here present a simple routine to simultaneously search for the depth of the top of slab and of the oceanic Moho, for strike and dip of the downgoing slab, as well as for the S-wave velocities and the P‑to-S wave velocity ratios of multiple layers of the overriding and downgoing plates in subduction zone forearcs. Our approach is based on the recent Python port PyRaysum of Frederiksen and Bostock's classic (2000) code for modeling ray-theoretical plane body-wave propagation in dipping anisotropic media, and on SciPy's simulated annealing global parameter search.We applied the routine to hundreds of azimuthally-dependent receiver function sections from the subduction zones of Cascadia (North America) and the central Andes (South America) and retrieved laterally coherent station measurements of the depth and orientation of the top of the subducting slab and the subducting Moho, with only weakly constrained seismic velocities. In Cascadia, we interpolated a regional slab model through fitting of regularized spline surfaces. Small scale structures that are not present in previous slab models can be resolved, e.g. under Olympic Peninsula (Cascadia) and Mejillones Peninsula (northern Chile). Where the receiver functions are more complex than can be accounted for by our model, the labeling of the modeled receiver function phases and comparison to the observed receiver functions allows us to confidently interpret the additional subsurface complexities and reconcile them with our interpretations.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".