Re: [Flightgear-devel] instrument patches

[Victhor]

Thanks! I've been looking for this for ages! :)
> Hello ,
> This patch adds the option of a barber pole in the airspeed
> indicator, adapted from K. Hoercher's nasal code for my b1900d...
>  It is enabled like this in the instrumentation.xml file : 
> 
> 
> airspeed-indicator
> 0
> 
> /systems/pitot/total-pressure-inhg
> 
> /systems/static/pressure-inhg
> 1 ... defaults to 0 / off
>  airspeed limit (Vmo) defaults to 248.0
>  mach limit (Mmo) defaults to 0.48
>  changeover altitude / defaults
> to 13200 ft
> 
> 
> These are the B1900D figures.
> If the extra options are left out ... no barber pole calculation is
> done.
> 
> The patch also includes the dme nav2 fix that I posted previously.
> 
> Could someone take a look and commit please ?
> Thanks ,
> 
> 
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___ Flightgear-devel mailing list 
> Flightgear-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel



--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] instrument patches

[James Turner]

On 9 Mar 2010, at 07:04, syd adams wrote:

> The patch also includes the dme nav2 fix that I posted previously.
> 
> Could someone take a look and commit please ?

I'm testing these now, and will commit in a couple of moments.

James


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Web Site

[Pete Morgan]

Curtis Olson wrote:
> Hi Pete,
>
> Definitely nice work on the page layout.  It's my job to play devil's 
> advocate so to speak, so don't take this as criticism, but instead I'm 
> just trying to think through all the important issues beyond "hey that 
> looks really nice."
>
> I'm not very familiar with google apps engine which you used to 
> develop this page, but it does look like a very nice and powerful 
> service.  There would be lots of good points to using it.
>
> On the other hand we should consider and discuss some of the possible 
> down sides to google apps engine.
>
> - Everything we develop for this site and all the database data is in 
> a format that depends on google's proprietary services.
>
> - We would be forced to host the site on google's servers (free 
> hosting up to a certain bandwidth/cpu limitation)
>
> - There would be no possibility of ever moving/porting the site to 
> another host because the entire site is dependent on the google apps 
> infrastructure.
>
> - Do we want to lock ourselves into google?
These issues worry me also, and indeed pointing www.flightgear.org to 
fg-www.appspot.com is likely to have other problems (major 404's will 
need to be handled)

A Major issues is that GAE does not support binary files very well, eg 
gallery, so I'm not sure how this would work. One possibility would be 
to rename the current machine as "www2." or "stash." and using it as the 
binary storage.

The main site fg-www has no database, so the design could be ported to 
the current site quite easily, as it used the Django templating engine.

 Does the current server have python or php installed ?
>
> We might decide that none of these issues are an overriding concern. 
>  I use google for my email, I use google docs more and more heavily, I 
> use google search 100's of times a day, I have a google android cell 
> phone, I use google's calendar service, I basically don't use my nuvi 
> any more now that google maps came out with a live navigation 
> application that runs on my phone.  I've been running google chrome on 
> my desktop now instead of firefox because it uses a lot fewer system 
> resources for the 30-40 web tabs I have open across 3 virtual desktops 
> at any given time on my computer. I'm probably still forgetting half 
> the google things I use every day.  I'd be SOL if google evaporated 
> from the planet.  So what's one more dependency?
Maybe we should ask Google to sponsor FlightGear?
> But that said, we should make sure we go a step beyond "looks great" 
> and understand what we would be getting ourselves into, and at least 
> make some conscious decision (even if we don't have 100% group 
> agreement ... we never have 100% agreement.) :-)
>
Can I make a suggestion. Shall I knock up a "report" of the way it could 
go so issues can be identified ?

pete


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Web Site

[Pete Morgan]

