Characterizing baseline concentrations, proportions, and processes controlling deposition of river-transported bitumen-associated polycyclic aromatic compounds at a floodplain lake (Slave River Delta, Northwest Territories, Canada)
Bibliographic record
Abstract
Inadequate knowledge of baseline conditions challenges ability for monitoring programs to detect pollution in rivers, especially where there are natural sources of contaminants. Here, we use paleolimnological data from a flood-prone lake ("SD2", informal name) in the Slave River Delta (SRD, Canada), ∼ 500 km downstream of the Alberta oil sands development and the bitumen-rich McMurray Formation to identify baseline concentrations and proportions of "river-transported bitumen-associated indicator polycyclic aromatic compounds" (indicator PACs; Hall et al. 2012) and processes responsible for their deposition. Results show that indicator PACs are deposited in SD2 by Slave River floodwaters in concentrations that are 45 % lower than those in sediments of "PAD31compounds", a lake upstream in the Athabasca Delta that receives Athabasca River floodwaters. Lower concentrations at SD2 are likely a consequence of sediment retention upstream as well as dilution by sediment influx from the Peace River. In addition, relations with organic matter content reveal that flood events dilute concentrations of indicator PACs in SD2 because the lake receives high-energy floods and the lake sediments are predominantly inorganic. This contrasts with PAD31 where floodwaters increase indicator PAC concentrations in the lake sediments, and concentrations are diluted during low flood influence intervals due to increased deposition of lacustrine organic matter. Results also show no significant differences in concentrations and proportions of indicator PACs between pre- (1967) and post- (1980s and 1990 s) oil sands development high flood influence intervals (t = 1.188, P = 0.279, d.f. = 6.136), signifying that they are delivered to the SRD by natural processes. Although we cannot assess potential changes in indicator PACs during the past decade, baseline concentrations and proportions can be used to enhance ongoing monitoring efforts.
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.001 | 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".