Pennypack Creek Drainage Basin Erosion History: Bucks, Montgomery, and Philadelphia Counties, PA, USA
Bibliographic record
Abstract
Topographic map evidence is used to interpret Pennypack Creek drainage basin erosion history in and north of the City of Philadelphia, Pennsylvania (USA). Southwest and west-southwest oriented through valleys crossing the south oriented Pennypack Creek drainage basin, barbed Pennypack Creek tributaries, and significant valley direction changes are used to determine that the Pennypack Creek valley eroded headward across massive southwest oriented floods. Initially floodwaters flowed on a low gradient topographic surface at least as high, if not higher, than the highest Pennypack Creek drainage basin elevations today. Shallow low gradient diverging and converging flow channels were eroded into the underlying bedrock surface predominantly along fault lines and other zones of easier to erode materials. Headward erosion of the much deeper Pennypack Creek valley across this anastomosing channel complex captured southwest oriented floodwaters and flow on northeast ends of beheaded channels was reversed so as to move toward the newly eroded and deeper Pennypack Creek valley. These reversed flow channels captured southwest oriented floodwaters still moving north of the actively eroding Pennypack Creek valley head. This captured water then moved in a northeast direction and eroded deep northeast oriented valleys headward from the newly eroded Pennypack Creek valley. These valleys today account for northeast and east oriented Pennypack Creek valley segments and northeast oriented (barbed) tributaries flowing to south oriented Pennypack Creek. The floodwater source cannot be determined from Pennypack Creek drainage basin evidence, but was from the northeast. Melting of a continental ice sheet could produce floods of sufficient volume and duration to overwhelm whatever drainage system previously existed and to erode new drainage basins in a manner similar to how the Pennypack Creek drainage basin was eroded.
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.000 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.000 | 0.001 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.014 | 0.003 |
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".