A Probabilistic Prediction of Rogue Waves from a WAVEWATCH III Model for the Northeast Pacific
Bibliographic record
Abstract
Abstract Rogue waves are stochastic, individual ocean surface waves that are disproportionately large compared to the background sea state. They present considerable risk to mariners and offshore structures especially when encountered in large seas. Current rogue wave forecasts are based on nonlinear processes quantified by the Benjamin Feir index (BFI). However, there is increasing evidence that the BFI has limited predictive power in the real ocean and that rogue waves are largely generated by bandwidth-controlled linear superposition. Recent studies have shown that the bandwidth parameter crest–trough correlation r shows the highest univariate correlation with rogue wave probability. We corroborate this result and demonstrate that r has the highest predictive power for rogue wave probability from the analysis of open ocean and coastal buoys in the northeast Pacific. This work further demonstrates that crest–trough correlation can be forecast by a regional WAVEWATCH III wave model with moderate accuracy. This result leads to the proposal of a novel empirical rogue wave risk assessment probability forecast based on r. Semilogarithmic fits between r and rogue wave probability were applied to generate the rogue wave probability forecast. A sample rogue wave probability forecast is presented for a large storm 21–22 October 2021. Significance Statement Rogue waves pose a considerable threat to ships and offshore structures. The rare and unexpected nature of rogue wave makes predicting them an ongoing and challenging goal. Recent work based on an extensive dataset of waves has suggested that the wave parameter called the crest–trough correlation shows the highest correlation with rogue wave probability. Our work demonstrates that crest–trough correlation can be reasonably well forecast by standard wave models. This suggests that current operational wave models can support rogue wave prediction models based on crest–trough correlation for improved rogue wave risk evaluation.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.001 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.000 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 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 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".