Noise Control for High Plume Exhaust Fans: A Case Study
Bibliographic record
Abstract
High plume exhaust fans are a notable source of noise for institutions that use fume hoods. These fans are intended toaddress local air quality effects without the need for tall stacks. This is done through the use of high air velocity to propel airemissions upwards. The exhaust is also mixed with dilution air directly at the exhaust point. It is common practice for twoor more units to operate together from a common mixing plenum. The fans exhaust a constant flowrate and compensate forthe change in fume hood airflows by drawing air into the mixing plenum through a bypass damper. The noise emissionlocations are therefore the exhaust point, the bypass intake, fan casing, and the casing of the mixing plenum. Each of theseemission locations becomes significant when large sound level reductions are needed. Large reduction amounts can benecessitated by strict sound level criteria, or close proximity to the points of reception. In the case illustrated here, the pointsof reception were close to the fans. A sound level reduction of approximately 25 dB was needed from the entire system. Itwas therefore necessary to mitigate all of the emission points to achieve an effective overall reduction. Mitigation solutionsproviding this level of reduction are not available from the manufacturer. A supplier focussed on custom noise mitigationwas retained to design, manufacture and install a package of mitigation measures. The final product achieved the necessaryreductions and resulted in a much more pleasant acoustic environment in adjacent areas.
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 distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 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 teacher head, 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".