Re: [Flightgear-devel] Bug in moving-average filter?
On Friday 16 Sep 2005 21:11, Roy Vegard Ovesen wrote: > Lee Elliot: > > Hello List, > > > > I think there's a small bug in the moving-average filter in > > xmlauto.cxx > > > > I noticed that the output from it was always out a bit and > > checking with a calculator showed that it seemed to be > > dividing by the number of samples + 1 instead of just the > > number of samples. > > > > subtracting 1 from 'samples' in line 702 seems to fix the > > problem and as 'samples' doesn't seem to be used elsewhere I > > think it's safe. Possibly implies that the number of > > samples may be one less than specified but I'm not familiar > > enough with c++ to spot it. > > You are right. I would suggest resizing input[] to (samples + > 1) instead. Change lines 654 and 661 to: > > input.resize(samples + 1, 0.0); > > That way we average over the number of samples as configured. > > Can anyone commit this?! the 'fix' in line 702 didn't feel right to me... ...better fixed up-stream. :) LeeE ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Bug in moving-average filter?
Done ... Roy Vegard Ovesen wrote: Lee Elliot: Hello List, I think there's a small bug in the moving-average filter in xmlauto.cxx I noticed that the output from it was always out a bit and checking with a calculator showed that it seemed to be dividing by the number of samples + 1 instead of just the number of samples. subtracting 1 from 'samples' in line 702 seems to fix the problem and as 'samples' doesn't seem to be used elsewhere I think it's safe. Possibly implies that the number of samples may be one less than specified but I'm not familiar enough with c++ to spot it. You are right. I would suggest resizing input[] to (samples + 1) instead. Change lines 654 and 661 to: input.resize(samples + 1, 0.0); That way we average over the number of samples as configured. Can anyone commit this?! -- Curtis Olsonhttp://www.flightgear.org/~curt HumanFIRST Program http://www.humanfirst.umn.edu/ FlightGear Project http://www.flightgear.org Unique text:2f585eeea02e2c79d7b1d8c4963bae2d ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re:[Flightgear-devel] Bug in moving-average filter?
Lee Elliot: > Hello List, > > I think there's a small bug in the moving-average filter in > xmlauto.cxx > > I noticed that the output from it was always out a bit and > checking with a calculator showed that it seemed to be dividing > by the number of samples + 1 instead of just the number of > samples. > > subtracting 1 from 'samples' in line 702 seems to fix the problem > and as 'samples' doesn't seem to be used elsewhere I think it's > safe. Possibly implies that the number of samples may be one > less than specified but I'm not familiar enough with c++ to spot > it. You are right. I would suggest resizing input[] to (samples + 1) instead. Change lines 654 and 661 to: input.resize(samples + 1, 0.0); That way we average over the number of samples as configured. Can anyone commit this?! -- Roy Vegard Ovesen ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] [OT] Outlook help
Richard Bytheway wrote: > I am about to go away for a week, and would like to setup my > out-of-office thing in Outlook (corporate setting - no choice on > email client). However I would like to prevent it replying to this, > and other, lists that I am on. Does anyone know if this is > possible, and if so how to do it? Resubscribe with a gmail account? (I'm serious, btw -- even your employer would probably appreciate it, personal email on work accounts is broadly frowned upon). That said, I believe that RFC822 and descendents actually specify a way to flag a message as an auto-reply, and that most list software supports it. It might "just work" ... :) Andy ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] [OT] Outlook help
I am about to go away for a week, and would like to setup my out-of-office thing in Outlook (corporate setting - no choice on email client). However I would like to prevent it replying to this, and other, lists that I am on. Does anyone know if this is possible, and if so how to do it? Thanks, Richard This e-mail has been scanned for Bede Scientific Instruments for all viruses by Star Internet. The service is powered by MessageLabs. For more information on a proactive anti-virus service working around the clock, around the globe, visit: http://www.star.net.uk ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
[Flightgear-devel] quick newbie questions
Still sorting through some docs, but I'm curious, is it possible to use flight gear as a generic visualization tool? What I'd like to do is have two or three UAV's flying around with (so would need multiple flight models active at once), and an api interface for these flight models to be driven by some AI code I'll be cooking up. I'd also like api interface for controlling the viewpoint, because being UAV's, there isn't a cockpit to be inside of :) Are there hooks for this stuff? Would it be hard to add, or should I start from a lower level with my own visualization using simgear as a base? ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:
Martin Spott wrote: > Yep, looks good adding to that I suggest to replace "alut.h" with > "alext.h" or simply remove it in simgear/sound/sample_openal.hxx, line > 50, maybe line 47 as well as alut now lives in a separate tree in the > OpenAL source, O.k., I see, this is the wrong approach Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:
Erik Hofman wrote: > You will need to add "#include " right after AL/al.h Yep, looks good adding to that I suggest to replace "alut.h" with "alext.h" or simply remove it in simgear/sound/sample_openal.hxx, line 50, maybe line 47 as well as alut now lives in a separate tree in the OpenAL source, Thanks, Martin. -- Unix _IS_ user friendly - it's just selective about who its friends are ! -- ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] cygwin problems (was Re cvslogs etc)
David Luff > On 16/09/2005 at 10:34 Vivian Meazza wrote: > > >Erik Hofman > > > >> Vivian Meazza wrote: > >> > >> > Er ... Erik are you about to break Cygwin again? > >> > >> BTW, form the openal (1.1) Changelog: > >> > >> * More fixes for Cygwin/MinGW compilation plus some #include cleanups. > >> The "linux" subtree compiles now under Linux, MinGW/MSYS and Cygwin > >> (with and without "-mno-cygwin"). > >> > >> Erik > >> > > Fantastic :-) > > > > >That sounds like really good news, but I hardly dare try - cvs has been > >more > >or less broken under Cygwin since mid Aug. There are work-arounds but > > > >Vivian > > > > If you mean FG cvs, it's compiling and running fine for me under Cygwin at > the moment, with the exception of a couple of files in the utils directory > that are easily tweaked to work. I haven't updated Cygwin for a while > though - it's gcc version 3.3.3. It's possible I'm carrying local mods > though that I've forgotten about. What problems are you seeing? > In addition to those there's one general problem - --real-weather-fetch which causes YASim to segfault. There's a workaround with JBSim. Harald's working on a fix. There's a problem which you probably aren't aware of - there's some new MP code around which I'm testing, but which needs a fix to enable it to compile under Cygwin. And of course there was the bug (in 3d clouds IIRC) which had me tearing my hair out for the last 2 weeks of Aug. Fixed now - phew. Like you, I have tweaked things so that cvs does compile under Cygwin. But technically it's broken. The OpenAL sounds like good news. I'll have to untangle Norman's OpenAL fix first though, I expect. Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] cygwin problems (was Re cvslogs etc)
On 16/09/2005 at 10:34 Vivian Meazza wrote: >Erik Hofman > >> Vivian Meazza wrote: >> >> > Er ... Erik are you about to break Cygwin again? >> >> BTW, form the openal (1.1) Changelog: >> >> * More fixes for Cygwin/MinGW compilation plus some #include cleanups. >> The "linux" subtree compiles now under Linux, MinGW/MSYS and Cygwin >> (with and without "-mno-cygwin"). >> >> Erik >> Fantastic :-) > >That sounds like really good news, but I hardly dare try - cvs has been >more >or less broken under Cygwin since mid Aug. There are work-arounds but > >Vivian > If you mean FG cvs, it's compiling and running fine for me under Cygwin at the moment, with the exception of a couple of files in the utils directory that are easily tweaked to work. I haven't updated Cygwin for a while though - it's gcc version 3.3.3. It's possible I'm carrying local mods though that I've forgotten about. What problems are you seeing? Cheers - Dave This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:FlightGear configure.ac, 1.94, 1.95
Erik Hofman > > Vivian Meazza wrote: > > > Er ... Erik are you about to break Cygwin again? > > No, should I? > :-) well, we've made a pretty good job of trying over the past month or so. Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re:[Flightgear-cvslogs] CVS:FlightGear configure.ac, 1.94, 1.95
Erik Hofman > Vivian Meazza wrote: > > > Er ... Erik are you about to break Cygwin again? > > BTW, form the openal (1.1) Changelog: > > * More fixes for Cygwin/MinGW compilation plus some #include cleanups. > The "linux" subtree compiles now under Linux, MinGW/MSYS and Cygwin > (with and without "-mno-cygwin"). > > Erik > That sounds like really good news, but I hardly dare try - cvs has been more or less broken under Cygwin since mid Aug. There are work-arounds but Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:FlightGear configure.ac, 1.94, 1.95
Vivian Meazza wrote: Er ... Erik are you about to break Cygwin again? BTW, form the openal (1.1) Changelog: * More fixes for Cygwin/MinGW compilation plus some #include cleanups. The "linux" subtree compiles now under Linux, MinGW/MSYS and Cygwin (with and without "-mno-cygwin"). Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:FlightGear configure.ac, 1.94, 1.95
Vivian Meazza wrote: Er ... Erik are you about to break Cygwin again? No, should I? Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
RE: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:FlightGear configure.ac, 1.94, 1.95
Erik Hofman > Martin Spott wrote: > > Hello Erik, > > > > Erik Hofman wrote: > > > >>Update of /var/cvs/FlightGear-0.9/FlightGear > >>In directory baron:/tmp/cvs-serv29428 > >> > >>Modified Files: > >>configure.ac > >>Log Message: > >>Prepare for OpenAL 1.1 and a separate alut lubrary. Er ... Erik are you about to break Cygwin again? Regards Vivian ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Electrical system properties
On Thu, Sep 15, 2005 at 09:57:56PM -0400, Steve Knoblock wrote:
> In NASAL, when I write
>
> elec = getprop("/systems/electrical/volts[0]");
> print("elec:");
> print(elec);
>
> It prints nothing.
If you do that at startup time, the property may not be
known yet. In this case use something like
INIT = func {
elec = ...
}
settimer(INIT, 0);
___
Flightgear-devel mailing list
Flightgear-devel@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Re: [Flightgear-cvslogs] CVS:
Martin Spott wrote: No such message as this one ? cc-1020 cc: ERROR File = arch/irix/iris.c, Line = 415 The identifier "AL_FORMAT_QUAD8_LOKI" is undefined. case AL_FORMAT_QUAD8_LOKI: Ah, yes, now that you mention it. You will need to add "#include " right after AL/al.h Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
Re: [Flightgear-devel] Electrical system properties
Steve Knoblock wrote: Are the electrical system properties readable? All properties are always readable. The only restriction might be write access. Erik ___ Flightgear-devel mailing list Flightgear-devel@flightgear.org http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
