New Features for OASES: The Query Server

1
New Features for OASESThe Query Server

• Robert Reynolds
• Northrop Grumman Information Technology
• Christopher Scannell
• Naval Research Laboratory

04F-SIW-088
2
The Query Server What It Is

• New OASES Federate
• Uses HLA Interactions to define
• Hierarchy of Query classes supporting
• Point queries request AOS state at a specified
  location
• Line queries request AOS state values along
  line-of-sight (LOS)
• Integrated-Line queries request line-integral
  of AOS state on LOS
• Parallel hierarchy of Response classes
• Provides services complementary to Publisher

OASES DB
3
Comparing Query Server with Publisher
4
Query Server Design

• Focused on the interface between the Query Server
  and a client Federate, as described by Query
  Server Simulation Object Model (SOM)
• First consideration
• What should be requestable?
• Conclusion four types of requestable data
• Point observations (of volumetric attributes)
• Line-of-sight observations
• Near-surface observations (of surface
  attributes)
• Vertical profile observations
• Second consideration
• How does one make a request?

5
Response Hierarchy
6
Response Parameter Table Example
7
Query Interaction Hierarchy
8
Query Parameter Table Example
9
SOM Agility and the MetaSOM

• SOM was reviewed with User Group and approved
• Implementation was begun
• Initial implementation efforts revealed that
  Query hierarchy can be derived from the Response
  hierarchy
• Requires augmenting Response hierarchy with
• Per-class concrete vs abstract qualifier
• Geometry-type
• o        Point-in-Volume
• o        Point-on-Surface
• o        Line-of-Sight
• o        Vertical Profile
• Supported coordinate systems for queries

10
MetaSOM Structure
(class EnvironmentObservation best_effort
receive (type abstract) (parameter
RequestingEntity) (class AtmosphereObservation
best_effort receive (type abstract)
(class AtmospherePointObservation best_effort
receive (type concrete)
(parameter EAC_Air_Temperature)
(parameter EAC_Relative_Humidity)
(parameter EAC_Wind_Speed_U_Component)
(parameter EAC_Wind_Speed_V_Component)
(parameter EAC_Obscurant_Type)
(parameter EAC_Aerosol_Particle_Concentration)
(geometry point-in-volume)
(coordsystem GDC) (coordsystem GCC)
)

11
(class AtmosphereLOSObservation best_effort
receive (type concrete)
(parameter Extinction_Coefficient_Visible)
(parameter Extinction_Coefficient_Near_IR)
(parameter Extinction_Coefficient_Mid_IR)
(parameter Extinction_Coefficient_Far_IR)
(parameter EAC_Obscurant_Type)
(parameter EAC_Aerosol_Particle_Concentration)
(parameter EAC_Cloud_Water_Mixi
ng_Ratio) (parameter EAC_Cloud_Liquid_Wat
er_Content) (parameter
EAC_Cloud_Drop_Mean_Diameter) (parameter
Total_Extinction_Visible) (parameter
Total_Extinction_Near_IR) (parameter
Total_Extinction_Mid_IR) (parameter
Total_Extinction_Far_IR) (parameter
Resolution) (geometry line-of-sight)
(coordsystem GDC) (coordsystem
GCC) )
12
In Conclusion

• Query Servers SOM is, to a degree, agile
• Using a documented syntax, user creates a
  MetaSOM (ascii text file, ala .fed)
• User-defined state variable sets for Responses
• User-selected query geometry and coordinate
  systems
• OASES utility generates .fed file from MetaSOM
• With derived Query classes
• Query Server to be included in OASES V2.1.1