Directions of lithosphere interactions in the Pamir – Hindu Kush junction inferred from anisotropic tomography
Bibliographic record
Abstract
The Pamir and Hindu Kush are examples of a puzzling collision system where a complex junction of colliding lithospheric plates coexists with intermediate depth seismicity at 300 km. In this study, we constructed a new tomography model using travel time data from local events recorded by the TIPAGE (Tien Shan – Pamir Geodynamic program) network. In addition to the P- and S-wave velocities down to 200 km, we derived the azimuthal anisotropy. The velocity anomalies were consistent with the results of previous studies. In the crust, the velocity structure and anisotropy directions were mainly oriented along major suture zones. At depths of 80–120 km, a narrow low-velocity anomaly coinciding with the distribution of deep seismicity was interpreted as a trace of entrained crustal material by the dipping lithosphere. The anisotropy directions at these depths were mainly oriented northwest–southeast and were interpreted as indicating the direction of the motion of colliding plates. The difference in the magnitude of anisotropy south and north of the Pamir seismic zone suggests that the lithosphere coming from the south possesses less anisotropy than that of the Asian plate. The local tomography model was supplemented by previously computed regional tomography that expanded the area both laterally and axially. Beneath the Pamir, both continental plates coming from the north and south form a drop-shaped anomaly that will possibly delaminate in time. Beneath the Hindu Kush, we could clearly trace a continuous almost vertical subduction of the Katawaz block from the south. Thus, the continental collision beneath the Pamir and subduction beneath the Hindu Kush are separate processes with different rates and directions of plate movement.
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.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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".