Oceans '04 MTS/IEEE Techno-Ocean '04 (IEEE Cat. No.04CH37600)
DOI: 10.1109/oceans.2004.1406448
|View full text |Cite
|
Sign up to set email alerts
|

Software infrastructure and applications for the Monterey Ocean Observing System: design and implementation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1

Citation Types

0
5
0

Publication Types

Select...
5
2

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(5 citation statements)
references
References 8 publications
0
5
0
Order By: Relevance
“…Two major instantiated OSML files were SensorControl.xml and SensorInfo.xml, the former of which mainly related to establishing a remote connection while the latter of which included supplement information for undersea equipment. The management of a sensor’s command information mainly utilized component technology [ 22 ], which was programmed to display and manage various types of control commands in a tree structure in the main interface using methods provided by the dynamic link library and .NET class, and corresponding instantiated OSML files.…”
Section: Plug-and-play Implementation Of Esomsmentioning
confidence: 99%
“…Two major instantiated OSML files were SensorControl.xml and SensorInfo.xml, the former of which mainly related to establishing a remote connection while the latter of which included supplement information for undersea equipment. The management of a sensor’s command information mainly utilized component technology [ 22 ], which was programmed to display and manage various types of control commands in a tree structure in the main interface using methods provided by the dynamic link library and .NET class, and corresponding instantiated OSML files.…”
Section: Plug-and-play Implementation Of Esomsmentioning
confidence: 99%
“…The key to achieving this is interface standardization, i.e., to unify the hardware and software interfaces of ocean instruments in the system. Since there is no common standard for ocean instruments, the current solution is adding a protocol layer to the system architecture of an ocean observatory [5], as shown in Figure 2. Drivers are customized for each instrument type to translate between native instrument protocols and individual observatory protocol with description files [6].…”
Section: Introductionmentioning
confidence: 99%
“…However, Java requires considerable computing and communication resources [18]. The PUCK firmware has also been evaluated to combine with IEEE 1451 and OGC-SWE standards [5,6,19,20]. The NeXOS project developed the Smart Electronic Interface for Sensors and Instruments (SEISI) to enable web-based sharing, discovery, exchange, processing, and operation of ocean observations [21].…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…The MOOS Mooring Controller (MMC) project [1] is focused on building the hardware and electronic infrastructure to support the unique requirements of disconnected, low-bandwidth ocean observing assets. The Software Infrastructure and Applications for MOOS (SIAM) project [2] is building the software infrastructure for handling plug and work instruments to enable automated configuration and control of those same assets. The Shore Side Data System (SSDS) [3] project is building the data management system to track the information coming from the observatory and its instruments and provide user access to those managed data.…”
Section: Introductionmentioning
confidence: 99%