Re: [Flightgear-devel] Real weather

2006-08-08 Thread metaf2xml
On 28/02/06, David Megginson [EMAIL PROTECTED] wrote:
 On 28/02/06, Justin Smithies [EMAIL PROTECTED] wrote:
  
 Also does the weather info include snow and ice ?
  
 As far as I know, the only live weather information used is the METAR.
 The source will be updated every hour or so, and FlightGear might lag
 a little behind that.
  
 The METAR gives the current conditions *on the surface* for a small
 area around an airport, and also reports cloud layers up to the point
 that the sky is fully obscured from the ground.

Additionally, some types of recent weather can be specified in the
Supplementary information of a METAR if it occured since the latest
report or within the last hour, whichever is shorter. Recent snow can be
reported as RESN (if heavy or moderate) or as showers RESHSN or blowing
snow REBLSN.

 The METAR will report
 precipitation (e.g. snow, rain, freezing rain, ice pellets) and its
 severity, as well as (surface) temperature, winds and visibility, but
 will not report snow or ice that has already accumulated on the
 ground.

Some countries publish it in the Remarks section. The USA use the
group SNINCR p/g, e.g.

PASN 161453Z 35032G39KT 1/2SM -SN BLSN OVC015 M10/M13 A2982 RMK AO2 PK WND 
35041/1400 SLP098 SNINCR 1/26 P0002 60002 T11001128 53018 $

reported 1 inch of snow during past hour and 26 inch already on the
ground.

Then there is the group 4/xxx where xxx is the depth of snow on the
ground in inches. And the water equivalent of snow on the ground can be
reported using 933xxx, where xxx is 1/10s of inches. There are also
remarks to describe the state of snow on the ground, e.g. traces, loose,
medium or hard packed. Finally there is a group to report how much of
the sky is obscured by a weather phenomenon; SN6 would mean 6/8th of the
sky is obscured by snow.

PATA had some of these this January:

PATA 191752Z COR 0KT 10SM FEW015 BKN050 M34/M38 A3009 RMK AO2 4/015 933032 
SNB40E49 SLP203 P 6 T13391378 11283 21356 53014

would translate to:

METAR Report(manually corrected)

Airport-Id: PATA
Report time:on the 19., 17:52 UTC
Wind:   calm
Visibility: 16.1 km 10 US-miles
ceiling:at 5000 ft  1520 m
Sky condition:  few clouds at 1500 ft   460 m
broken clouds at 5000 ft1520 m
Temperature:-34°C   -29.2°F
Dewpoint:   -38°C   -36.4°F
relative humidity:  67%
Pressure:   1019 hPa30.09 in. Hg

Remarks:

automated station with precipitation discriminator
Snow on ground: 15 in.
Water equivalent of snow on ground: 3.2 in.
precipitation:  snow:
began at 40 minutes after the hour
ended at 49 minutes after the hour
sea level pressure: 1020.3 hPa  30.13 in. Hg
hourly precip. amount:  0 mm0 in.
6-hour precip. amount:  0 mm0 in.
1h avg. temperature:-33.9°C -29°F
1h avg. dewpoint:   -37.8°C -36°F
6h max. temperature:-28.3°C -18.9°F
6h min. temperature:-35.6°C -32.1°F
3-hourly press. tend.:  decreasing or steady, then increasing; or increasing 
then increasing more rapidly by 1.4 hPa

There may be even more ...

HTH,
Thomas

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] YF-23/yasim: how to climb to 163000 ft

2006-08-08 Thread Joacim Persson

On Tue, 8 Aug 2006, Lee Elliott wrote:


Thanks for posting this observation - this is clearly a bit wacky
(not that accelerating w/o +energy wasn't) - can you reproduce
it?


Now that I tested it again, I saw however that the FF number didn't fall
over from a high number to a negative, but decreased to zero first. Same
goes for N1. But it happens quite suddenly.

KSFO Fair weather, Noon. 2D mini-panel on. Full throttle (no AB, no flaps
or slats). Take-off. Gear up and climb to 1000'. Bank 90° and pull the
stick all the way back. After a while the engine sound suddenly changes to
a low thunder and not only FF goes negative, but so does N1 and EGT.  (I
don't think N2 did though) Tank fills up and overfills quickly. FF is
*very* negative. The number runs off-screeen. If you get too much altitude
the phenomenon stops. Stay low; below 5000', at 1000'
or so ...without crashing into anything -- which isn't that easy to avoid in
70G mach 3 turns. If you ease off throttle, you get the reported phenomenon
with insane speed instead. (mach 8 and 300G). AoA seems to stay at about
16°.

Apparently the magical energy doesn't come from increased mass -- FF is
near zero (and positive) with zero throttle and mass doesn't increase. My
guess is that this is a bug in the yasim jet engine code somewhere. One of
these one-liners that are so hard to find. ;) But at least it's easy to
reproduce.-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] Bug in mp-visibility of planes?

2006-08-08 Thread Mathias Fröhlich

Hi Maik,

On Monday 31 July 2006 23:49, Maik Justus wrote:
  Also that should not stay that long. There is a timeout of 10 seconds
  that an aircraft is kept in the scene even if the network packets do no
  longer arrive.
 
  Can you verify if this is still the case with the cvs version?
 yes, I have the same problem with the cvs version. For cvs I am using
 msvc express while 9.10 I used the compiled windows file.

I have tried to reproduce that with my local linux boxes on 
mpserver02.flightgear.org.
But I can not reproduce any of that problems.