Heiko Schulz wrote:
>
> I heard Google will rename our planet soon in GoogleEarth;-)
>
> I admit to Curt in a lot of points here. The only advantage is there is no 
> advertisement, which makes the current page look really bad. 
>   
Adverts can be dropped in where required. However an observation here is 
that my 10 year olde nephew downloaded some backup software as this was 
a featured advert in the main page above the "downlaod flightgear" section.
> On the other side I like the clear structure of this new concept, the NOTAM 
> is a great idea! I like that it makes use of a newer and fresh logo as the 
> current one is from the last century.
>   
One of my dislikes is the dropdown navigation. mainly because its 
javascript and not search engine friendly.
> Only small things which could maybe improved:
>
> -the visual appearence needs still a little "kick"- maybe This logo: 
> http://wiki.flightgear.org/images/3/3b/Wiki_logo.png with more different 
> aircrafts as the A10 as header bar 
>   
Whilst I like the logo, I dislike it because it contains an efficient 
American Killing Machine and makes FlightGear look like a shoot up.
> - a simple, good looking button "2.0.0" with a link straight link to the 
> Download page 
>   
The home page needs some more thought imho.
> -I miss the fact that we are OpenSource on the main page. Still a lot of 
> people thinks we are commercial and all developers are salaried workers for 
> "FlightGear" which leds to confusion
>   
Its at the top " /The World's Leading Open Source Flight Simulator" - 
but see point above.
/
>
> Is this style and Design of this concept proteced by any licence? If not We 
> could just take it over and find a place for the advertisement...
>   
Not at all. I am not a designer, merely a developer. In fact a designer 
would be really helpful.. anyone ? Gijs ?
> Or maybe better: make a package of FGFS with the whole Scenery, sell it for 
> less than 30Dollars for those who doesn't want and can't to download all 
> stuff. That would probably help against FPS and keep the page running without 
> advertisement
>   
That's why I mentioned a while back making a donation/contribution to 
FG, which I would go towards Infrastructure costs.

pete
>
> Cheers
> Heiko
>
>
>
> __
> Do You Yahoo!?
> Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz 
> gegen Massenmails. 
> http://mail.yahoo.com 
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>   


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] found some bugs with CVS 22012010

[Forums Virgin Net]

I have noticed a lot of bugs lately and thought I might try and help by doing a 
search through all the cvs for all the errors I find here is a report below of 
some of them.

WHERE 22012010 = DATA  Directory for that cvs date

In fgfs binary dated 22012010

ERROR
Could not find at least one of the following objects for animation:

RAlt.Bug

REFERENCES
09/03/2010 12:24:43
Search String: RAlt.Bug
Replace String: 
Path: G:\datacvs\22012010\
File Mask: *
Search Subdirectories, Regular Expression

Processing file : 
G:\datacvs\22012010\Aircraft\Carreidas\Models\Interior\Panel\Instruments\radar-alt\kra10a.ac
Line 1351 - name "RAlt.bug"
Found 1 occurrences.

Processing file : 
G:\datacvs\22012010\Aircraft\Carreidas\Models\Interior\Panel\Instruments\radar-alt\kra10a.xml
Line 81 - RAlt.bug
Found 1 occurrences.

Processing file : 
G:\datacvs\22012010\Aircraft\ec135\instrumentation\radar-alt\kra10a.ac
Line 1351 - name "RAlt.bug"
Found 1 occurrences.

Processing file : 
G:\datacvs\22012010\Aircraft\ec135\instrumentation\radar-alt\kra10a.xml
Line 81 - RAlt.Bug
Found 1 occurrences.

Processing file : 
G:\datacvs\22012010\Aircraft\Sikorsky-76C\Models\Instruments\Ralt.ac
Line 860 - name "RAlt.bug"
Found 1 occurrences.

Processing file : 
G:\datacvs\22012010\Aircraft\Sikorsky-76C\Models\Instruments\Ralt.xml
Line 41 - RAlt.bug
Found 1 occurrences.

Searched 102186 file(s), found 6 occurrences in 6 file(s)

Aerotro--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Google Summer of Code

[Curtis Olson]

On Tue, Mar 9, 2010 at 8:08 AM, Pete Morgan  wrote:

> Has/Does FlightGear participate ?
>
>
> http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html


We have never participated before, but I see the deadline for organizations
to apply is March 12 ... coming right up.  It's not like I've got nothing
else to do, but I like the idea of mentoring.  I can think of many
individuals who have played a mentor roll from time to time for me and I am
very appreciative of that.  So I am submitting an application for FlightGear
(assuming no one else has already.)

Here are some things we need:

1. Mentors
2. Student applicants (mentorees).
3. A web page listing project/mentoring ideas

1 & 3 are the most important to have lined up before March 12 (Friday.)

The organization application has some questions that I'd love to have some
help thinking about and answering:

1. What criteria did you use to select the individuals who will act as
mentors for your organization? Please be as specific as possible.

2. What is your plan for dealing with disappearing students?

3. What is your plan for dealing with disappearing mentors?

4. What steps will you take to encourage students to interact with your
project's community before, during and after the program?

5. What will you do to ensure that your accepted students stick with the
project after GSoC concludes?

6. What would our organization expect to gain from this experience?

As you can see, this would not be a trivial undertaking for the FlightGear
project, and it's not something I can carry entirely on my own shoulders.
 Do we have others in the project that would be willing to volunteer their
time and participate in a mentoring and organizational roll?

We also need to quickly assemble a list of possible student project ideas
... and these need to be well measured ... like you would measure a pass in
soccer/futbol.  We want to avoid things that are too hard or too easy.  The
ball needs to arrive with the correct pace so the student can handle it.  We
want suggestions that could be attainable by a *student* in the allotted
time frame (summer?) and realize that a student may have to spend a good
chunk of their time learning about the FlightGear structure before they can
advance with their project.

I think we should avoid suggesting projects that are in FlightGear's
critical path.  I.e. "add aircraft shadows" might be an tempting project to
suggest, but is this student level work that could be finished in a summer?
 Do we want to pin all our hopes for aircraft shadows in FlightGear on a
google summer of code student who may bugout mid stream if it starts looking
too hard?  If it does get too hard, does that student "fail" or is it us
that failed as a mentoring organization?

So for project suggestions I think we should focus on projects that have the
best chance of teaching student level people, have the best chance of being
attainable in a summer of effort, have the best chance of helping a student
to gain confidence, knowledge, experience, etc.  We should be
careful/resistant to suggesting projects that are simply FlightGear feature
wishlist items.  We should suggest projects that the mentors have some idea
of a clear path to a solution (i.e. not so much research into new and
unknown things.)

I think to be successful, we need to keep our focus on the mentoring aspect
of this.  The focus is to help bring some of the younger generation up to
speed more quickly by sharing our experiences and knowledge.  It's something
we do already to some extent in a casual context.  The google program just
makes it official.  The mentors commit some time to sharing their experience
and knowledge and the students commit to actually listening and respecting
what is shared. :-)

Those are my thoughts.  I can get the ball rolling, but I can't do it all
myself.

Thanks,

Curt.
-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Google Summer of Code

[Curtis Olson]

One more thing we need.  I need someone to sign up on the google summer of
code page and create an ID for themselves.  The applications requires a
"backup admin" link id and it will not let me enter myself.

Thanks,

Curt.


On Tue, Mar 9, 2010 at 9:39 AM, Curtis Olson > wrote:

> On Tue, Mar 9, 2010 at 8:08 AM, Pete Morgan  wrote:
>
>> Has/Does FlightGear participate ?
>>
>>
>> http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html
>
>
> We have never participated before, but I see the deadline for organizations
> to apply is March 12 ... coming right up.  It's not like I've got nothing
> else to do, but I like the idea of mentoring.  I can think of many
> individuals who have played a mentor roll from time to time for me and I am
> very appreciative of that.  So I am submitting an application for FlightGear
> (assuming no one else has already.)
>
> Here are some things we need:
>
> 1. Mentors
> 2. Student applicants (mentorees).
> 3. A web page listing project/mentoring ideas
>
> 1 & 3 are the most important to have lined up before March 12 (Friday.)
>
> The organization application has some questions that I'd love to have some
> help thinking about and answering:
>
> 1. What criteria did you use to select the individuals who will act as
> mentors for your organization? Please be as specific as possible.
>
> 2. What is your plan for dealing with disappearing students?
>
> 3. What is your plan for dealing with disappearing mentors?
>
> 4. What steps will you take to encourage students to interact with your
> project's community before, during and after the program?
>
> 5. What will you do to ensure that your accepted students stick with the
> project after GSoC concludes?
>
> 6. What would our organization expect to gain from this experience?
>
> As you can see, this would not be a trivial undertaking for the FlightGear
> project, and it's not something I can carry entirely on my own shoulders.
>  Do we have others in the project that would be willing to volunteer their
> time and participate in a mentoring and organizational roll?
>
> We also need to quickly assemble a list of possible student project ideas
> ... and these need to be well measured ... like you would measure a pass in
> soccer/futbol.  We want to avoid things that are too hard or too easy.  The
> ball needs to arrive with the correct pace so the student can handle it.  We
> want suggestions that could be attainable by a *student* in the allotted
> time frame (summer?) and realize that a student may have to spend a good
> chunk of their time learning about the FlightGear structure before they can
> advance with their project.
>
> I think we should avoid suggesting projects that are in FlightGear's
> critical path.  I.e. "add aircraft shadows" might be an tempting project to
> suggest, but is this student level work that could be finished in a summer?
>  Do we want to pin all our hopes for aircraft shadows in FlightGear on a
> google summer of code student who may bugout mid stream if it starts looking
> too hard?  If it does get too hard, does that student "fail" or is it us
> that failed as a mentoring organization?
>
> So for project suggestions I think we should focus on projects that have
> the best chance of teaching student level people, have the best chance of
> being attainable in a summer of effort, have the best chance of helping a
> student to gain confidence, knowledge, experience, etc.  We should be
> careful/resistant to suggesting projects that are simply FlightGear feature
> wishlist items.  We should suggest projects that the mentors have some idea
> of a clear path to a solution (i.e. not so much research into new and
> unknown things.)
>
> I think to be successful, we need to keep our focus on the mentoring aspect
> of this.  The focus is to help bring some of the younger generation up to
> speed more quickly by sharing our experiences and knowledge.  It's something
> we do already to some extent in a casual context.  The google program just
> makes it official.  The mentors commit some time to sharing their experience
> and knowledge and the students commit to actually listening and respecting
> what is shared. :-)
>
> Those are my thoughts.  I can get the ball rolling, but I can't do it all
> myself.
>
> Thanks,
>
> Curt.
> --
> Curtis Olson: http://baron.flightgear.org/~curt/
>



-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] instrument patches

[syd adams]

If you see places for improvement or accuracy  , updates are welcome . This
was based on the nasal code , and I didnt research much other than to read
the pages listed in that nasal piece.
And thanks for reading and commiting , James.
Cheers

On Tue, Mar 9, 2010 at 3:19 AM, James Turner  wrote:

>
> On 9 Mar 2010, at 09:18, James Turner wrote:
>
> >> Could someone take a look and commit please ?
> >
> > I'm testing these now, and will commit in a couple of moments.
>
> Committed now, with some changes:
>
>  - I've switched the pressure-alt source to be configurable, instead of
> hard-coded; it defaults to /instruments/altimeter/pressure-alt-ft
>  - the ias and mach limits are read each frame, so they could (potentially)
> be updated from Nasal
>  - I've removed the default values for alt-threshold / ias-limit /
> mach-limit, on the assumption that anyone enabling the barber-pole will
> supply appropriate values. If people disagree with that, adding back the
> B1900 values (or similar) as default is easy.
>
> My biggest concern is that the code references /velocities/mach to compute
> the mach-limit, which seems undesirable - instruments should read/compute
> values based on physical properties if possible - that's certainly the
> philosophy of the basic instruments.
>
> Ideally, we would extend the airspeed indicator to compute Mach as
> described here:
>
>http://williams.best.vwh.net/avform.htm#Mach
>
> I know OAT is available trivially, which lets us compute CS (speed of
> sound) easily, but computing TAS from IAS is more complex, as the formulae
> show. If someone can explain the formuale in detail to me, I'd be happy to
> add a 'indicated-mach' property to the airspeed indicator code (effectively
> allowing it to be used as a mach-meter too), and then use that mach value
> for the mach-limit computation.
>
> Comments? I guess all the formulae required already exist elsewhere in the
> code.
>
> Regards,
> James
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] instrument patches

[James Turner]

On 9 Mar 2010, at 09:18, James Turner wrote:

>> Could someone take a look and commit please ?
> 
> I'm testing these now, and will commit in a couple of moments.

