Element mobilities during serpentinization: Insights from the Ronda Massif, Spain
Bibliographic record
Abstract
Serpentinization is a widespread hydrothermal alteration of ultramafic rocks, particularly peridotites, resulting in the formation of serpentinite through hydration processes. While the behavior of fluid-mobile elements (FME; e.g. B, Li, Cl, As, Sb, Pb, U, Th, Cs, Sr, Ba) during serpentinization is well documented, the mobility of other elements (e.g. base metals) remains poorly constrained. We analyzed bulk rock compositions of pairs of poorly and highly serpentinized peridotite rocks from the Ronda Massif (Spain), complemented by in situ LA-ICP-MS mineral analyses. The Loss On Ignition (LOI) content of whole rock represents a good proxy for serpentinization intensity. Ca, Al, Cu, V, and Ti are increasingly mobilized during the initial stages of pervasive serpentinization. In a second stage corresponding to total serpentinization along cm-wide, several meters-long corridors, a systematic loss in Ca, Al, Rb, Sr, REE Hf, Ti, Cu, and V was observed. In contrast, during the third stage of serpentinization corresponding to late faulting only Ca and Cu were leached. The trace element composition of serpentine minerals, including Ti, V, and Zn, is influenced by the primary mineral assemblage, particularly olivine and pyroxenes. In contrast, the mobility of Al and Ca from millimeter to meter scale is notably linked to the bastite-pyroxene and serpentine mesh texture-olivine transformation. Co, Ni, Zn, and Cr depletion in serpentine within veins is compensated by their significant incorporation into magnetite. Copper is systematically leached from serpentinized rocks, suggesting that serpentinization likely serves as a significant source for Cu-rich hydrothermal metallogenic systems hosted in ultramafic rocks. • LOI values in peridotites are a reliable proxy for serpentinization degree. • Serpentinization in the Ronda Massif is clearly non-isochemical. • Ca, Al, Ti, Sr, V, and Cu are leached during serpentinization. • Serpentinization may be a key source term in ultramafic-hosted deposits.
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.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.003 | 0.002 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.002 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.000 |
| Insufficient payload (model declined to judge) | 0.001 | 0.001 |
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".