Segmentation of the Main Himalayan Thrust Revealed by Low‐Temperature Thermochronometry in the Western Indian Himalaya
Bibliographic record
Abstract
Abstract Despite remarkable tectonostratigraphic similarities along the Himalayan arc, pronounced topographic and exhumational variability exists in different morphotectonic segments. The processes responsible for this segmentation are debated. Of particular interest is a 30‐ to 40‐km‐wide orogen‐parallel belt of rapid exhumation that extends from central Nepal to the western Himalaya and its possible linkage to a midcrustal ramp in the basal décollement, and the related growth of Lesser Himalayan duplex structures. Here we present 26 new apatite fission track cooling ages from the Beas‐Lahul region, at the transition from the Central to the Western Himalaya (~77°–78°E) to investigate segmentation in the Himalayan arc from a thermochronologic perspective. Together with previously published data from this part of the orogen, we document significant lateral changes in exhumation between the Dhauladar Range to the west, the Beas‐Lahul region, and the Sutlej area to the east of the study area. In contrast to the Himalayan front farther east, exhumation in the far western sectors is focused at the frontal parts of the mountain range and associated with the hanging wall of the Main Boundary Thrust fault ramp. Our results allow us to spatially correlate the termination of the rapid exhumation belt with a midcrustal ramp to the west. We suggest that a plunging anticline at the northwestern edge of the Larji‐Kullu‐Rampur window represents the termination of the Central Himalayan segment, which is related to the evolution of the Lesser Himalayan duplex.
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.000 |
| 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.001 | 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".