Hi fellow wiki editors!

To help newly registered users get more familiar with the wiki (and maybe older users too) there is now a {{Welcome to the wiki}} template. Have a look at it and feel free to add it to new users discussion pages (and perhaps your own).

I have tried to keep the template short, but meaningful. /Johan G

FlightGear Headless

From FlightGear wiki
Revision as of 18:00, 17 November 2015 by Hooray (Talk | contribs) (Status (07/2014): http://forum.flightgear.org/viewtopic.php?f=6&t=28020&start=15#p264824)

Jump to: navigation, search
This article describes content/features that may not yet be available in the latest stable version of FlightGear (2018.3).
You may need to install some extra components, use the latest development (Git) version or even rebuild FlightGear from source, possibly from a custom topic branch using special build settings: .

This feature is scheduled for FlightGear 4.x. 30}% completed

If you'd like to learn more about getting your own ideas into FlightGear, check out Implementing new features for FlightGear.

FlightGear Headless

Screen shot showing a the performance monitor in a patched version of FlightGear 3.2 where subsystem initialization is made better configurable and increasingly optional by allowing subsystems to be explicitly disabled/enabled during startup. Decoupling internal subsystem dependencies means that we can more easily provide support for benchmarking, but also headless regression testing - and eventually, also a standalone FGCanvas startup mode.
Note  Also see Testing
Cquote1.png If we want to remove an subsystem from the flight gear source code, without leaving any trace of it.. What are the essential steps ?(for example, if the sound update has to be removed, what are steps to be followed).
Cquote2.png
Cquote1.png the route manager has a fairly nasty bug that results in memory consumption increasing throughout a flight. The rate at which it increases appears to increase with the number of waypoints, with a flight of 20 waypoints experiencing an increase of over 2GB per hour in my tests. The longer the flight, the more waypoints it tends to have and the more unsustainable the growth becomes.
— Richard Senior (2015-02-25 22:00:53). Memory leak most likely from route manager in 3.4.0 and next.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png I am wishing I could easily add tests for the route-path / GPS code, but anything that needs ‘globals’ is hard to test in isolation.
Cquote2.png
Cquote1.png I appreciate that would require us to have a unit-testing infrastructure, and way to bring up a subset of globals and the nav-cache, in a test environment. I have made a few abortive attempts at exactly that but the sprawling nature of FGGlobals keeps defeating me.


(The ability to run many tests efficiently was actually one of the smaller reasons for introducing the nav-cache, since without it any automated testing system would be horribly slow)


Cquote2.png


Cquote1.png The primary goals are:
  • make startup more predictable and less hard-coded.
  • allow running flightgear in a server/test mode with only some subsystems, and no rendering

Obviously supporting a standalone 'fgcanvas' would be quite a small extension from those. I'm not worrying about dynamic dependencies or automatic subsystem creation for the moment - I expect the user / defaults to have defined a set of subsystems that work without crashing You're correct of course that Nasal has many assumptions about subsystems, but I think that can be improved incrementally on the Nasal side.

For the test mode, I really want to start Nasal-the-langauge very early, without loading all the modules in Nasal/ immediately. (Or maybe load a 'safe' subset). That's going to take some thought and I didn't get that far yet![1]
— James Turner
Cquote2.png


Cquote1.png I'm working on a prototype of this - with no X11 / VLC required at all. It will load scenery tiles (for ground-intersections) but no views or rendering. But don't be in a rush for something to appear in Git, it's just an experiment.[2]
— James Turner
Cquote2.png
Cquote1.png A "headless" mode is a long-standing feature request, especially requested by developers and contributors who are hoping to do better/automated regression testing (valgrind, gdb, gprof). At the moment, it isn't directly possible - not without modifying the C++ source code and and rebuilding FG from source. You would basically have to change our OSG init code such that the window is not visible, note that you would still require OSG and X11 obviously, the window just wouldn't be shown - so that FG could be run from a console/shell
— Hooray (Sun Mar 24). Re: run without osg.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png the main camera is created in CameraGroup::buildCamera and a pbuffer is allocated when you set osg::GraphicContext::Traits.pbuffer to true. These traits are available in buildCamera because we set width and height there. For debugging purpose, you can add a line like
window->gc->getTraits()->pbuffer=true;
at the end of this function.
— FredB (Sun Mar 24). Re: run without osg.
(powered by Instant-Cquotes)
Cquote2.png

