The Wave Server (OWS) bridges the gap between your Earthworm and SeisComP Systems.
At Raspberry Shake we encourage users to send all data, regardless of flavor, to a centralized Seedlink wave server for archival in a SeisComP Data Structure (SDS) waveform database as daily miniSEED records. Streams can then be imported into Earthworm and Earlybird systems with slink2ew. This greatly simplifies acquisition protocols and allows for redundant data processing systems (e.g., Earthworm, Earlybird and/ or SeisComP) to all feed off a single data acquisition and archival system (Seedlink + slarchive).
In 2012, we introduced a new product in C++ called the Wave Server (OWS), which essentially makes the SDS look like a wave server. The user points their OWS at their Seedlink server(s) and SDS miniSEED database. Then everything is transparent to Earthworm: getmenu, waveman2disk, heli_ewII, localmag, gmew, ew2mseed, Swarm and anything else that requires a wave server all work as normal. The Wave Server (OWS) streams data directly from the Seedlink server. Older data is instantly queued up from the SDS miniSEED database. The Wave Server (OWS) drives Swarm and other tools as fast (often faster) as the Winston Wave Server (WWS).
Earthworm modules known to work with the Wave Server (OWS):
- Theoretically, everything is transparent to Earthworm and anything else that requires a wave server should work.
Other programs known to work with the Wave Server (OWS):
- Obspy’s obspy.earthworm