Committed now, with some changes:

 - I've switched the pressure-alt source to be configurable, instead of 
hard-coded; it defaults to /instruments/altimeter/pressure-alt-ft
 - the ias and mach limits are read each frame, so they could (potentially) be 
updated from Nasal
 - I've removed the default values for alt-threshold / ias-limit / mach-limit, 
on the assumption that anyone enabling the barber-pole will supply appropriate 
values. If people disagree with that, adding back the B1900 values (or similar) 
as default is easy.

My biggest concern is that the code references /velocities/mach to compute the 
mach-limit, which seems undesirable - instruments should read/compute values 
based on physical properties if possible - that's certainly the philosophy of 
the basic instruments.

Ideally, we would extend the airspeed indicator to compute Mach as described 
here:

http://williams.best.vwh.net/avform.htm#Mach

I know OAT is available trivially, which lets us compute CS (speed of sound) 
easily, but computing TAS from IAS is more complex, as the formulae show. If 
someone can explain the formuale in detail to me, I'd be happy to add a 
'indicated-mach' property to the airspeed indicator code (effectively allowing 
it to be used as a mach-meter too), and then use that mach value for the 
mach-limit computation.

Comments? I guess all the formulae required already exist elsewhere in the code.

Regards,
James


--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Web Site

[HB-GRAL]

Pete Morgan schrieb:
> Not at all. I am not a designer, merely a developer. In fact a designer 
> would be really helpful.. anyone ? Gijs ?

I am working as graphic and web designer for many years. As I saw your 
new site my first impression was there is already a designer at work. 
But when you need help I can help you of course, also for another 
engine. -Yves

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Google Summer of Code

[Alex Perry]

On Tue, Mar 9, 2010 at 6:08 AM, Pete Morgan  wrote:
> Has/Does FlightGear participate ?

Not that I'm aware of.  I don't see any reason why not, except that it
does require someone to take on the mentoring responsibilities.  Maybe
that has been sufficient discouragement in the past:
http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#org_role

> http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html

If someone would like to mentor students on FGFS projects, but nobody
else is comfortable taking on the Administrator role for FlightGear as
defined by the gSoC program, let me know.  If someone has a student
project in mind for which I would be the ideal mentor, feel free to
tell me about it ... because I don't have anything in mind and by
default won't be applying for mentorship.

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Google Summer of Code

[Pete Morgan]

Has/Does FlightGear participate ?

http://google-opensource.blogspot.com/2010/03/google-summer-of-code-applications-now.html

pete

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Web Site

[Curtis Olson]

Hi Pete,

Another option (perhaps my favorite at the moment) would be to pull in CSS
and design elements from your google app engine example and roll them into
the current flightgear web page design.  We may need to give up on some of
the "app" elements or rewrite them in a way that is supported by more
typical web hosting services.

Regards,

Curt.


On Tue, Mar 9, 2010 at 4:07 AM, Pete Morgan wrote:

> Heiko Schulz wrote:
> >
> > I heard Google will rename our planet soon in GoogleEarth;-)
> >
> > I admit to Curt in a lot of points here. The only advantage is there is
> no advertisement, which makes the current page look really bad.
> >
> Adverts can be dropped in where required. However an observation here is
> that my 10 year olde nephew downloaded some backup software as this was
> a featured advert in the main page above the "downlaod flightgear" section.
> > On the other side I like the clear structure of this new concept, the
> NOTAM is a great idea! I like that it makes use of a newer and fresh logo as
> the current one is from the last century.
> >
> One of my dislikes is the dropdown navigation. mainly because its
> javascript and not search engine friendly.
> > Only small things which could maybe improved:
> >
> > -the visual appearence needs still a little "kick"- maybe This logo:
> http://wiki.flightgear.org/images/3/3b/Wiki_logo.png with more different
> aircrafts as the A10 as header bar
> >
> Whilst I like the logo, I dislike it because it contains an efficient
> American Killing Machine and makes FlightGear look like a shoot up.
> > - a simple, good looking button "2.0.0" with a link straight link to the
> Download page
> >
> The home page needs some more thought imho.
> > -I miss the fact that we are OpenSource on the main page. Still a lot of
> people thinks we are commercial and all developers are salaried workers for
> "FlightGear" which leds to confusion
> >
> Its at the top " /The World's Leading Open Source Flight Simulator" -
> but see point above.
> /
> >
> > Is this style and Design of this concept proteced by any licence? If not
> We could just take it over and find a place for the advertisement...
> >
> Not at all. I am not a designer, merely a developer. In fact a designer
> would be really helpful.. anyone ? Gijs ?
> > Or maybe better: make a package of FGFS with the whole Scenery, sell it
> for less than 30Dollars for those who doesn't want and can't to download all
> stuff. That would probably help against FPS and keep the page running
> without advertisement
> >
> That's why I mentioned a while back making a donation/contribution to
> FG, which I would go towards Infrastructure costs.
>
> pete
> >
> > Cheers
> > Heiko
> >
> >
> >
> > __
> > Do You Yahoo!?
> > Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz
> gegen Massenmails.
> > http://mail.yahoo.com
> >
> >
> --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ___
> > Flightgear-devel mailing list
> > Flightgear-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/flightgear-devel
> >
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>



