Metamorphic and intrusive history of the Hindu Raj region, northern Pakistan
Bibliographic record
Abstract
Abstract The Hindu Raj region of northern Pakistan is situated between the Karakoram to the east and the Hindu Kush to the west. Both the Karakoram and the Hindu Kush are better studied and have well-documented, distinct geological histories. Investigation of the Hindu Raj region has been mainly limited to reconnaissance exploration and as such little is known about its tectonometamorphic history and whether that history is similar to its neighbouring areas. Analysis of new specimens collected along the Yasin Valley within the Hindu Raj region outline mid-to-Late Cretaceous pluton emplacement (ca. 105 and 95 Ma). Some of those plutonic rocks were metamorphosed to ∼750 ± 30 °C and 0.65 ± 0.05 GPa during the ca. 80–75 Ma docking of the Kohistan arc. A record of this collisional event is well-preserved to the west in the Hindu Kush and variably so to the east in the Hunza Karakoram. A subsequent, ca. 61 Ma, thermal event is partially preserved in Rb–Sr geochronology from the Hindu Raj, which overlaps with sillimanite-grade metamorphism in the Hunza portion of the Karakoram region to the east. Finally, apatite U–Pb and in situ Rb–Sr both record a late Eocene thermal/fluid event likely related to the India-Asia collision. These new data outline a complex geological history within the Hindu Raj, one that shares similarities with both adjacent regions. The information about the tectonometamorphic development of the Hindu Raj is important to gaining a detailed view of the geological characteristics of the southern Asian margin prior to the India-Asia collision.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.006 | 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 teacher head, 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".