Fgtape: Difference between revisions

Jump to navigation Jump to search
4,475 bytes added ,  23 September 2015
mNo edit summary
Line 16: Line 16:
== For reproducible bug reports ==
== For reproducible bug reports ==
== For benchmarking ==
== For benchmarking ==
== Regression testing ==
{{FGCquote|1= For starters, you will need a reproducible test case - e.g. a startup profile, or a saved flight (fgtape) and then play with different startup/runtime settings (location/aircraft, enabled/disabled features) to see if/how the bug can be reproduced. |2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=254310#p254310  | title  = <nowiki>Re: 32bit and low memory systems, read this</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Aug 17th, 2015  }}}}
{{FGCquote|1= Once there is a handful of different test cases, those could be used for regression testing purposes - e.g. to compare FG 3.2 RAM/VRAM (memory) occupancy against 3.6 and 3.8. Equally, that would mean, that it would become easier for people to spot serious bugs/regressions, such as an aircraft (or Nasal script) suddenly utiliing much more resources.|2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=255010#p255010  | title  = <nowiki>Re: Looking for people with ATI/AMD GPUs building from sourc</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Aug 25th, 2015  }}}}
{{FGCquote|1= deally, people doing such flights regularly would provide a corresponding "fgtape" file using a standard aircraft and get this committed to $FG_ROOT into some kind of "Tests" directory containing pre-recorded flights for doing regression testing in an automated fashion. The thing to keep in mind here is that those among us able (and willing) to troubleshoot such issues are most unlikely to ever actually use FlightGear like this, which certainly includes Zakalawe. Thorsten recently also mentioned that he'll typically just start up FlightGear a few doen of times using a simple aircraft to test things, without really doing any "real" flying at all. So there are certainly a number  of use-cases that aren't getting much attention unfortunately.Which is why it would be a good idea for  people to provide flight recorder tapes covering use-cases they care about, and get those committed to fgroot (fgdata) - so that we can grow a library of useful flights to do regression testing - as long as those flights are using standard aircraft and features, they should also be useful for people entirely new to FlightGear.While developers, and power users, could use those flights to run FG in an unattended fashion, without having to be overly familiar with aircraft internals (think aircraft startup procedures, IAPs, STARs and other VA stuff) - we could even use accelerated sim-time to complete whole flights in a fraction of the time normally required, while stress-testing a bunch of underlying systems, including the route manager, autopilot, and FDM. Many of those don't necessarily require any "rendering" - which is touching on the whole "headless" effort that James has been working towards independently: [[FlightGear Headless]]|2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=233211#p233211  | title  = <nowiki>Re: 3.4 and the pain begins ...</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Feb 26th, 2015  }}}}
== Pre-release testing ==
{{FGCquote|1= At some point, this could then even be done in an automated fashion on the build server directly - but we '''will''' need people to provide fgtape files covering different use-cases to exercise different code paths, without core developers necessarily having to spend hours doing transcontinental flights in a twin-engine turbprop, you know  xD But I guess that is something that should be better discussed on the devel list, once we have people offering to provide a few pre-recoreded fgtape files to get this started ...|2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=233211#p233211  | title  = <nowiki>Re: 3.4 and the pain begins ...</nowiki>  | author = <nowiki>Hooray</nowiki>  | date  = Feb 26th, 2015  }}}}
== Flight analysis ==
{{FGCquote|1= i would like to use the flight data recorded during the flight in the .fgtape format. However, i don't want to watch the replay but compare the recordednumbers of the replay with i.e. an ideal flight curve. For this reason, i'd like to extract the data from the file to work with it. How can i proceed? Is it already implemented in a way?|2= {{cite web  | url    = http://forum.flightgear.org/viewtopic.php?p=231739#p231739  | title  = <nowiki>Extracting flight data from recorded flights</nowiki>  | author = <nowiki>CasJanM</nowiki>  | date  = Feb 9th, 2015  }}}}

Navigation menu