-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] anti windup for the pi-simple-controller

[Torsten Dreyer]

Hi,

I am about to commit a change that adds anti windup logic to the pi-simple-
controller (FGPISimpleController) which currently lacks such functionality.

The FGPIDController has some anti windup logic but that controller does not 
suit very well for some solutions and one might (I do) want to use the pi-
simple-controller instead, if this just had some anti windup.

My question is: should I add a switch to make the pi-simple-controller behave 
like it currently does, e.g. add something like 
true
and default that switch to 'false'?
This should be a good idea if some autopilots relied on wound up 
PISimpleController. Or is it oversized backwards-compatibility?
I can't imagine a single case where wind-up is a good idea - but who knows...

Comments?
Torsten

BTW. the patch is really simple:
 double output = prop_comp + int_sum;
-output = clamp( output );
-set_output_value( output );
+double clamped_output = clamp( output );
+if( output != clamped_output ) // anti-windup
+  int_sum = clamped_output - prop_comp;
+
+set_output_value( clamped_output );

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] anti windup for the pi-simple-controller

[Curtis Olson]

On Tue, Mar 9, 2010 at 12:15 PM, Torsten Dreyer wrote:

> Hi,
>
> I am about to commit a change that adds anti windup logic to the pi-simple-
> controller (FGPISimpleController) which currently lacks such functionality.
>
> The FGPIDController has some anti windup logic but that controller does not
> suit very well for some solutions and one might (I do) want to use the pi-
> simple-controller instead, if this just had some anti windup.
>
> My question is: should I add a switch to make the pi-simple-controller
> behave
> like it currently does, e.g. add something like
> true
> and default that switch to 'false'?
> This should be a good idea if some autopilots relied on wound up
> PISimpleController. Or is it oversized backwards-compatibility?
> I can't imagine a single case where wind-up is a good idea - but who
> knows...
>
> Comments?
> Torsten
>
> BTW. the patch is really simple:
> double output = prop_comp + int_sum;
> -output = clamp( output );
> -set_output_value( output );
> +double clamped_output = clamp( output );
> +if( output != clamped_output ) // anti-windup
> +  int_sum = clamped_output - prop_comp;
> +
> +set_output_value( clamped_output );
>

Speaking as the author of the original PISimpleController code I think some
anti-windup logic would be a good additive feature.  I don't think we would
need a switch to maintain the old behavior (unless we want to demonstrate to
someone why anti-windup is a good idea ... but in that case, the switch
should be to turn it off, not turn it on.)

Another thing that would be possibly interesting is the addition of a D
component which I never included.

Generally I use the more advanced PID controller for everything except P
only controllers.

Regards,

Curt.
-- 
Curtis Olson: http://baron.flightgear.org/~curt/
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Linker problems

[Roland Haeder]

Hi all,

I still have linker problems. I use the following compiler and linker:

- GCC 4.4.3-3 (Debian Unstable)
- GNU ld (GNU Binutils for Debian) 2.20

