Common Image Generator Interface Study Group CIGI SG

1
Common Image Generator InterfaceStudy
Group(CIGI SG)

• SISO Spring 2005 SIW
• - 7 April 2005 -

2
Study Group Agenda

• Call to Order
• Introductions
• Discussion of Election of AC officers
• Reading of previous meeting minutes
• Action item review
• Discussion of CIGI maturation goals
• Discussion of CIGI Compliance
• Set up next meeting
• Problem/Change Request Review
• Adjourn

3
Goals and Objectives

• CIGI SG
• Purpose
• The goal of the Common Image Generator Interface
  Study Group (CIGI SG) is to serve as an oversight
  organization to guide the maturation of the CIGI
  Open Source product to the point where CIGI can
  be proposed as an industry standard. This group
  will administer changes to the CIGI Interface
  Control Document (ICD), coordinate Open Source
  code development, and guide CIGI functionality
  growth.

4
CIGI SG Officers

• Discussion of election of officers
• Use SISO processes and procedures.
• Within a study group - you manage your own
  elections for whatever positions you feel you
  need.
• Whos willing to serve?

5
Reading of the Minutes

• Action item review
• Lance Durham took an action item to investigate
  and write up a Problem Change Request to
  investigate the implementation of providing HAT
  or HOT data every computational frame without
  actually making a request through the interface.
• PCR 1 to be reviewed at this meeting
• Greg Basler will create a Problem Change Request
  to investigate a better implementation for the
  Trajectory Definition data packet.
• PCR 2 to be reviewed at this meeting
• Lance Durham took the action to formulate a CIGI
  extensions document to contain commonly needed
  extensions.
• The extensions document has been formatted and is
  awaiting input

6
CIGI Maturation

• Discussion of CIGI maturation
• Definition of maturity is in the SISO Balloted
  Products Development Process, Para 4.1.3
• Completed balloted products must be able to
  demonstrate
• Generality, stability, and supportability.  The
  issue of maturity focuses more on the stability
  of the product proposal and involves
  demonstrating the viability and utility of the
  product.
• How near to agreement is the community?
• How hard it is to conduct authoritative
  experiments?
• How hard people work on it?

7
CIGI Maturation

• Discussion of CIGI maturation (continued)
• Issues relating to CIGI
• Broad support from Government, Integrators and IG
  Developers
• CIGI was mature for Air but minimal for ground
  and sea
• If there is broad support for CIGI now, we could
  consider proceeding to a standard that supports
  Air only and having the SG continue with ground
  and sea

8
Compliance

• Discussion of CIGI Compliance
• What does it mean to be CIGI compliant?
• A CIGI implementer shall, as much as possible,
  implement all features necessary for a particular
  application using standard CIGI packets
  (retaining intended use as described in the ICD).
  If further functionality is required by the
  application the interface may be supplemented
  through the use of user-defined packets.
• Who should be the gate keeper?
• What test methodologies should be employed?
• Develop test cases
• Perhaps begin with CIGI HE test scripts

9
Break

• Set next meeting

Back in 30 minutes
10
PCR Review

• Problem/Change Request Review
• PCR 1 HAT/HOT responses without host request
• PCR 2 Trajectory packet implementation

11
Boeing Contact Information

• Bill Phelps
• 314-232-8888
• Willard.b.phelps_at_boeing.com

• Lance Durham
• 314- 234- 1583
• Lance.w.durham_at_boeing.com

• Andrew Sampson
• 314-234-8680
• Rob.lechner_at_boeing.com

• Greg Basler
• 314-233-0419
• Gregory.a.basler_at_boeing.com

• Jim Durtschy
• 314-233-9866
• James.h.durtschy_at_boeing.com