An aerodynamic database of wind loads on gable and hip roof buildings
Bibliographic record
Abstract
Experimental wind tunnel databases are essential for determining design wind loads on buildings for a range of applications, including building code development and database-assisted design. Such databases have played a key role in developing data-driven methods and validating numerical simulations in recent years. Despite their importance, there are limited publicly available databases. This paper presents wind tunnel data obtained at Western University, which aims to address the gap for data on low-to mid-rise gable and hip-roof buildings. The database encompasses 154 different cases, examining the impacts of non-dimensional building geometry parameters and roof shape on the resulting aerodynamic loads. Notably, it includes 74 gable and 80 hip roof-shaped building cases, all with a roof slope 6/12 across open and suburban terrain categories. The paper examines the geometric aspect ratio limits as to when the gable or hip roof can be considered aerodynamically flat with respect to the total base shear. For gable-roofed buildings, the contribution of the mean and the variance of the base shear loads of the walls and roof collapse relatively well with respect to the mean roof height-to-length ( h / L ) ratio, where the length, L , is the plan dimension parallel to the wind direction. The contribution of the roof reduces to less than 3 % when h / L > 2 . For uplift, the contribution of the windward roof and leeward roof to the total uplift was examined. For h / L < 2 , the leeward roof contributes more to the total uplift. As for the hip roof, the contributions of the walls and roof collapse are observed to be a function of the height-to-breadth ( h / B ) ratio, where the breadth, B , is the plan dimension perpendicular to the wind direction. The contribution of the hip roof to the total base shear is less than 1 % when h / B > 1.25 for the L / B ratios considered in the database. The controlling geometric aspect ratios are different for a gable and hip roof due to how these parameters alter the projected roof area that contributes to the total base shear. Generally, when the hip or gable roof contributes to the total base shear, the peak design base shear is smaller than a case with a flat roof.
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.001 | 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".