I still got tons of these messages:
---
libMain.a(main.o): In function `osg::Referenced::unref() const':
/usr/local/include/osg/Referenced:194: undefined reference to
`osg::Referenced::signalObserversAndDelete(bool, bool, bool) const'
---

OSG is 2.9.7 can compiles without errors (no special options specified).

SimGear is recent CVS (updated some minutes ago) and compiles:

./configure --with-jpeg-factory --prefix=/opt/ --with-osg=/usr/local

FlightGear is also updated some minutes ago and compiles but does not
link.

./configure --with-osg=/usr/local --with-eventinput --with-logging
--enable-osgviewer --enable-sp-fdms --prefix=/opt/
--datarootdir=/home/quix0r/fgfs/fgfs-base/data/

I use these "special" environment variables:
--
declare -x CC="ccache gcc"
declare -x CXX="ccache g++"
declare -x CXXFLAGS="-g -O0"
--

As I found out with the help from Jester (strace), the linker seems to
take the right lib but cannot link it.

I already tried GCC 4.3.x but doesn't help. :(

Please help me here. :)

Regards,
Roland


signature.asc
Description: This is a digitally signed message part
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] Web Site

[Pete Morgan]

Curtis Olson wrote:
> Hi Pete,
>
> Another option (perhaps my favorite at the moment) would be to pull in 
> CSS and design elements from your google app engine example and roll 
> them into the current flightgear web page design.  We may need to give 
> up on some of the "app" elements or rewrite them in a way that is 
> supported by more typical web hosting services.
>
> Regards,
>
> Curt.

Was thinking the same thing. That way improvement can be done in steps. 
First targets would be
* valid html
* replacing the js menu with css

what do you think ? Is the website in git ?

pete

>
>
> On Tue, Mar 9, 2010 at 4:07 AM, Pete Morgan wrote:
>
> Heiko Schulz wrote:
> >
> > I heard Google will rename our planet soon in GoogleEarth;-)
> >
> > I admit to Curt in a lot of points here. The only advantage is
> there is no advertisement, which makes the current page look
> really bad.
> >
> Adverts can be dropped in where required. However an observation
> here is
> that my 10 year olde nephew downloaded some backup software as
> this was
> a featured advert in the main page above the "downlaod flightgear"
> section.
> > On the other side I like the clear structure of this new
> concept, the NOTAM is a great idea! I like that it makes use of a
> newer and fresh logo as the current one is from the last century.
> >
> One of my dislikes is the dropdown navigation. mainly because its
> javascript and not search engine friendly.
> > Only small things which could maybe improved:
> >
> > -the visual appearence needs still a little "kick"- maybe This
> logo: http://wiki.flightgear.org/images/3/3b/Wiki_logo.png with
> more different aircrafts as the A10 as header bar
> >
> Whilst I like the logo, I dislike it because it contains an efficient
> American Killing Machine and makes FlightGear look like a shoot up.
> > - a simple, good looking button "2.0.0" with a link straight
> link to the Download page
> >
> The home page needs some more thought imho.
> > -I miss the fact that we are OpenSource on the main page. Still
> a lot of people thinks we are commercial and all developers are
> salaried workers for "FlightGear" which leds to confusion
> >
> Its at the top " /The World's Leading Open Source Flight Simulator" -
> but see point above.
> /
> >
> > Is this style and Design of this concept proteced by any
> licence? If not We could just take it over and find a place for
> the advertisement...
> >
> Not at all. I am not a designer, merely a developer. In fact a
> designer
> would be really helpful.. anyone ? Gijs ?
> > Or maybe better: make a package of FGFS with the whole Scenery,
> sell it for less than 30Dollars for those who doesn't want and
> can't to download all stuff. That would probably help against FPS
> and keep the page running without advertisement
> >
> That's why I mentioned a while back making a donation/contribution to
> FG, which I would go towards Infrastructure costs.
>
> pete
> >
> > Cheers
> > Heiko
> >
> >
> >
> > __
> > Do You Yahoo!?
> > Sie sind Spam leid? Yahoo! Mail verfügt über einen
> herausragenden Schutz gegen Massenmails.
> > http://mail.yahoo.com
> >
> >
> 
> --
> > Download Intel® Parallel Studio Eval
> > Try the new software tools for yourself. Speed compiling, find bugs
> > proactively, and fine-tune applications for parallel performance.
> > See why Intel Parallel Studio got high marks during beta.
> > http://p.sf.net/sfu/intel-sw-dev
> > ___
> > Flightgear-devel mailing list
> > Flightgear-devel@lists.sourceforge.net
> 
> > https://lists.sourceforge.net/lists/listinfo/flightgear-devel
> >
>
>
> 
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
>
>
>
> -- 
> Curtis Olson: http://baron.flightgear.org/~curt/ 
> 
>
>
> 
>
> ---

