Multiple Use Stormwater Detention Adjacent to UBC Centre for Comparative Medicine : Final Report Design
Bibliographic record
Abstract
This Final Design Report provides information pertaining to Thunderbird Lake, a proposed stormwater wet pond facility for South UBC in Vancouver. This report consists of a table of contents, overview, introduction, design overview, design criteria, technical considerations, summary of software and standards used, construction planning, project cost estimate and appendices including construction specifications and detailed drawings. Thunderbird Lake was chosen as the preferred design for a number of reasons, namely, the existence of numerous precedent examples to similar systems, the high quality of effluent discharge released into the ocean, and promotion of green space for students, nearby residents, and visitors. Thunderbird Lake will be capable of safely handling a volume of 8,500 m3 in the event of a 1/100 year rainfall event. Thunderbird Lake is a typical wet pond featuring a forebay for sediment settlement and a main pond for stormwater detention, separated by a concrete weir. The pond features continuous orifice flow into an outlet detention tank, as well as a pair of pipes that can be opened with a valve when the pond is to be drained. Other design criteria which were considered include the use of a water recirculation system, biofiltration mechanisms, serviceability, and aesthetics. Construction of the facility is expected to take approximately 8 months, with an anticipated start date of May 2019. Based on preliminary estimates, the total cost of the project is valued at $2,677,000. Disclaimer: “UBC SEEDS provides students with the opportunity to share the findings of their studies, as well as their opinions, conclusions and recommendations with the UBC community. The reader should bear in mind that this is a student project/report and is not an official document of UBC. Furthermore readers should bear in mind that these reports may not reflect the current status of activities at UBC. We urge you to contact the research persons mentioned in a report or the SEEDS Coordinator about the current status of the subject matter of a project/report.”
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.011 | 0.012 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.000 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.189 | 0.032 |
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".