Phase Relations in the Fe–Ni–Cu–PGE–S System at Magmatic Temperature and Application to Massive Sulphide Ores of the Sudbury Igneous Complex*
Bibliographic record
Abstract
Experiments in the Fe–Ni–Cu–S system were performed to identify the role of the metal/S atomic ratio on monosulphide–melt partition coefficients and closed-system fractionation paths. In accord with previous work, DCu is ∼0·2 at all temperatures and all metal/S ratios. DNi is highly sensitive to temperature and metal/S, and changes from ∼0·6 at high metal/S and high temperature to >2 at low temperature and low metal/S. The temperature at which the cross-over in DNi occurs is sensitive to S2 fugacity. The monosulphide solid solution (mss)–melt partition coefficients of the platinum group elements (DPGE) are determined with laser-ablation inductively coupled plasma mass spectrometry calibrated on synthetic sulphide standards. At trace element concentration levels, the DPGE are largely insensitive to metal/S, contrary to previous experiments with PGE concentrations in the percentage range. Pt and Pd are highly incompatible with mss (D < 0·1) whereas Ir, Ru, and Rh are compatible, ranging from >3 to ∼10. The chemical differentiation paths of Fe–Ni–Cu–S sulphide melts experiencing mss fractionation are determined by the metal/S parent melt ratio. Oxidized sulphide melts with metal/S < 1 solidify in the stability field of intermediate solid solution (iss) whereas reduced sulphide melts with metal/S > 1 may fractionate past iss stability. The latter will accumulate Ni together with Cu down to solidus temperature. Toward the end of their fractionation path, they are too depleted in S to crystallize iss. Instead, they will precipitate a copper sulphide with monovalent Cu and presumably solidify at an iss–bornite–millerite eutectic. The dataset is applied to massive sulphide ores of the Sudbury Igneous Complex fractionated with respect to Ni/Cu and (Ni + Cu)/Σmetal ratios. It is shown that the change-over in DNi may be used to retrieve parent melt compositions, fractionation temperatures, and magmatic fractionation paths of these 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.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| 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.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".