From: Bertrand C. <bco...@gm...> - 2018-10-17 22:16:50
|
Le dim. 14 oct. 2018 à 12:16, Bertrand Coconnier <bco...@gm...> a écrit : > Hi, > > I'm quite busy at the moment but I plan to open an issue on GitHub about > that issue. > > Basically, there was 2 distinct issues : > > * The humidity feature needs some additional care to handle very high > altitude flights because, above ~150,000 ft the saturated vapor pressure > can become higher than the ambient pressure and in that case the humidity > rate HR can no longer reach 100% or we get negative density. > I have filled an issue on GitHub for the bug above. Bertrand. > > * The routine to compute the standard temperature in FGStandardAtmosphere > was using equations above 360,892 ft that were not accounted for in the > temperature computations in GetTemperature(). That was causing a drift in > the temperature bias to keep the ambient temperature constant and equal to > the value requested by FlightGear (-76.5°C/354°R). At some point, the > temperature was even becoming negative in Kelvin and Rankine !!! > > Bertrand. > > Le mer. 10 oct. 2018 à 11:19, Alan Teeder <ajt...@v-...> a > écrit : > >> >> >> *From:* Sean McLeod >> *Sent:* Wednesday, October 10, 2018 9:19 AM >> *To:* Development issues >> *Subject:* Re: [Jsbsim-devel] PythonJSBSim link error with VS 2017 >> >> >> Hi Alan >> >> >> >> So what was the fix to get it past 150,000ft? >> >> >> >> Cheers >> >> >> >> >> >> ------------------ >> >> Sean >> >> >> >> Bertrand pushed a fix to flightgear. It does not look as if he pushed >> them to JSBSim itself. >> >> >> >> Alan >> > |