MINERAL COMPOSITIONS AND PHASE RELATIONS OF Ni-Co-Fe ARSENIDE ORES FROM THE AGHBAR MINE, BOU AZZER, MOROCCO
Bibliographic record
Abstract
In an attempt to contribute to a better knowledge of phase relations, chemical trends and complex depositional history of the Co–Ni arsenide ores at Bou Azzer district, Morocco, (and by extension to the natural arsenides and sulfarsenides of the Ni–Co–Fe–As–S system), forty samples from the Aghbar mine have been studied. The Aghbar mine, located in the western central area of the Bou Azzer inlier, displays noticeable mineralogical variations depending on the type of mineralization: filling veins or replacing the host serpentinite. Nickel ores of vein type, Co–Fe ores of serpentinite-hosted type and late Cu ores are the assemblages that we identified. Although there is a good agreement with the general sequence established for the Bou Azzer district, meaningful differences in mineral chronology, composition and temperatures of formation are discussed on the basis of the experimental data. The crystallization sequence of Ni ores reveals a continuous increase in As fugacity up to the formation of Ni-rich skutterudite, with formation temperatures fitting well the field of solid solution experimentally established at 650°–625°C. In contrast, the Co–Fe ores seem to form at a somewhat lower temperature (from ~500° to 400°C), and especially at the lower part of this range, during the crystallization of arsenopyrite. These temperature differences between the two main ores of the deposit can be interpreted by assuming either different temperatures in the two ore-forming fluids or considering differences in the paths followed by similarly hot mineralizing fluids.
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.003 | 0.001 |
| Science and technology studies | 0.001 | 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".