[Flightgear-devel] making sign of side-slip consistent between fdm (bug 901)
hi there, following this bug report: http://code.google.com/p/flightgear-bugs/issues/detail?id=901 it appears that orientation/side-slip-deg and side-slip-rad don't have the same sign, depending if it's a yasim or a jsbsim plane. is there a commonly adopted convention for this property? if not, shouldn't we document somewhere the meaning of the different fdm properties present in fg tree, to avoid such problems in the future ? jano -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] making sign of side-slip consistent between fdm (bug 901)
As in this image: http://dodlithr.blogspot.com/2011/09/airplanes-stability-axis.html Beta is positive when the wind hits the right side of the vehicle. This is the only standard convention I have ever seen. I would recommend strongly against artificially changing the sign of this parameter as output from JSBSim. Jon -Original Message- From: jean pellotier [mailto:jean.pellot...@wanadoo.fr] Sent: Monday, July 29, 2013 6:27 AM To: FlightGear developers discussions Subject: [Flightgear-devel] making sign of side-slip consistent between fdm (bug 901) hi there, following this bug report: http://code.google.com/p/flightgear-bugs/issues/detail?id=901 it appears that orientation/side-slip-deg and side-slip-rad don't have the same sign, depending if it's a yasim or a jsbsim plane. is there a commonly adopted convention for this property? if not, shouldn't we document somewhere the meaning of the different fdm properties present in fg tree, to avoid such problems in the future ? jano --- --- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.cl ktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] making sign of side-slip consistent between fdm (bug 901)
On 29 Jul 2013, at 13:54, Jon S. Berndt jonsber...@comcast.net wrote: Beta is positive when the wind hits the right side of the vehicle. This is the only standard convention I have ever seen. I would recommend strongly against artificially changing the sign of this parameter as output from JSBSim. Which raises the question, why does Yasim use the opposite sign? Does it use the opposite sign for Beta too? James -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
Re: [Flightgear-devel] making sign of side-slip consistent betweenfdm (bug 901)
This confusion is common. It arises when people try to visualise the angle beta by simply yawing the aircraft, which they at the same time visualise as flying straight in the original direction. (you get the same condition if you yaw the aircraft in a wind tunnel) In this special case beta equals minus yaw angle - which is why they make this mistake. In turning flight there is of course no such simple relationship between sideslip and yaw. Side slip angle beta has the same sign as side slip velocity v. Alan -Original Message- From: Jon S. Berndt Sent: Monday, July 29, 2013 1:54 PM To: 'FlightGear developers discussions' Subject: Re: [Flightgear-devel] making sign of side-slip consistent betweenfdm (bug 901) As in this image: http://dodlithr.blogspot.com/2011/09/airplanes-stability-axis.html Beta is positive when the wind hits the right side of the vehicle. This is the only standard convention I have ever seen. I would recommend strongly against artificially changing the sign of this parameter as output from JSBSim. Jon -Original Message- From: jean pellotier [mailto:jean.pellot...@wanadoo.fr] Sent: Monday, July 29, 2013 6:27 AM To: FlightGear developers discussions Subject: [Flightgear-devel] making sign of side-slip consistent between fdm (bug 901) hi there, following this bug report: http://code.google.com/p/flightgear-bugs/issues/detail?id=901 it appears that orientation/side-slip-deg and side-slip-rad don't have the same sign, depending if it's a yasim or a jsbsim plane. is there a commonly adopted convention for this property? if not, shouldn't we document somewhere the meaning of the different fdm properties present in fg tree, to avoid such problems in the future ? jano --- --- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.cl ktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
[Flightgear-devel] The latest on Download_and_compile.sh
The download_and_compile team clone has been rebuilt as of 1:15 AM Tuesday, July 30, 2013 (UTC) if you cloned it locally, you'll want to move or delete your local clone and get a new one: Get a new clone of the fg-download-and-compile-fgmeta team clone on gitorious: git clone git://gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta.git The team clone can be found at: http://www.gitorious.org/+fg-download-and-compile/fg/fg-download-and-compile-fgmeta Information about using the script is at: http://wiki.flightgear.org/Scripted_Compilation_on_Linux_Debian/Ubuntu Discussions of changes to the script are at: http://wiki.flightgear.org/Talk:Scripted_Compilation_on_Linux_Debian/Ubuntu Tomorrow, I'll request a merge from the team clone to master and next on the main fgmeta. Here's where things stand on the team clone: - master has a copy of the latest approved script version 1.9.11. master should be merged to 2.12.0 next has a copy of the lastes unapproved script version 1.9.12 Changes on Next: rebuild command When download_and_compile.sh is run, the file rebuild is placed in the current build directory. ./rebuild will re-execute ./download_and_compile.sh with the same options it last ran with. -B option The -B allows you to specify a branch as a version # next, master, 2.12.0, 2.10,0, 2.8.0 are supported -R option The R option allows you to select a revision on a branch It defaults to HEAD -G option Allows the selection of a version of OSG for example -G 3.1.9 The Window title gives information about the build while it is in progress. When the build finishes the window will indicate Finished Building. If the build does not finish, the Window title will inidicate where it stopped. OpenRadar can be built The version on next is still undergoing testing, Help out by trying it and reporting bugs. Better yet, join the team and make changes on next. -- Get your SQL database under version control now! Version control is standard for application code, but databases havent caught up. So what steps can you take to put your SQL databases under version control? Why should you start doing it? Read more to find out. http://pubads.g.doubleclick.net/gampad/clk?id=49501711iu=/4140/ostg.clktrk ___ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
