|
From: Jon S. B. <js...@ha...> - 2007-12-30 22:41:42
|
I like all this a lot. I'll look into the code and think about it some more. Discuss. J Jon On 12/29/07, David Culp <dav...@co...> wrote: >Actually it might be best to include a speed freeze along with the above "full >freeze". Without this the model will be allowed to speed up or slow down. >For a true "wind tunnel effect" the speed will need to be held constant until >the user "dials in" a new one. > >Dave And: On 12/29/07, Agostino de Marco wrote: >But I think that sometimes there's the need to verify the longitudinal >motion aerodynamics of aircraft complete models Freezing would really be useful to check the aerodynamic data in the aircraft configuration file. For this, it would be necessary to freeze the velocity and position (altitude). Orientation would not affect the task, it just would be irrelevant. We would only need the print-out of the buildup values of each parameter we are interested in; in other words, it would be good to be able to make a run at constant speed and altitude, AND set a sweep of alpha or beta values (introduced as a table in the script file). We would then obtain the total CL, CD, etc, and also the contributions of each component as functions of alpha or beta, for any aircraft configuration (flaps deflection, spoilers, landing gear up/down, etc). We could even cut the tail out of the configuration file and run a tail-off case. Fabian |