Status (07/2014)

Note  As of mid 2014, this is being worked on via Initializing Nasal early, in part, this effort is also overlapping with the Reset & re-init and FlightGear Run Levels efforts.
Cquote1.png I organised Simgear into 'core' and 'scene' libraries; the 'core' part is also what we call 'headless' simgear, i.e can be compiled without requiring OpenSceneGraph or any GUI systems. (Which is how SG is used by terragear and potentially some other users).
— James Turner (Aug 28th, 2012). [Flightgear-devel] SimGear libraries.
(powered by Instant-Cquotes)
Cquote2.png
Cquote1.png I'm writing some automated testing code for pieces of FG, so that I can experiment with changes to various internal bits of code with more confidence that I haven't broken anything. These aren't quite unit-tests (they test multiple areas of the code at once) and they're pretty crude, but any testing is better than none (and quicker than manual testing).[3]
— James Turner
Cquote2.png
Cquote1.png I only need the graphical output for the real aircraft and want to disable the unnecessary graphical outputs (to reduce work load).[4]
— Rahlf, Jonas (ext.)
Cquote2.png
Cquote1.png I'm interested in the capability of doing multiple builds with different versions, branches and options and in doing some kind of automated testing on the resulting builds[5]
— Pat
Cquote2.png
Cquote1.png Make subsystems create-able and removable from commands. Only some subsystems are supported so far, since many have non-default constructors or other complexities.

With this, change, it's possible to dynamically add and remove the traffic-manager at runtime, for example:

fgcommand("add-subsystem", props.Node.new({ "subsystem": "traffic-manager", "name":"traffic-manager", "do-bind-init":1}));
[6]
— James Turner
Cquote2.png
Cquote1.png could some thought be given to producing a benchmark suite for Flightgear. It would need to take in all of the, by now well known, variables - making it by no means a simple beast to manage. If this could be automated in some way it would be much easier to capture, and then submit, consistent data. [7]
— Alan Teeder
Cquote2.png
Cquote1.png A scripted run would be an EXCELLENT tool.[8]
— geneb
Cquote2.png
Cquote1.png Is there a way to do that "headless", without any graphic output? I wasn't being clear - I wanted to run *FlightGear* in a "headless" mode, not the browser.[9]
— geneb
Cquote2.png
Cquote1.png I don't think you can run FlightGear without a window. There used to be some property "draw-otw" that - if set - stops fg from rendering anything to the screen, but it still needs an opengl screen.[10]
— TorstenD
Cquote2.png

Also see, FlightGear Benchmark

  1. James Turner (Oct 01, 2012). incremental initialization of SGSubsystems.
  2. James Turner (Sep 26, 2012). Issues 882 (Improved CI / regression testing support by providing options to disable interactive features (sound/window)).
  3. James Turner (Sun, 24 Aug 2008 13:53:58 -0700). Startup position offsets (fg_init).
  4. Rahlf, Jonas (ext.) (Wed, 31 Jul 2013 04:42:48 -0700). [Flightgear-devel] Disable grahpical output in flightgear / interface flightgear server instead of flightgear.
  5. Pat (Wed, 03 Jul 2013 17:24:19 -0700). Re: [Flightgear-devel] FG 2.12 RC Broken ?.
  6. James Turner (Oct 01, 2012). Initial work on dynamic subsystem creation..
  7. Alan Teeder (Thu, 20 Jun 2013 10:15:42 -0700). [Flightgear-devel] Benchmark matrix.
  8. geneb (Thu, 20 Jun 2013 10:20:41 -0700). Re: [Flightgear-devel] Benchmark matrix.
  9. geneb (2014-04-23 14:22:57). Property documentation....
  10. TorstenD (2014-04-23 14:22:57). Property documentation....

Regression Testing in FlightGear

