- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
This work presents a benchmark dataset for wind turbine tower fatigue prediction, the FLOATBench, and applied a number of machine learning based methods, such as trees based and neural network based, to conduct modeling and perform the prediction. Numerical results are reported.
Critical strengths
I have critical concerns rather than seeing strength regarding this work.
Critical weaknesses
The critical weakness is that the dataset is generated from a simulation software rather than field data collected by various sensors mounted on a real 22-MW wind turbine. If it is a field dataset, I would do a full support. However, we do know the issues of the simulated dataset and its value is limited on conducting data-driven modeling. I have seen people repeating this error for decades. The simulated software in its nature is a set of mathematical equations, e.g., PDEs. Hence, machine learning methods applied into modeling based on such data are eventually approximating this set of math equations rather than the true dynamics of a wind turbine. The only benefit is that you might leverage the surrogate models to speed up the simulation experiments by OpenFAST and other tools, such as Blades.
Questions for authors
I have no questions for authors. I only concern the value of such a dataset and its benchmarking results in the real wind turbine tower fatigue modeling.
6 comments
Response to authors' feedback
Thank you very much for the constructive feedback.
Please allow me to again present my stand. I agree with you that maybe, so far, so publicly accessible wind turbine datasets for evaluating latest 20MW above offshore wind turbine tower fatigue. Yet, this does not address the critical point that the presented dataset value is not as meaningful as imagined by you to people who worked on wind turbine system modeling with data-driven methods. The core issue have been clearly explained in my previous points, data generated from simulators are distant from reality and people who use these simulated data can only obtain a surrogate of the equations behind the simulator. Therefore, if a score collaborated with a wind turbine design and research laboratory, once get the inputs, can generate simulated data very well. However, the real tower fatigue of offshore wind turbine in reality can be much more than that. And the data-driven models obtained based on such a dataset cannot draw more reliable conclusions beyond the simulator can tell. Then, the scientific aspect value of the dataset become very slim. Studies based on this dataset will be rejected by journals as editors will ask why not directly work with simulation tools?
Meanwhile, as a scholar who has worked in this field for a long while, I can tell you that I have visited the real laboratory for offshore wind turbines with capacity higher than 20 MW. People have installed sample machines for degradation studies and fatigue studies with collecting real data. They also have testing facilities to accelerate the fatigue testing of the tower under different conditions. I hence encourage authors to reach out more and explore more. One primary assumption that engineering field can accept the data-driven study is that we believe data serve as the digital copy of the real world and data-driven methods help us approximate this real world dynamics or other complicated relations that classical explicit math expressions cannot do. Yet, if you report only the simulated data, this principle got violated. Meanwhile, I use simulators can explore much more design or operating scenarios that this dataset can tell.
Hope my feedback can further help authors in the future identify and report real and more valuable dataset and benchmarking studies.
Physical Grounding and the Scientific Value of FLOATBench
FLOATBench is grounded in real offshore operating conditions and established wind-turbine engineering practice. Its wind–wave operating envelope is informed by 22 years of ERA5 reanalysis for a real offshore site; its labels are generated through OpenFAST, which has undergone experimental validation in other turbine configurations; and its fatigue assessment follows established engineering procedures. We therefore disagree with the characterization that the data’s simulated origin makes it detached from reality or scientifically uninformative.
The research question arises directly from this engineering workflow: when expensive simulations are approximated by ML surrogates, do their predictions remain accurate under unseen operating conditions, and can standard validation identify the models that do so? FLOATBench demonstrates that strong aggregate performance can conceal substantial extrapolation errors and misleading model rankings. Knowing the simulator’s equations does not determine these properties of the learning algorithms.
Where matching field measurements are not publicly accessible, why should their availability be a prerequisite for publishing reproducible evidence of these ML failures? A physically grounded, openly available simulation benchmark enables the community to investigate them now.
The simulator can certainly generate further scenarios. Releasing a common dataset and controlled evaluation protocol allows researchers to compare methods without independently repeating an expensive simulation campaign. This is the contribution of a shared benchmark.
Experimental measurements would complement this work by enabling direct validation of the particular 22 MW configuration. That additional validation question does not negate the dataset’s existing physical grounding or the relevance of the surrogate-learning failures it reveals. We will acknowledge this in the paper. We ask that the submission be assessed on those contributions and its explicitly stated scope.
Physical Validation, Real-World Relevance, and Benchmark Value
We thank the reviewer for finding the paper clear and easy to follow. We agree that engineering datasets should be grounded in real measurements. We'd like to clarify that FLOATBench already reflects this principle: our inputs are drawn from a real site, as outlined in Sec. 3. However, fatigue data isn't feasible because no such site has ever been constructed. The purpose of this data is to support design decisions, not to reflect maintenance conditions.
Assessing fatigue for a single tower requires thousands of simulations, which limits how many candidate designs engineers can evaluate. Reliable ML surrogates could reduce this cost, and FLOATBench tests whether they stay reliable under unseen conditions. We address the concern in seven points: where the data come from and why simulation is needed (1-3), how OpenFAST has been validated (4), what the benchmark adds (5-6), and where field data fit (7).
1. The inputs come from a real site. The wind and wave conditions come from 22 years of ERA5 data west of the Isle of Barra (Papi et al., 2022): 1,078 conditions with 6 seeds each, following DLC 1.2 and DNV-RP-C203.
2. No public field data exist for floating towers at this scale. To our knowledge, no field measurements of a floating turbine tower of 20 MW or more are publicly available. Data from smaller floating turbines cannot simply be scaled to 22 MW: geometry, natural frequencies, loading and platform dynamics change the fatigue response. Field data also cover few sensors and only the conditions experienced, and need calibration.
3. Real turbines are designed with simulations. Fatigue must be assessed before a turbine is built (IEC TS 61400-3-2). Loads are measured later, on a prototype (IEC 61400-13): measurements validate the simulator; simulations design what does not yet exist.
4. OpenFAST has been checked against measurements: Hywind Demo (Driscoll et al., 2016), alpha ventus (Popko et al., 2021) and TetraSpar, where an OpenFAST digital twin estimated tower fatigue DELs with errors of 10–15% on average (Branlard et al., 2024). Known limits are documented as well: in scale-model wave-tank tests, tower loads are somewhat underestimated (Robertson et al., 2017), mainly through low-frequency hydrodynamic loads (Robertson et al., 2020), and no validation exists yet at 22 MW.
5. Speed is not the only benefit. A faster surrogate helps only if it can be trusted. Random validation selects a model with 1.4–1.6× the extrapolation error of the best network. With it, 38–59% of the joint-extrapolation damage lies in predictions more than 10% too low, against 6–19% with the network, so a design could look safer than its simulation reference.
6. It also serves ML research. 582,120 section-resolved labels and 735 fitted models give a testbed for building tabular models, including foundation models such as TabPFN, that extrapolate reliably; physics data are rare in tabular benchmarks (at most 3 of 51 TabArena datasets). The global rank-1 model falls to ranks 21/11/13 under joint extrapolation, while a network ranked 69th–79th becomes the best, across grids, partitions and five seeds, and TabPFN-2.5 does not beat it. PDEBench and The Well are similar simulation-based testbeds.
7. Field data would extend, not invalidate, the benchmark. Measurements from a large floating turbine could be added as a test set with the same inputs (wind and wave conditions) and labels (damage at gauge heights). Models trained on FLOATBench could then be tested and fine-tuned on real data, measuring the simulation-to-reality gap, and the regime partition would show which measured conditions fall outside the simulated envelope.
In summary, FLOATBench serves the design stage, where fatigue is assessed with simulations before a turbine is built. Its inputs come from a real site, and no public fatigue measurements exist for a floating turbine of this size. FLOATBench provides a public dataset and a reproducible benchmark for developing reliable surrogates that support these design decisions, and for ML generalization research. We thank the reviewer for raising this concern, and we hope these clarifications and revisions warrant a reconsideration of the overall assessment.
References (added to the revised paper):