20,741
edits
FGPythonSys: Difference between revisions
Jump to navigation
Jump to search
→Python Federates
| Line 471: | Line 471: | ||
== Python Federates == | == Python Federates == | ||
{{FGCquote | {{FGCquote | ||
|1= even if Python isn't integrated with the FG core, there is plenty of opportunitie to use it within a FG-based simulation. | |1= even if Python isn't integrated with the FG core, there is plenty of opportunitie to use it within a FG-based simulation. | ||
| Line 480: | Line 481: | ||
| date = Jan 26th, 2016 | | date = Jan 26th, 2016 | ||
| added = Jan 26th, 2016 | | added = Jan 26th, 2016 | ||
| script_version = 0.23 | |||
}} | |||
}} | |||
=== Weather Simulation === | |||
{{FGCquote | |||
|1= The weather module. That needs to provide wind and atmosphereic parameters for all simulation entities. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/27704016/ | |||
| title = <nowiki>Re: [Flightgear-devel] FlightGear Manager...</nowiki> | |||
| author = <nowiki>Mathias Fröhlich</nowiki> | |||
| date = Jun 25th, 2011 | |||
| added = Jun 25th, 2011 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= A weather module running in a different process/thread/machine that computes positions for clouds that are consistenly displayed on each attached viewer. That being a module that is exchangable. The simple version just interploates metars like today, but more sphisticated versions might do a local weather simulation to get good results for thermals in some small area. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/29431494/ | |||
| title = <nowiki>Re: [Flightgear-devel] Slow frame rates</nowiki> | |||
| author = <nowiki>Mathias Fröhlich</nowiki> | |||
| date = Jun 20th, 2012 | |||
| added = Jun 20th, 2012 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= In the future, I hope to have a completely independent weather module using the HLA stuff that runs in an own process/thread. So, at that time you might be able to do more sophisticated stuff. May be it will then be possible to do a full cfd for subparts of the scene. That might be a good thing for a glider scene where you might want to have a more detailed fluid behaviour ... | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/27886790/ | |||
| title = <nowiki>Re: [Flightgear-devel] Future Weather System</nowiki> | |||
| author = <nowiki>Mathias Fröhlich</nowiki> | |||
| date = Aug 2nd, 2011 | |||
| added = Aug 2nd, 2011 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I hope we get Mathias' HLA interface productive soon, so we can add a detailed weather simulation outside the main loop... | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=144989#p144989 | |||
| title = <nowiki>Re: NOAA GFS </nowiki> | |||
| author = <nowiki>Torsten</nowiki> | |||
| date = Dec 16th, 2011 | |||
| added = Dec 16th, 2011 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= A shared Weather federate publishing both the environment for individual aircraft within the simulation, but also cloud positions so all aircraft had a consistent weather environment. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34795859/ | |||
| title = <nowiki>Re: [Flightgear-devel] Designing a thread-safe property tree API | |||
(was Re: A FGPythonSys implementation: ...)</nowiki> | |||
| author = <nowiki>Stuart Buchanan</nowiki> | |||
| date = Jan 26th, 2016 | |||
| added = Jan 26th, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= I'm hopeful that the work I'm doing on HLA will allow us to run Nasal in a separate thread from the FDM and display, so Nasal GC no-longer can impact frame-rates. It would also allow for writing a weather simulation completely external to the FlightGear instance, which could be quite neat. | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=265721#p265721 | |||
| title = <nowiki>Re: the real cost of the Nasal Garbage Collector</nowiki> | |||
| author = <nowiki>stuart</nowiki> | |||
| date = Nov 24th, 2015 | |||
| added = Nov 24th, 2015 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= HLA being that different tasks are run by separate programs which all talk to a central controller unit... that will make the GUI interface (not the menu as some are want to call it) rendering one separate module while all the other stuff like AI craft and weather and such are in other modules which all talk to a central module... think of it like a central server with various clients getting and giving information while the GUI interface simply renders what it is told is available to render... | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=271072#p271072 | |||
| title = <nowiki>Re: 3.7 no smoke</nowiki> | |||
| author = <nowiki>wkitty42</nowiki> | |||
| date = Jan 2nd, 2016 | |||
| added = Jan 2nd, 2016 | |||
| script_version = 0.23 | |||
}} | |||
}} | |||
{{FGCquote | |||
|1= Some of the stuff that I miss in nasal and i can easy do in python is adding an WebSocket client for example to connect to blitortung for real time lighting data. | |||
Or parsing Global Forecast System data for more realistic weather simulator using pygrib. ([https://github.com/jswhit/pygrib https://github.com/jswhit/pygrib]) | |||
|2= {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=270375#p270375 | |||
| title = <nowiki>Re: FGPython an propose for </nowiki> | |||
| author = <nowiki>www2</nowiki> | |||
| date = Dec 28th, 2015 | |||
| added = Dec 28th, 2015 | |||
| script_version = 0.23 | | script_version = 0.23 | ||
}} | }} | ||
}} | }} | ||