U-Pb DATING OF A DIABASE DIKE RESOLVES THE PROBLEM OF MUTUALLY CROSSCUTTING RELATIONSHIPS WITHIN THE FRASER-STRATHCONA DEEP COPPER VEIN SYSTEM, SUDBURY BASIN
Bibliographic record
Abstract
A geologic problem has been addressed in the Fraser-Strathcona Deep Copper mine, Sudbury, wherein diabase dikes and the chalcopyrite vein system have a mutually crosscutting relationship. In any situation where crosscutting relationships are mutual there is ambiguity, and it is important to independently test and verify the ages of the events in question, thus avoiding erroneous conclusions about the controls on mineralization. To this end detailed underground geologic mapping and U-Pb dating have been applied to a diabase dike that crosscuts the 1850 Ma Sudbury Igneous Complex and footwall Cu-Ni-PGE vein mineralization. The dike has a minimum 1.5 km strike length, 2.2 km dip length, and a width of 20 m. Where the dike cuts the Cu-Ni-PGE vein system there are (1) sharp contacts with the dike clearly cutting chalcopyrite veins, (2) laminated chalcopyrite-pyrrhotite-pentlandite veins along the hanging-wall or footwall contacts of the dike, and (3) back veining in the form of 0.5- to 2 m-wide remobilized sulfide veins and stockworks that cut the dike. \n \nMagmatic zircons from the diabase have a concordant 206Pb/238U age of 506 ± 4 Ma, whereas abundant xenocrystic zircons have ages of 1810 to 1840 Ma and appear to have been derived from the Sudbury Igneous Complex. Magmatic titanite from the dike defines a highly discordant array of points with an upper intercept at 530 ± 21 Ma, although the titanite analyses are not precise. The discordance results from recent Pb loss, which may have been related to brittle fracturing and fluid infiltration during exhumation and mild deformation. \n \nThe diabase dike is interpreted to be part of the 500 to 600 Ma extension and rifting that formed the Ottawa-Bonnechere graben and related features during rifting of eastern North America prior to the opening of the Iapetus Ocean. It represents the youngest intrusive event within the post-impact geologic history of the Sudbury structure.
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.001 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.000 | 0.001 |
| 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".