While introducing unit tests and regression tests into the FlightGear project has been repeatedly brought up by several long-term contributors [1] and core developers [2], it isn't yet in wide or regular use in FlightGear, even though it is generally understood to be a worthwhile addition to FlightGear in order to do automated testing of individual features, for example when preparing releases [3].

And while there are indeed some minor build tests provided by both, the SimGear and FlightGear projects, such test cases aren't really commonly provided our updated by developers when introducing modified or new code. Also, these are just low level tests for specific APIs - and do not lend themselves to be used for testing high level features.

Increasingly, FlightGear users are facing issues that are highly specific to their usage of FlightGear so that it isn't directly or easily possible to reproduce certain issues without exactly reproducing possibly an entire flight including identical startup and runtime settings, a fact that is also frequently acknowledged by FlightGear core developers [4].

This is however not only a tedious and long-winded process, but also a process that may require certain usage patterns and background information or a specific set of skills (such as for example landing a specific aircraft on an aircraft carrier).

In fact, the corresponding bug reports are often fairly long winded and complicated in that they try to provide all information necessary in order to allow developers to redo a certain flight segment that resulted in an error (see for example [5] or [6], [7]).

These obstacles in debugging such highly specific issues are also highlighted by core developers to severely limit the troubleshooting process [8].

For a more recent discussion of regression testing and benchmarking, see FlightGear Benchmark.

Background

FlightGear in its current form is an application that was primarily designed as an interactive graphical simulator, in other words, it is meant to be used by a user sitting in front of one or multiple screens, controlled by means such as a keyboard, mouse and other optional hardware such as joysticks/yokes and possibly also rudder/yaw pedals.

While confining FlightGear's design and use cases to this standard use scenario was of course very valid and feasible (as this is definitely the primary use) this restriction isn't necessarily ideal or even appropriate for the project to eventually be able to leverage itself for increasingly important purposes such as automated unit testing or automated benchmarking of individual FlightGear components in order to do regression testing.

This is an approach that is already used by the jsbsim project to some extent [9].

This RFC is meant to discuss the possible merits and approaches of allowing FlightGear to be used non-interactively, i.e. in an automated fashion such as for example by invoking it via shell scripts, so that FlightGear doesn't necessarily have to rely on user input or even a graphical output window in order to do a certain, well-defined and limited job, such as for example running certain subsystems for benchmarking purposes or by running scripted flights to fly standard patterns in order to generally help test aircraft that are considered for inclusion in upcoming FlightGear releases.

While there are certainly various thinkable scenarios for employing such facilities in other interesting contexts, this RFC will merely focus on the benefits for FlightGear itself.

Introducing Regression Tests to FlightGear

Cquote1.png Unit-testing for the FlightGear classes would be fantastic, but in general the ‘FGGlobals’ structure makes it hard. To unit-test most areas will mean a standard test harness which starts up a skeletal subsystem manager, the NavCache (for some classes, e.g. radio testing), and somehow makes an FGGlobals which works (maybe a mock one) but doesn’t require linking in 80% of the codebase. Any maintainable, not-too-intrusive idea on doing that is welcome!
Cquote2.png
Cquote1.png I've done some initial measurement to identify potential memory leaks in SimGear.

Detection was limited to execution of code covered by unit tests.


— xDraconian (2015-03-24). [Flightgear-devel] SimGear Memory Leaks.
(powered by Instant-Cquotes)
Cquote2.png

The task of introducing regression tests isn't that easily achieved in FlightGear's case:

FlightGear has largely become an independent system and platform, so while it would be fairly straightforward (but still very tedious) to introduce individual unit tests in order to validate the correct behavior of low level C++ components, such as the SimGear APIs, it wouldn't really be that easy to properly test the various abstract, high level features that are provided by FlightGear as a functionality provider and simulation framework/platform with all its various subsystems providing support for abstract features.

In fact, conventional regression tests would inevitably fail when it comes to supporting base package resources, simply because FlightGear is the sole target platform for these resources.

While base package resources do generally make use of well-understood and established technologies or standards (i.e. textures, XML, scripts, 3D models, text files etc), it is only the specific combination of these resources inside FlightGear, that define a real purpose and use.

