State-of-the-art review of occupant behavior modeling and implementation in building performance simulation
Bibliographic record
Abstract
Occupant Behavior (OB) is one of the major drivers of building energy consumption. However, OB is usually oversimplified in Building Performance Simulation (BPS), resulting in a significant performance gap between actual and simulated building energy use. Thus, understanding the true nature of OB and its accurate representation within BPS is crucial. Despite the existence of many review articles that focus on several aspects of OB, the vast majority of reviews are centered on a specific aspect of OB modeling, scattering the main findings among various studies. The literature still lacks a comprehensive review that compiles and analyzes the recent studies on each stage of OB such as data collection and analysis, modeling, integration of OB models into BPS, validation, and presentation of the data in a suitable format. To this end, the present review summarizes, compiles, and analyzes the recent literature on every aspect of OB in BPS, and presents an up-to-date evaluation of the multiple facets of OB modeling in BPS. It aims to present the development and implementation steps of the OB model within BPS tools. A general outline characterizing the recommended workflow for modeling OB in BPS is described. A brief categorization of data collection methods used in OB modeling is presented. Common quantitative OB modeling approaches in BPS i.e., Stochastic, Statistical, Data mining, and Agent-based methods, are elucidated. The main applications, advantages, and limitations of each model are discussed. The available literature on the influence of different OB patterns and occupants’ interaction with building systems, such as cooling, lighting, shading, and appliances, on building energy performance is evaluated. In brief, this study provides an up-to-date review of OB in BPS, offering valuable insights to both academic researchers and industrial professionals to aid them in choosing and adopting correct strategies to accurately model OB and incorporate it into available BPS tools.
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.004 | 0.013 |
| Meta-epidemiology (narrow) | 0.002 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.004 | 0.006 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.003 |
| Open science | 0.003 | 0.001 |
| Research integrity | 0.002 | 0.001 |
| Insufficient payload (model declined to judge) | 0.006 | 0.002 |
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".