Publication Date:
2019-08-13
Description:
If a CFD code/model developer is asked what experimental data he wants to validate his code or numerical model, his answer will be: "Everything, everywhere, at all times." Since this is not possible, practical, or even reasonable, the developer must understand what can be measured within the limits imposed by the test article, the test location, the test environment and the available diagnostic equipment. At the same time, it is important for the expermentalist/diagnostician to understand what the CFD developer needs (as opposed to wants) in order to conduct a useful CFD validation experiment. If these needs are not known, it is possible to neglect easily measured quantities at locations needed by the developer, rendering the data set useless for validation purposes. It is also important for the experimentalist/diagnostician to understand what the developer is trying to validate so that the experiment can be designed to isolate (as much as possible) the effects of a particular physical phenomena that is associated with the model to be validated. The probability of a successful validation experiment can be greatly increased if the two groups work together, each understanding the needs and limitations of the other.
Keywords:
Fluid Mechanics and Thermodynamics
Type:
JANNAF 40th Combustion/28th Airbreathing Propulsion/22nd Propulsion Systems Hazards/4th Modeling and Simulation Joint Subcommittee Meeting; Jun 13, 2005 - Jun 17, 2005; Charleston, SC; United States
Format:
application/pdf
Permalink