| System
Requirements |
- Any
computer with a Java 1.2 virtual machine or later
-
eqWatch only - JDBC enabled database, eg. MySQL or SQL Server
|
| eqWatch |
|
| Inputs |
-
Earthquake and state of health information telemetered from
seismographs as PC-SUDS files
-
Manually entered arrivals
-
Emails from other systems
|
| Outputs |
- Triggers
stored in a database. Most commercial databases can be used,
allowing the data to be used in a wide variety of other programs
such as eqFocus,
GIS, spreadsheets and web pages
-
State of health history for each contributing data source
-
A web page of the event, which includes a map, arrivals, magnitudes
and location. The page is based on an easily modifiable template
-
Email, pager and SMS messages give users a quick alert within
a few minutes of an earthquake, and are also used for network
health alerts. Updated alerts are sent as more information becomes
available
-
Audible alert when an earthquake is detected
|
| Display |
- Network
state of health information
-
Log of recent arrivals and alerts
|
| eqLogger |
|
| Inputs |
- PC-SUDS
files generated by any number of seismographs. Data may include
waveforms, detected arrivals, maximum amplitude and frequency,
earthquake duration and state of health information
|
| Outputs |
- Trigger
information stored in PC-SUDS files can be sent to remote sites
running eqWatch via FTP (including via dial-up connection)
-
Earthquake and state of health alerts
-
PC-SUDS files compressed and stored in a ring-buffered archive
using a hierarchical file system
-
PC-SUDS files extracted from data archive
-
Log file containing triggers, dial-up history, etc.
-
Alarm on:
- Seismograph trigger
- Seismograph battery level and storage capacity
- Seismic signal level
|
| Display |
- Continuous
waveforms
- Archived
data
- Operational
status and history of archive
-
Seismograph state of health information
-
Dial-up telephone statistics (for monitoring the costs and quality
of a dial-up connection)
|
