Re: [Flightgear-devel] logging data
On Mon, 24 Nov 2003 09:27:04 -0600 "Curtis L. Olson" <[EMAIL PROTECTED]> wrote: David, Now I'm imagining a script that sets up all the initial conditions (altitude, speed, pressure, temp, etc.) as well as specfic logging fields, flies an FAA certification test, logs the results, and graphs the results. Maybe even eventually building a big web page so you can navigate the results of all the tests in your browser, compare fdm A to fdm B, etc. This is pretty much what we set up with JSBSim a year or two ago. We can now plot the data "sets" we want as well as individual properties, and at pretty much whatever rate we want. It's fairly simple. We needed something to regression test our changes, so I modified the command line plotting program I wrote specifically for JSBSim data, and added the ability to run the plotting program in an automated fashion and spit out .png plot file images. I also had the script write out an html page that gave specifics for a test/plot and provided a hyperlink to the property in question. So, we had a set of batch files that could run JSBSim in a specified flight profile (via the JSBSim scripting language) and produced a "report" - all in very few seconds as we were running batch and not real-time. Jon ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] logging data
David, I've been playing with your logging system (/logging/log/etc. in the property tree) and it is very slick. Good work. :-) It's very convenient for setting up the fields you want to log and the rate and dumping out to a file. I added an "fg_command" wrapper so I could set up the fields from a remote script and then call the logging->reinit() function remotely. It works great. Now I'm imagining a script that sets up all the initial conditions (altitude, speed, pressure, temp, etc.) as well as specfic logging fields, flies an FAA certification test, logs the results, and graphs the results. Maybe even eventually building a big web page so you can navigate the results of all the tests in your browser, compare fdm A to fdm B, etc. Regards, Curt. -- Curtis Olson HumanFIRST Program FlightGear Project Twin Citiescurt 'at' me.umn.edu curt 'at' flightgear.org Minnesota http://www.flightgear.org/~curt http://www.flightgear.org ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
[Flightgear-devel] Logging
I've made a minor change to logging -- all logs and log entries now require an explicit 'enabled' property, set to a boolean true value, or else they will be skipped. I made this change to support the new logging dialog (under State/Logging) that I've just checked in -- you can now log properties without creating XML files and adding them to the command line. The dialog supports logging up to 9 properties to a CSV file, though there's no hard-coded limit in FlightGear internally. All the best, David -- David Megginson, [EMAIL PROTECTED], http://www.megginson.com/ ___ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
