Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!zephyr.ens.tek.com!uw-beaver!cornell!ken From: ken@gvax.cs.cornell.edu (Ken Birman) Newsgroups: comp.sys.isis Subject: Seismic monitoring using ISIS Message-ID: <35194@cornell.UUCP> Date: 15 Dec 89 13:59:25 GMT Sender: nobody@cornell.UUCP Reply-To: jackson@gymer.css.gov (Jerry Jackson) Distribution: comp Organization: Science Aplications Int'l Corp. Lines: 37 Here at SAIC in San Diego, we are using ISIS to build a worldwide monitoring system that locates and identifies seismic events. The system is intended to determine if particular events could be the results of nuclear weapons testing. Data come in from a variety of sensors and several seismic arrays on a continuous basis. One of our design goals is to provide for continuous operation of the system without requiring a large full-time staff. We were attracted to ISIS because of its strong support for fault tolerance and redundant computation. It has also proved flexible enough to allow us to bring together pre-existing pieces of code in a natural fashion. However, a couple of minor nits: 1) Executable size Currently, the size of an executable after linking in ISIS is quite large.. ~300K. I suspect the libraries might include some unnecessary code. 2) Program exit if ISIS is not running Some of our programs can run stand alone. It would be nice if they could attempt to connect to ISIS and get an error code back when it is not running so that they could take appropriate action. Another possibility would be some sort of "autostart" feature that would start up ISIS when a connection was requested. Thanks for the support. +-----------------------------------------------------------------------------+ | Jerry Jackson UUCP: seismo!esosun!jackson | | Geophysics Division, MS/12 ARPA: jackson@esosun.css.gov | | SAIC SOUND: (619)458-4924 | | 10210 Campus Point Drive | | San Diego, CA 92121 | +-----------------------------------------------------------------------------+