If a MP client leaves the server it stays online for 10 seconds and then 
disappears.
If an unknown model enters the scene it does not appear in the scene. But the 
next known model shows up.

In this case I need some help on windows.
I have somebody on my short range radar :)

   Greetings

  Mathias

-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] YF-23/yasim: how to climb to 163000 ft

2006-08-08 Thread Lee Elliott
On Tuesday 08 August 2006 12:08, Joacim Persson wrote:
 On Tue, 8 Aug 2006, Lee Elliott wrote:
  Thanks for posting this observation - this is clearly a bit
  wacky (not that accelerating w/o +energy wasn't) - can you
  reproduce it?

 Now that I tested it again, I saw however that the FF number
 didn't fall over from a high number to a negative, but
 decreased to zero first. Same goes for N1. But it happens
 quite suddenly.

 KSFO Fair weather, Noon. 2D mini-panel on. Full throttle (no
 AB, no flaps or slats). Take-off. Gear up and climb to 1000'.
 Bank 90° and pull the stick all the way back. After a while
 the engine sound suddenly changes to a low thunder and not
 only FF goes negative, but so does N1 and EGT.  (I don't think
 N2 did though) Tank fills up and overfills quickly. FF is
 *very* negative. The number runs off-screeen. If you get too
 much altitude the phenomenon stops. Stay low; below 5000', at
 1000' or so ...without crashing into anything -- which isn't
 that easy to avoid in 70G mach 3 turns. If you ease off
 throttle, you get the reported phenomenon with insane speed
 instead. (mach 8 and 300G). AoA seems to stay at about 16°.

 Apparently the magical energy doesn't come from increased
 mass -- FF is near zero (and positive) with zero throttle and
 mass doesn't increase. My guess is that this is a bug in the
 yasim jet engine code somewhere. One of these one-liners that
 are so hard to find. ;) But at least it's easy to reproduce.

I think there's now a patch in for the engine problem - don't 
know if it fixes everything though.

LeeE


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel


Re: [Flightgear-devel] YF-23/yasim: how to climb to 163000 ft

2006-08-08 Thread Joacim Persson
On Tue, 8 Aug 2006, Lee Elliott wrote:

 I think there's now a patch in for the engine problem - don't
 know if it fixes everything though.

Well it changed the behaviour somewhat. No more negative FF et al values.
It still accelerates like mad in extreme turns but now we get a SIGSEGV
clue. I got this SIGSEGV three times in a row in the same manner as for the
negative FF effect, so it seems to be reproducable.

#1 (below) is a call to localWind for the thruster calculations, only the 
thruster
altitude is NAN. The altitude comes from the lines just
before the for-loop. (yasim::Model::initIteration, Model.cpp line 100 and on)
   // Need a local altitude for the wind calculation
   float lground[4];
   _s-planeGlobalToLocal(_global_ground, lground);
   float alt = Math::abs(lground[3]);

_global_ground are all NAN:s too. But I think by then, my insane turns had
become insane loopings. (Hard to tell with the view flipping around like
that.) I can't see where the NAN value of _global_ground came from, from a
stack backtrace, so the lead ends there.

On the other hand it's perfectly reasonable that altitude becomes a NAN
under those circumstances -- the aircraft bloody should disintegrate under
that kind of stress. So maybe it isn't a bug after all, rather a realistic
simulation of a massive structural failure due to severe overspeed and
exceeded G limit. ;)  (Altitude? ...of debris and fumes you mean?)


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 9871)]
0x0825a3b8 in yasim::Turbulence::getTurbulence (this=0xa806678, loc=0x0, 
alt=nan(0x40),
 up=0xbfffed60, turbOut=0xbfffedb0) at Turbulence.cpp:100
100 static inline float c2fu(unsigned char c) { return (c+0.5)*(1.0/256); }
(gdb) bt
#0  0x0825a3b8 in yasim::Turbulence::getTurbulence (this=0xa806678, loc=0x0, 
alt=nan(0x40),
 up=0xbfffed60, turbOut=0xbfffedb0) at Turbulence.cpp:100
#1  0x0824fcb5 in yasim::Model::localWind (this=0x9c1222c, pos=0xbfffee40, 
s=0x9c1223c,
 out=0xbfffee30, alt=nan(0x40)) at Model.cpp:544
#2  0x0824e923 in yasim::Model::initIteration (this=0x9c1222c) at Model.cpp:111
#3  0x0824eb00 in yasim::Model::iterate (this=0x9c1222c) at Model.cpp:163
#4  0x08244baa in yasim::FGFDM::iterate (this=0x9c12228, dt=0.0083377) at 
FGFDM.cpp:92
#5  0x0823dab7 in YASim::update (this=0xa92fae0, dt=0.01524188350679) at 
YASim.cxx:217
#6  0x080520bd in fgUpdateTimeDepCalcs () at main.cxx:163
#7  0x08052cb6 in fgMainLoop () at main.cxx:488
#8  0x08087492 in GLUTidle () at fg_os.cxx:124
#9  0x400a5929 in __glutRegisterEventParser () from /usr/X11R6/lib/libglut.so.3
#10 0x400a60ad in glutMainLoop () from /usr/X11R6/lib/libglut.so.3
#11 0x0805582b in fgMainInit (argc=2, argv=0xb464) at main.cxx:1021
#12 0x08051a86 in main (argc=2, argv=0xb464) at bootstrap.cxx:203


-
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnkkid=120709bid=263057dat=121642
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel