On Fri, 12 Apr 2002 14:08:00 -0500 Michael Selig <[EMAIL PROTECTED]> wrote:
>Ahhhhh ... thank you ... I see it now. The fact that >"CLadot" gets included on the fly is pretty neat. As our We wanted the ability to add whatever we wanted to for aero coefficients. One could do lateral or longitudinal only, or translational or rotational only. I can't think of a good reason offhand to do so, but there might be other applications - particularly ones useful for educational purposes I'd hope. Also, odd aircraft might have wildly different sets of coefficients - or even none at all. >The point - are plans underway to have JSBSim include >nonlinear aero data via path/filename, rather than >including all that nonlinear data in the single xml file? We do include files instead of config-file-inline inclusion of data for engines and propellers. As time went along we saw that it would be very good to allow for a simple FILE="" specifier to allow for loading tables or data from file instead of loading it inline. It is a very good idea. >Also, does JSBSim accept aero data in the body axes as >well as the stability axes? No. This is something we need to think about. In what way would it affect our EOM calcs? Would it be better to for us to convert the data to stability axes first? etc. Comments solicited. >Can JSBSim do 3D interpolation for, say, data as a >function of angle of attack, sideslip and flaps? We have >this in our Twin Otter setup, for example Right now we are limited to data that is either: 1) a single value 2) a "vector" (i.e. lookup with one index, e.g. alpha) 3) a table (lookup with two indices) 4) equation (not implemented yet) The desire is that we *do* plan to do multi-dimensional lookup tables, so this would be supported someday - sooner rather than later if there was a pressing need. Jon _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
