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

TerraGear Stabilization

From FlightGear wiki
Jump to: navigation, search
This Page is a draft.

TerraGear Stabilization / This page is actively being written


Terragear Stabilization
Started in 2019-Jan
Description Stabilize the TerraGear tools
Maintainer(s) Scott Giese
Contributor(s)

Scott Giese (xDraconian)

Torsten Dreyer
Status Under active development

Overview

This page defines the goals and provides a status on stabilization efforts related to a working set of TerraGear tools.

TerraGear is a set of programs utilized in generating the worldwide scenery for Flightgear.


Goals

  • Release a new version of worldwide scenery during 2019
  • Make TerraGear accessible to people interested in contributing to scenery development
    • Docker Image to enable cross-platform support for running TerraGear Done Done
    • Legacy Shapefiles via FGBlenderTools Done Done
    • Master data via a Web interface Pending Pending
  • Utilize Oahu as the working data set for assessing the stability of TerraGear programs


Status

Primary Tools

hgtchop: Done Done 100}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Done Done
  • Performance: (0.75 second) Done Done


terrafit: Done Done 100}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Done Done
  • Performance: (5.00 seconds) Done Done


genapts850: Done Done 100}% completed

  • Memory Leaks: (1,419,778 bytes in 6,419 blocks)
  • Memory Leaks: (813,948 bytes in 4 blocks)
  • Memory Leaks: (813,604 bytes in 2 blocks)
  • Memory Leaks: (0 bytes in 0 blocks) Done Done
  • Performance: (24.01 seconds - Avg: 3.43 seconds) Done Done


ogr-decode: Pending Pending 90}% completed

  • Memory Leaks: (529,442 bytes in 5,751 blocks)
  • Memory Leaks: 0 bytes in 0 blocks Done Done
  • Still Reachable: 32 bytes in 1 blocks Pending Pending
  • Performance: (7.43 seconds - Avg: 0.30 seconds) Done Done


tg-construct: Done Done 100}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Done Done
  • Performance: (165.01 seconds - Avg: 2.95 seconds) Done Done


Secondary Tools

dtedchop: Pending Pending 0}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Pending Pending
  • Performance: (0.00 seconds) Pending Pending


gdalchop: Pending Pending 0}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Pending Pending
  • Performance: (0.00 seconds) Pending Pending


srtmchop: Pending Pending 0}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Pending Pending
  • Performance: (0.00 seconds) Pending Pending


cliff-decode: Pending Pending 0}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Pending Pending
  • Performance: (0.00 seconds) Pending Pending


fillvoids: Pending Pending 0}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Pending Pending
  • Performance: (0.00 seconds) Pending Pending


poly2ogr: Pending Pending 0}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Pending Pending
  • Performance: (0.00 seconds) Pending Pending


rectify_height: Pending Pending 0}% completed

  • Memory Leaks: (0 bytes in 0 blocks) Pending Pending
  • Performance: (0.00 seconds) Pending Pending


Known Issues: Memory Leaks

ogr-decode

HEAP SUMMARY:
    in use at exit: 32 bytes in 1 blocks
  total heap usage: 1,086,249 allocs, 1,086,248 frees, 303,320,257 bytes allocated

LEAK SUMMARY:
   definitely lost: 0 bytes in 0 blocks
   indirectly lost: 0 bytes in 0 blocks
     possibly lost: 0 bytes in 0 blocks
   still reachable: 32 bytes in 1 blocks
        suppressed: 0 bytes in 0 blocks