For How Long Should What Data Be Assimilated for the Mesoscale Forecasting of Convection and Why? Part I: On the Propagation of Initial Condition Errors and Their Implications for Data Assimilation
Bibliographic record
Abstract
Abstract Data assimilation is used among other things to constrain the initial conditions of weather forecasting models by fitting the model fields to observations made over a certain time interval. In particular, it tries to tie incomplete data with model constraints to detect and correct for initial condition errors. This is possible only if initial condition errors leave their signature on the data assimilated and if the model is capable of faithfully reproducing such signatures. Using simulations of the evolution of convective storms in the Great Plains over an active 6-day period, the propagation of initial condition errors to other variables as well as their effect on the accuracy of the forecasts were investigated. Increasing the assimilation time window boosts the ability of assimilation systems to detect a variety of initial condition errors; however, limits to the predictability of convective events impose a maximum assimilation period that is a function of the type of measurements assimilated as well as of the type of errors one tries to correct for. These findings are then used to suggest changes in assimilation approaches to take into account the different predictability times of the model fields constrained by assimilation.
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.011 | 0.035 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.002 |
| Scholarly communication | 0.003 | 0.005 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".