ERC Enhancements

1
ERC Enhancements OneSAF Users Conference April
2008
2
Acronyms and Definitions

• OTF (Objective Terrain Format) Stores the
  terrain and feature data for OneSAF.
• - OneSAF 1.0 and 1.1 use OTF 5.0
• - OneSAF 1.5 and 2.0 use OTF 6.0
• - OneSAF 2.5 and 3.0 will use OTF 7.0
• ITIN (Integrated Triangular Irregular Network)
  Triangle mesh used to represent the terrain data
  in the OTF.
• UHRB (Ultra High Resolution Building) Buildings
  with doors, windows, and interiors.
• ACQUIRE Sensing model implemented by OneSAF.
• SSE, SSE2, SSE3 Specialized CPU instructions
  for improving performance.
• Repoly Process of updating the ITIN with new
  triangles that represent dynamic features.

3
OneSAF 1.0 to 2.0 Enhancements

• OTF 6.0 Format
• SWA Terrain Database
• Performance Improvements
• OTF API Enhancements

4
OTF 6.0 Format

• Reduction in OTF Size (RAM and On Disk)
• JRTC 35
• NTC 37
• Fort Hood 47
• Feature Templates in the OTF 6.0
• Stores unique attribute combinations for
  features.
• Reduces OTF size.

5
OTF 6.0 Format Feature Templates

• Assuming all other attributes are the same, the
• following 3 buildings would produce 2 unique
• feature templates
• Building 1 Height 10 meters
• Building 2 Height 20 meters
• Building 3 Height 10 meters

6
OTF 6.0 Format

• 3. Steep Slopes in the OTF 6.0
• Stores polygons around areas in the terrain
  database that are steep.
• Can be used by Models to determine where no go
  areas are.
• 4. Bridge Model Support in OTF 6.0
• Stores a 3D bridge model for each bridge in a
  database.
• Simple model is auto generated if need be.

7
SWA Terrain Database

• Contains 9 GeoTiles (1 high resolution Baghdad
  GeoTile and 8 medium resolution GeoTiles from
  WARSIM). WARSIM GeoTiles were built using DTED1
  (100 meter spacing) and VMAP1 (1250k).
• Baghdad GeoTile contains
• 2.2 million ITIN triangles
• Built from 112.5k map scale data
• 30,351 Buildings (8 km x 6 km)
• 65,250 Roads
• 250 UHRBs (single and multi-storied)
• 2 UHRB Tunnels
• 3. 592 MBs for 9 GeoTiles

8
SWA Buildings
UHRB showing interior representation (more
detail next slide)
Brown blobs buildings
Brown blobs black outline UHRBs
Dark lines roads
9
Label identifies which floor or level is being
shown
UHRB Key Green door White window Black wall
10
2.0 Performance Improvements

• 32,000 entities in a scenario.
• OneSAF 1.0 supported 6,000.
• Required overall system performance increase
  of 80.
• Performance was improved for the following ERC
  interfaces called by ACQUIRE
• LOS (255 micro to 23 micro on 32 bit 3.4 Ghz
  CPU)
• Transmittance
• Inherent Contrast
• Illumination

11
2.0 PerformanceImprovements

• 3. Performance was improved for the following ERC
  interfaces called by the OneSAF mobility models
• EarthSkinState
• PolyGroundRoute
• PolyAirRoute
• Performance was improved for the following ERC
  interfaces called by the OneSAF LR and MR
  drivers
• SegmentIntersectsBuilding
• FeatureMap

12
2.0 Performance Improvements

• Linux 64-bit Support
• Improves performance (CPU, File I/O, etc.)
• Removes 2 GB address space limit
• Used mostly for SimCores
• 6. Better Threading Support
• Moved thread locks down to the terrain cache.
• Supports multiple threads calling into ERC
  software at the same time.
• Better performance on computers with multiple
  CPU cores

13
OTF API Enhancements

• Improved Performance for 32-bit Linux and 32-bit
  Windows
• 3 to 4 times faster
• 2 Build more dense terrain databases
• Added ability to cache terrain data that is
  passed to OTF API
• Built OTFs with 15 million ITIN triangles in
  1 GeoTile. Have not reached limit.
• Built OTFs with 3 million features in 1
  GeoTile
• Uses much less RAM (approximately 300 MBs)

14
OneSAF 2.0 to 3.0 Enhancements

• OTF 7.0 Format
• Performance
• Robotics Urban Terrain Database
• OTF API
• Dynamic Terrain Server
• SE CORE Merge

15
OTF 7.0 Format

• Improved spatial organization of feature data
• Improves performance
• Needed to support more dense urban terrain
  databases
• Needed to support SE CORE terrain databases
  with 14 million trees
• Better paging support for road networks
• Needed for road route planning in dense urban
  areas

16
OTF 7.0 Format

• Local coordinate system for pages
• Shrinks OTF size
• Improves performance because of less caching
• Better supports hardware acceleration (SSE,
  SSE2, SSE3, etc.)
• 4. CCTT style tunnels
• Tunnel model with 3D geometry
• Lower resolution than UHRB tunnels
• Needed by SE CORE to support CCTT terrain
  databases

17
UHRB 2.2 Format

• Changed 3D locations in UHRB templates from
  64-bit floats to 32-bit floats
• Shrinks OTF size
• Improves performance because of less caching
• Can put more UHRBs in an OTF before 32-bit
  address space limit is reached (UHRBs are memory
  mapped)
• Better supports hardware acceleration (SSE,
  SSE2, SSE3, etc.)
• Global coordinates in UHRB features are still
  using 64-bit floats

18
3.0 PerformanceImprovements

• LOS
• 50 for OneSAF use case (SWA, JRTC, NTC, etc.)
• Match CCTT LOS performance (14 million trees)
• Network route planning
• Interfaces heavily used in dense urban terrain
  databases
• Interfaces called by ACQUIRE, OneSAF mobility
  models, and OneSAF drivers

19
Robotics Terrain Database

• Baghdad geo-typical database
• Will be used to train operators using robots to
  remove IEDs
• One GeoTile with high resolution inset.
• Inset is approximately 3 km by 3km of dense urban
  data
• Urban clutter
• Trash cans
• Rubble
• Barricades
• Street signs
• 6. Curbs

20
OTF API Enhancements

• Support for building terrain databases with
  millions of trees.
• Tested with 16 million trees. Will do more.
• 64-bit Linux support
• Improves performance (CPU and File I/O)
• Removes 2 GB address limit
• 64-bit File I/O Support for 32-bit Linux and
  32-bit Windows
• Supports individual OTF files that get larger
  than 2 GBs
• Needed to build more dense terrain databases

21
Dynamic Terrain Server

• Supports repoly of ITIN. Examples of features
  that are supported by default
• Craters
• Tank defilades
• Infantry trenches with berms
• 2. Provides framework that allows you to compose
  a composition that uses your custom repoly
  software
• 3. Improves performance of ERC interfaces
• 4. Supports checkpoint, restore, and late join

22
SE CORE Merge

• SE CORE has modified ERC for integration into
  CCTT and AVCATT
• Enhancements (collision detection, better
  bridge support, steep slopes, etc.)
• CCTT and AVCATT terrain databases converted to
  OTF
• Performance improvements
• PTR fixes
• Improvements to the OTF API by DVED