Re: [Flightgear-devel] instrument patches

[syd adams]

Hi James , I have one request (since you have write access) , could you
change that  option to  ?
Dont know if that slang would be clear to everyone , but Im sure everyone
understands "overspeed".
If your planning on further changes , two facts seem to pop up consistently
while researching this :
1: overspeed needle always points to Mmo ... mach limit .
2: when the aircraft reaches that limit .. the overspeed and indicated
airspeed needles should be aligned .

Personally I think K. Hoercher's code worked well, without over-complicating
things , and the default
figures were there in case someone only enabled the  without
options 
260 ias seems to be a pretty common airspeed limit.

Thanks




On Tue, Mar 9, 2010 at 3:19 AM, James Turner  wrote:

>
> On 9 Mar 2010, at 09:18, James Turner wrote:
>
> >> Could someone take a look and commit please ?
> >
> > I'm testing these now, and will commit in a couple of moments.
>
> Committed now, with some changes:
>
>  - I've switched the pressure-alt source to be configurable, instead of
> hard-coded; it defaults to /instruments/altimeter/pressure-alt-ft
>  - the ias and mach limits are read each frame, so they could (potentially)
> be updated from Nasal
>  - I've removed the default values for alt-threshold / ias-limit /
> mach-limit, on the assumption that anyone enabling the barber-pole will
> supply appropriate values. If people disagree with that, adding back the
> B1900 values (or similar) as default is easy.
>
> My biggest concern is that the code references /velocities/mach to compute
> the mach-limit, which seems undesirable - instruments should read/compute
> values based on physical properties if possible - that's certainly the
> philosophy of the basic instruments.
>
> Ideally, we would extend the airspeed indicator to compute Mach as
> described here:
>
>http://williams.best.vwh.net/avform.htm#Mach
>
> I know OAT is available trivially, which lets us compute CS (speed of
> sound) easily, but computing TAS from IAS is more complex, as the formulae
> show. If someone can explain the formuale in detail to me, I'd be happy to
> add a 'indicated-mach' property to the airspeed indicator code (effectively
> allowing it to be used as a mach-meter too), and then use that mach value
> for the mach-limit computation.
>
> Comments? I guess all the formulae required already exist elsewhere in the
> code.
>
> Regards,
> James
>
>
>
> --
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> ___
> Flightgear-devel mailing list
> Flightgear-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/flightgear-devel
>
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] instrument patches

[syd adams]

P.S.

- the ias and mach limits are read each frame, so they could (potentially)
be updated from Nasal

dont know if I like this idea , the intent was to install a specific
instrument at startup ...
 oh well :)

Cheers
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] Mpserver 05 Move

[Brant Gipson]

My VPS migrated to a new datacenter with new IP's

Unfortunately, this breaks the incoming relays. Please restart your MPserver
to fix the relays.

ALL mpservers MUST restart to relay to the new IP address.

-- 
Brant Gipson
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

[Flightgear-devel] [PATCH] jsclient and jsserver 64 bit support and 6 axes

[Pete Morgan]

bug #100 recently submitted is a fix for 64bit system.

http://code.google.com/p/flightgear-bugs/issues/detail?id=100

pete

--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel

Re: [Flightgear-devel] instrument patches

[adams . syd]

Hi James ,
Ive had a better look at the changes you made to my patch ... could you  
please change them back ?
I'd prefer the option of setting these in the instrumentation.xml file ,  
and for safety sake , add the default settings back.
I appreciate your time on this , but consider the time i spent on it as  
valuable... and i feel any modifications should be

discussed first and not done behind the scenes .
Thanks,
Syd
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev___
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel