Version 3.0 Bill Phelps The Boeing Company - Training Systems and Services -IMAGE- -July Bill Phelps The Boeing Company - Training Systems and Services -IMAGE- -July 2003-

2 Order of Presentation Introduction CIGI 3.0 Highlights CIGI 3.0 Considerations CIGI 2 to CIGI 3 Enhancements Current Issues Future Plans Summary

3 What Is CIGI? Communication protocol for host-to-image generator interface control definition. Provides a high level of abstraction, simple to use. Plug-and-play type interface. API provided to remove error-prone data packaging. Released open-source, non-proprietary under a GNU Lesser General Public License. Host Simulation CIGI SDK CIGI API CIGI IG Run-Time CIGI SDK CIGI API CIGI CIGI Messages Data & Synchronization

4 Availability All data and documentation are available on –includes ICD, API, SDK, CIGI Host Emulator –on-line forum for help, bug tracking, and distribution list ICD contains complete definition of all data packets ANSI C design tested on W2K, Linux, IRIX, VxWorks, and Solaris. CIGI Host Emulator test tool with scripting interface available.

5 CIGI 3.0 Highlights Improved documentation –More detail on coordinate systems and special effects –Database load sequencing –Orthographic projection General improvements –Changing fixed-point numbers to floating point IG Control –Interface support for byte-ordering –Improved support for asynchronous operation Entity Controls –Clarified entity animation controls –Added animation loop flag –Added inherit opacity flag –Added entity ground clamp support Component Controls –User defined data formats

6 CIGI 3.0 Highlights Separated and classified simulated environment controls –Celestial Sphere Controls (sky model) –Date/time valid flags in Celestial Packet –Atmospheric Control (global controls) –Regional weather definition –Weather Layer Control Increased view count Added multiple motion tracker support Added Earth Reference Model (ERM) definition Added light point definition Collision volume rotation h w p θ r (lat, lon) Y X

7 CIGI 3.0 Highlights HAT/HOT/LOS –Added polygon normal response Sensors –Sensor control –Sensor gate position response –Sensor track point and gate position response Added ability to query IG for positional information Added weather condition request Animation complete notification

8 CIGI 3.0 Considerations Entity definition packet – Is it needed, how to implement Volumetric primitive control – awaiting input from 3DPipeline Skinned object control – awaiting input from 3DPipeline Sensor multi-target tracks – advanced sensor targeting Surface conditions control – need user input to define parameters Sub-surface conditions control – need user input to define parameters

9 CIGI 2 to CIGI 3 Enhancements

10 IG Control Interface support for byte ordering. Added “Magic Number” field so IG can determine whether byte swapping is necessary Improved support for asynchronous operation –Changed single-precision floating point time tag to 32-bit integer –Changed time tag units from 1-µs to 10-µs to provide a simulation time of almost 24 hours before a rollover occurs

11 Entity Control Functional change to entity animation controls –Stop –Play –Pause –Continue Added animation loop flag Inherit opacity flag Ground clamp flag –Altitude –Altitude with Pitch and Roll

12 Component Control One 8-bit discrete component state Three 32-bit user-defined data fields

13 Celestial Sphere Control Moved date/time to this packet –Better applicability to ephemeris model Added Starfield intensity

14 Atmosphere Control Global atmosphere control Atmospherics model enable

15 Layered Weather Control Changed Weather Control packet to Layered Weather Control packet. –applicable to both global and regional weather –Added nine clouds types

16 Motion Tracker Control Enable/Disable Device Multiple Trackers Boresight View/View Group assignment

17 Earth Reference Model Definition Default ERM is WGS 84 New ERM defined by specifying Equatorial Radius and Flattening Point P Semi Minor Axis Prime Meridian Equator Radius Pole

18 Light Point Definition State (On/Off) Type (Raster, Calligraphic) Visibility (Day, Dusk, Night) Front/Back Color Front/Back Intensity Min/Max/Actual Size Animation Properties (flash, rotation, etc.) Directionality (Omni-/Uni-/Bi-directional) Lobe Angle, Intensity, Falloff Fog Punch-Through Enable Fading Enable Range Mode (Z-Depth/Slant Range)

