Skip to end of metadata
Go to start of metadata
This is the main page for the OOI CI Marine Integration efforts.

Team

Name Org Status
Role
Area of Work
Bollenbacher, William
UCSD
active 100% Developer Driver Development / Direct Access
Everett, David UCSD active 100% Developer 
Driver Development / Instrument Development Kit
Foley, Steve UCSD
active 30% Developer Driver Development / Data Products
French, Bill 
UCSD
active 100% Developer
Marine Integration lead 
Manning, Maurice UCSD active, part-time Architect  
Unwin, Roger
UCSD
active 100% Developer
Driver Development / Simulators
Emily Hahn Raytheon BBN active 100% Developer Driver Development
Chris Wingard OSU active 75% Developer Driver Development / Data Curation
Stuart Pearce OSU active 100% Developer Driver Development / Data Curation
Jeffrey Roy Raytheon   Developer Dataset Agent Driver Development
Christopher Goodrich Raytheon   Developer Dataset Agent Driver Development
Nicholas Almonte Raytheon   Developer Dataset Agent Driver Development
Mike Nicoletti Raytheon BBN active 100% Developer Dataset Agent Driver Development
Chris Fortin Raytheon BBN active 50% Developer Dataset Agent Driver Development
Maria Lutz Raytheon BBN active 50% Developer Dataset Agent Driver Development

Weekly MI status meeting notes

Development Pipeline Tracking

  • [Instrument Driver Development]
  • [Data Product Development]
  • [instruments:OL Instrument Development Pipeline Report]

Technical Overview

The Instrument Platform Agent Architecture (IPAA) is the infrastructure entity that is responsible for accessing an instrument (that device that senses and acquires data) or platform (that structure that holds sensors) in the OOI framework. This access may be to control, configure, or collect data from an instrument or platform. The agents that are part of IPAA are Taskable Resource Agents as they front a system resource (instrument or platform) and can be asked to perform a function on that device. The agent logic is responsible for accepting requests from clients in the OOI, performing whatever infrastructure logic is required for that request, then translating that into the detailed actions needed to communicate with its resource.

With the goal of making a fairly standard agent interface with many different types of instruments and platforms, the bulk of the work is in generating the translation drivers that work with individual instrument interfaces. Since there are so many, the IPAA work is to be seen more as software production once some of the common design is worked out.

Please see the Marine Integration section in the ION System Architecture and its child pages for high-level architecture and interfaces for all MI elements.

Design Elements

The links above mostly refer to the Marine Integration section in the ION System Architecture.

Materials About Sensors

  • [ENG:Sensor Working Group Workspace] (see the sensor needs table)
  • [ENG:OOI Engineering] (see the acquisition schedule table)
  • Frank and Matt's early spreadsheet (complexity estimates, characteristics)
  • Early IO spreadsheet (miscellaneous early sensor information)
  • Life of an instrument (Ed Chapman's process from procurement through end of life)
  • [ENG:Instrument Integration Research] (CG Instruments)
  • [ENG:RSN Instruments Summary] (RSN Instruments)
  • [science:Instruments and Data Integration] (Maintained by Ed Chapman et al., see instrument procurement)
  • [science:Sampling Strategy] (Steve Ackleson's sampling strategy working group)
  • [science:Instruments and Data Integration] (Instrument integration page)
  • [science:Old Algorithms Page] (Algorithm working group, AKA "Pickles")

Instrument Development Kit

Marine Platform Integration

Sensor Set Development

Related Activities and Pages

MI Development

Notes and Reference Materials

Gumstix Overo Operating Systems, Root Filesystems and Distributions:

The Cellar

Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
Page: Marine Platform Integration
Page: Sensor Set Development
Page: CI-CG Common Driver Architecture Responses
Page: Instrument or Node Operational Specification (IOS or NOS)
Page: Copy of OOI Deployment June 2013
Page: Driver Development Process
Page: Driver Delivery Checklist
Page: Early Data Integration
Page: Instrument Development Kit
Page: Instrument Operational Specification - IOS
Page: Marine CyberPoP Activation
Page: Marine Integration R2E1
Page: Marine Integration R2E2
Page: Marine Integration R2E3
Page: Marine Integration - Sensor Set 1 Construction 2
Page: Marine Integration - Sensor Set 1 Construction 3
Page: Marine Integration - Sensor Set 2 Construction 1
Page: MI building guide
Page: Welcome to Marine Integrations
Page: Digi RealPort Virtual Serial Port
Page: MI Container Messaging Elements task
Page: MI Process Execution Elements task
Page: OOI Deployment August 2013
Page: OOI Deployments
Page: OOI Deployment July 2013
Page: OOI Deployment June 2013
Page: Building Port Agent on TS-7370
Page: OOI Deployment October 2013
Page: Packaging Versioned Drivers for Platforms and External Data Agents
Page: Driver Development Documentation
Page: OOI Deployment November 2013
Page: Marine Integration Tracking Points for Process Flow (Monthly Progress Reports)
Page: MI Service Bulletins
Page: Dataset Driver Developer Tutorial
Page: Instrument Driver Development Life Cycle
Page: Apache Camel Based Prototype
Page: UFrame VM Setup
Page: Marine Integration Design Notes
Page: Activating Dataset Agents for OOI Devices
Page: Dataset Agent Development Life Cycle
Page: Gumstix Installation and Deployment
Page: IDK Data Stream Configuration
Page: Instrument Use Cases and Configurations
Page: Marine Integration Designs
Page: masterParameters.xml file changes