Efficient nonlinear flame response modeling for propulsion thermoacoustic analysis using limited numerical data

Sicherheitsmeldung mit Schweregrad noch nicht bewertet. Technische Details im Tab „Originaltext“; empfohlene Schritte in der Checkliste.

Originaltext der Quelle (nicht übersetzt) – die deutsche Zusammenfassung findest du im Tab „Kurzfassung".

arXiv:2409.05885v2 Announce Type: replace Abstract: Characterizing nonlinear flame response is critical for predicting thermoacoustic instabilities in propulsion combustors, yet obtaining a comprehensive response map through high-fidelity simulations remains computationally prohibitive. This study proposes a data-driven approach for learning nonlinear flame-response dynamics from limited numerical samples. Instead of requiring exhaustive harmonic-forcing simulations, a frequency-sweeping dataset with multiple perturbation amplitudes is designed to capture the coupled effects of excitation frequency and amplitude, enabling efficient learning of the nonlinear input-output relationship between flow perturbations and heat-release-rate fluctuations. A dual-path temporal surrogate model is developed to represent nonlinear response evolution in the time domain, where complementary temporal features are extracted to retain both global response trends and local nonlinear characteristics. The proposed framework is validated using numerical simulations of a laminar premixed flame. It accurately predicts nonlinear single-frequency responses over a wide range of forcing amplitudes and frequencies, with an average mean relative error of 6.69\% for 72 independent test cases. Further evaluation using a modified $n-\tau$ model demonstrates that the framework can capture stronger nonlinear responses by increasing the diversity of the training data. This work provides an efficient alternative for constructing nonlinear flame-response models and offers a promising approach for rapid …

Vollständiger Originalartikel ↗

• Betroffenheit im eigenen Stack prüfen: Versionen/Komponenten abgleichen.
• Originalquelle / Hersteller-Advisory lesen: https://arxiv.org/abs/2409.05885
• Verfügbaren Patch oder Workaround einspielen und dokumentieren.