19 Transition Perimeter Regional Weather Definition Weather region defined within a rounded rectangle –Weather region in an infinite column –Weather region volume is defined by the intersection of the column and the layered weather –Multiple weather regions –Transition perimeter for smooth transition between regions –Multiple weather layers defined within a region h w p θ r (lat, lon) Y X w = width h = height r = corner radius p = transition perimeter width θ = rotation Infinite column Regional volume Layer definition Column definition

20 Position Request Specify class of object –Entity –Articulated Part –View –View Group –Motion Tracking Device Specify coordinate system –World (Geodetic) –Entity Local NED –Submodel

21 Weather Condition Request Allows host to request current weather parameters because IG will have control of weather conditions when Ownship is location within regional weather transition perimeter. Weather region 1 Weather region 2

22 Start of Frame Added “Magic Number” so Host can determine whether byte swapping is necessary Flag indicates whether WGS 84 or other ERM is being used Improved support for asynchronous operation –Changed single-precision floating point time tag to 32-bit integer –Changed time tag units from 1-µs to 10-µs to provide a simulation time of almost 24 hours before a rollover occurs

23 HAT/HOT Response Two Packets: –Basic Height –Extended Height Material Code Normal Vector Azimuth and Elevation

24 LOS Response Two Packets: –Basic Altitude Latitude Longitude –Extended Altitude, Latitude Longitude Material Code Azimuth Elevation

25 Collision Detection Segment Response Intersection point defined as distance from an endpoint along the test vector

26 Sensor Response Two Packets: –Sensor Gate Position Response Target Offset X, Y Gate Size X, Y Frame counter –Sensor Track Point and Gate Position Response Target Offset X, Y Gate Size X, Y Frame counter Target point Latitude, Longitude, Altitude

27 Animation Stop Notification Entity ID –Notifies the host when an animation sequence has completed so that the next action can be commanded

28 Position Response Lat., Long., Alt., X, Y, Z, Yaw, Pitch, Roll Coordinate System specified by request packet –World (Geodetic) –Entity Local NED –Submodel

29 Current Issues Entity definition: How to specify entity scale, color, and other properties Animation definition: How to define animation properties Surface/subsurface control: How to define environmental properties

30 Entity Definition Two methods: –Entity Definition Packet Scale Color Other properties –Component Controls

31 Animation Definition Possible methods for defining attributes: –Component Control for all animation properties –Single Animation Definition packet –Specialized Animation Definition packets Frame-based animations (dynamic textures, switched geometry) Scripted articulations Smoke Trails and wakes Particle systems Many others

32 Single Animation Definition Packet Pros –Similar to CIGI 1 and 2 (Special Effect Definition) –Promotes standardization of interface Cons –Many attributes in interface do not apply to a given phenomenon –Must change all attributes if we change any –Increased packet size –Cannot foresee all needed attributes

33 Specialized Animation Definition Packets Pros –Promotes standardization of interface –Attributes all apply to the animation type Cons –Forces implementation of a particular phenomenon (e.g., frame-based smoke vs. particle system smoke) –Must change all attributes if we change any –Increases complexity of the interface (more packets) –Cannot foresee all types and attributes

34 Surface / Subsurface Control Packets Surface –Wave states, direction –Surface trafficability –Surface contaminates, i.e. ice, snow, slush, water, other debris –Dynamic terrain control, bomb craters, trenches Subsurface –Under water –Subterranean

35 Future Plans Active News page on –Review for news/forums/updates –We need users to subscribe to the update mailing list so we can get feedback Boeing would like to host a CIGI Working Group –Would like to know who would be interested? –Where to hold meeting –We need multiple inputs on current and future designs –And a voting body on some designs Presented at SISO SIW (March 2003) –Standards Study Group being formed CIGI 3.0 ICD to be released Q303 –API will follow suite –Host Emulator will be released Q403

36 Summary CIGI is designed to assist suppliers and integrators of IG systems with ease of integration, code reuse, and cost reduction. CIGI has become an accepted IG interface. Boeing will continue to support CIGI, but we desire to move CIGI to a standards organization or form a consortium with a review board. We desire assistance to foster future development and advancement. All inputs, contributions, and ideas are welcome!