Sediment transport due to tree root throw: integrating tree population dynamics, wildfire and geomorphic response
Bibliographic record
Abstract
Abstract A field study was conducted to analyze root throw and associated sediment transport in Hawk Creek Watershed, Canadian Rockies. A large crown fire in 2003 allowed the opportunity to study pre‐fire and post‐fire root throw. Based on field data, a significant relation was found between gradient and root plate volume, as well as individual root plate dimensions. Given that tree diameters increase as trees age and that a relation in the field data was found between tree diameter and root plate volumes, sediment transport due to root throw is expected to change in response to forest disturbance and stand age. Sediment disturbance, which is the amount of sediment upheaved during tree topple and does not take into account transport distance, shows higher values on steeper gradients. Sediment transport was notable for the steepest plots, with pre‐fire values of 0·016 cm3 cm–1 a–1and post‐fire values of 0·18 cm3 cm–1 a–1. A tree population dynamics model is then integrated with a root throw transport model calibrated for the Canadian Rockies to examine the temporal dynamics of sediment transport. Fire is incorporated as a disturbance that initiates development of a new forest, with the model cycling through generations of forest. Trees fall according to an exponential rate that is based on time since death, resulting in a time lag between tree mortality and sediment transport. When values of time‐since‐previous‐fire are short, trees are generally <13 cm, and minimal sediment is upheaved during toppling. If trees reach a critical diameter at breast height (dbh) at time of fire, a pulse of sediment occurs in the immediate post‐fire years due to falling of killed trees, with tree fall rates decreasing exponentially with time‐since‐fire. A second pulse of root throw begins at about 50 years after the previous fire, once new recruits reach a critical dbh and with initiation of competition‐induced mortality. Copyright © 2009 John Wiley & Sons, Ltd.
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.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 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".