So, doing proper regression testing for such high level features would be very difficult without writing lots of redundant test code, which would probably end up being a maintenance burden in the long term - probably resulting in a situation similar to the current one, where tests simply end up being neglected and ignored at some point.

Thus, this discussion of bringing regression testing to FlightGear favors an approach where FlightGear itself is used as the regression testing framework.

So this isn't about doing low-level unit testing for individual FlightGear C++ code, but much more abstractly do regression testing by making use of the FlightGear platform to test abstract FlightGear features by making use of FlightGear's native support for technologies such as XML, scripting and networking.

Goals

Leverage FlightGear as its own regression testing framework, for purposes such as for example:

  • debugging (running FlightGear non-interactively, without requiring user input)
  • unit tests (e.g. to facilitate refactoring efforts)
  • automated release preparations (e.g. to test individual subsystems but also complete aircraft, or even flights/flight plans)
  • benchmarking the whole system or individual subsystems 60}% completed
  • feature-scaling by making some subsystems optional or better configurable

Approach

Due to FlightGear's extensive support for flexible software interfaces (such as e.g. networking, scripting and XML), FlightGear can in many scenarios theoretically already be used for serving as its own test platform.

In fact, the major obstacle really limiting FlightGear to be used by automated/scripted tests is its reliance on having a graphical output window available and opened.

If FlightGear provided an option to be run in non-interactive/headless mode, so that it wouldn't necessarily create a visible output window but could just run silently in a shell environment, it could already be easily used by shell scripts to do simple things such as for example profiling the fgfs process while running a specific Nasal script non-interactively and automatically terminating afterwards.

It's worth pointing out that this is indeed already possible: Nasal scripts can terminate the simulator by invoking an fgcommand, so this really isn't that much off the table and would facilitate scenarios where Nasal scripts may run certain test suites and automatically report status back to the caller (shell script). So, this would be just one scenario for running fgfs non-interactively in order to profile the Nasal interpreter. Another possible use might be scripted flights to have aircraft fly standard patterns or instrument approaches, while using a network interface such as the telnet facility to monitor the state of the flight during all phases of the flight.

Also, FlightGear's reliance on user input via means such as the mouse/keyboard and other hardware peripherals doesn't really pose a real problem, because all of these inputs are already internally handled by a combination of XML and scripting, so that emulating arbitrary user input by making use of scripts or by automatically writing to the property tree via network sockets is fairly straightforward and could also be accomplished by running shell scripts, that may for example invoke "netcat" specifically for this purpose.

The recent additions to the Autopilot and Route Manager systems in FlightGear also make it increasingly feasible to create completely scripted test flights for automatically doing certain portions of a flight without relying on user input.

Cquote1.png the most flexible approach would be using scripting - FligthGear has a built-in scripting language (called "Nasal"), that can be used to control aircraft, and even to instantiate multiple AI aircraft, one of the most straightforward examples is the "tanker.nas" script, which creates a fully scripted AI tanker - that could be easily extended to create dozens of tankers, and obviously you could also change the 3D model if you wanted to. In fact, we have a separate addon, named "bombable" that adds "AI bots" to the simulator, for dogfighting purposes - none of that required C++ changes, it's all done in scripting space. Another users implemented a fully scripted missile (fox2.nas) that tracks aircraft
Cquote2.png
Cquote1.png Curt did that a while back for the f14b, which did a fully automated carrier approach using just Nasal scripting:

Cquote2.png

Milestones

  • allow FlightGear to be run without creating a visible GUI window, i.e. in "headless" mode, using a --headless parameter Pending Pending
  • allow FlightGear to be optionally compiled and run without any sound support/dependencies (OpenAL) Done Done
  • allow replay buffers to be saved to a file in order to be replayed for automated test/demo flights, so that users can share saved replay buffers when reporting a bug Done Done (supported via the flight recorder subsystem)
  • allow arbitrary user inputs to be simulated via property tree modifications (pretty much possible already) Done Done
  • allow individual subsystems to be enabled/disabled dynamically (via properties), so that profiling and debugging can be restricted to specific usage scenarios and components 30}% completed
  • extend the Nasal API in order to facilitate "remote controlling" the simulator largely using scripts

Related

Devel List