This dataset contains high‑resolution measurements of solar irradiance and ambient temperature collected on roof (horizontal plane, I1/T1) and facade (vertical plane, I2/T2) surfaces of an urban university building in Medellín, Colombia. The monitoring system was implemented using an edge computing device that enabled local acquisition, validation, and transmission of sensor data to the cloud in real time. The dataset is organized as time series in both CSV and Parquet formats, ensuring accessibility and reproducibility. It provides continuous records from January 30, 2026 (14:30 local time) to June 12, 2026 (12:39 local time), with an average sampling interval of approximately 1.71 seconds. Measurements on dual orientations (roof vs. façade) offer valuable insight into the variability of solar exposure in building‑integrated photovoltaic (BIPV) contexts, highlighting the influence of surface inclination and surrounding urban elements. The dataset underwent a structured processing workflow to ensure quality and consistency. Initially, the consolidated CSV file was loaded into the edge computing environment, and only relevant columns were selected (sensor ID, measurement value, and units). Timestamps were converted from UTC to local time in Medellín (UTC‑5). Subsequently, null records were removed, and out‑of‑range values were excluded, specifically irradiance and temperature values below zero. Files referring to irradiance measurements are denoted with the prefix irr_, while files referring to temperature measurements are denoted with the prefix temp_. The suffix 1 corresponds to sensors installed on the roof (horizontal plane), and the suffix 2 corresponds to sensors installed on the façade (vertical plane). Parque i ├── Horizontal measurement (I1, T1) - roof │ ├── irr_1.csv │ ├── irr_1.parquet │ ├── temp_1.csv │ └── temp_1.parquet └── Vertical measurement (I2, T2) - façade ├── irr_2.csv ├── irr_2.parquet ├── temp_2.csv └── temp_2.parquet
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The perception of the impact of agile methods is predominantly positive, and several challenge areas were discovered, but based on this study, agile methods are here to stay.
M. Laanti, O. Salo, P. Abrahamsson· Information and Software Tec...· 260 citations· ⚡20
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 8, 2026
Jennifer Neville did not want to go into computer science—but that’s exactly where she landed. Neville discusses the starts and stops that led to her professional sweet spot and her work identifying “surprising failures” making it hard for AI to handle complexity. The post What AI gets wrong and what failure teaches us appeared first on Microsoft Research.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.