This dataset contains the simulation data, the post-processed results and the code underlying the paper "Dynamics of floating-wind-turbine wakes in a wind tunnel setup" (Amaral et al., Wind Energy Science, 11, 3401-3426, 2026) and Chapter 7 of the author's PhD thesis at Delft University of Technology. The study investigates how imposed platform motion shapes the wake of a floating wind turbine, using large-eddy simulations with the YALES2 solver coupled to an actuator-line model to reproduce the 1:75-scale DTU 10 MW rotor in the Politecnico di Milano wind tunnel, as tested in the UNAFLOW and IEA Wind Task 30 OC6 Phase III campaigns. Eleven load cases were simulated: a fixed-bottom reference case and two cases per degree of freedom (surge, sway, pitch, roll and yaw), one with a low Strouhal number and a high normalized amplitude, and one with a high Strouhal number and a low normalized amplitude. The dataset is organized as five sub-datasets, each in its own top-level folder: (1) WIND_TUNNEL_SIMULATIONS, the post-processed wake and rotor data with the YALES2 input files and job scripts; (2) POST_PROCESSING_WORKFLOW, the Python and Bash scripts used for post-processing and preparing the post-processing workflows; (3) PLOT, the scripts that turn the post-processed data into the figures of the wake analysis; (4) U_STD_THRESHOLD_DATA, flow-field snapshots on two slices of the domain with the vortex trail extraction and analysis scripts; and (5) Q_CRITERION_DATA, the Q-criterion iso-surfaces and the script that renders them. The raw probe outputs of the solver were too large to publish and are not included. Each folder carries its own README.txt with the full description of its content, the numerical and post-processing settings, the file formats and naming conventions, and the software requirements and script adaptations needed for reuse.
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 results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.