Design of a multipart wicket gate for Wuskwatim Generating Station : final design report
Bibliographic record
Abstract
The purpose of this report is to present a solution to Manitoba Hydro’s request for a multipart wicket gate that can be installed and removed from Wuskwatim Generating Station without requiring major disassembly of the generating equipment. The team has designed a multipart wicket gate that addresses the requirements of the project. This report includes a discussion of the design, a method of installation and removal, drawings of the designed wicket gate assembly and a finite element analysis. The current wicket gate is one solid part, and significant disassembly of generating equipment must occur before the gate can be removed and refurbished. Disassembly of the generating station takes several months and results in substantial costs to Manitoba Hydro due to loss of revenue. Therefore, Manitoba Hydro has requested a multipart wicket gate be designed in order to greatly reduce generator downtime. The final design is made up of three major components: the top stem section, the gate body, and the bottom stem section. These three sections can be bolted together inside the scroll case, which eliminates the need for removal of any generating equipment. The top and bottom stem sections mate with the gate body in such a way that the torque required to rotate the gate can be transmitted to the body through the mating surfaces as well as the bolts. Due to the large stress concentrations present in the corners of the stem-to-gate mating surfaces, it is recommended that large fillets be present at those corners and that a high strength material be used for the top stem section. Preliminary finite element analysis showed maximum Von Mises stresses below the allowable stress for some, but not all of the loading conditions. In addition to performing the finite element analysis, the team was asked to produce a detailed installation procedure for the multipart wicket gate. The team recommends that a detailed review of the installation procedure, as well as further finite element analysis, be performed before manufacture and implementation of the multipart gate.
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.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.000 |
| Science and technology studies | 0.001 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.012 | 0.004 |
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".