search

usgs / swarm

a Java application designed to display and analyze seismic waveforms in real-time.
http://volcanoes.usgs.gov/software/swarm
Other
36 stars 16 forks source link

Add new data source (Enhancement, not bug) #141

Closed osop-raspishake closed 6 years ago

osop-raspishake commented 7 years ago

New data source tab: "OSOP Wave Server" (turns SeisComP SDS into a wave server)

Same code as WWS but on port 16032 by default.

osop-raspishake commented 7 years ago

Sorry, Jargon. SDS = the SeisComP Data Structure or the miniSEED files on disk.

tparker-usgs commented 7 years ago

We're reluctant to add another option to the current data source pane if it doesn't affect functionality. However, it may be possible to provide some annotation in the GUI to note common default port number of known servers.

osop-raspishake commented 7 years ago

Bummer :) Perhaps "Winston Wave Server / OWS" or "WWS/ OWS"

The annotations could be:

" Use this data source to connect to a Winston Wave Server (WWS) or OSOP Wave Server (OWS). The default port for the OWS is 16032. "

Then,

" Port: 16022 Winston default: 16022, OWS default: 16032 "

dlnorgaard commented 6 years ago

How's this?

image

Spelling out OSOP Wave Server would require a second line. Looked cleaner if I could get the annotation on one line.

tparker-usgs commented 6 years ago

The text should make the distinction between protocol and application more clear. We wouldn't want to list every program which supports the Winston Wave Server protocol in the box. Maybe something more like:

Use this data source to connect to servers which support the Winston Wave Server protocol (e.g. WWS or OWS)

I would leave just the one 16022 default. That's the default used by the WWS protocol.

dlnorgaard commented 6 years ago

I'm inclined to agree with Tom on not wanting to list all programs that support the protocol. Reverting, with minor change, to:

image

dlnorgaard commented 6 years ago

Sorry Branden!

osop-raspishake commented 6 years ago

Thank you Diana and Tom:

Good morning.

Technically, OWS is a completely separate protocol. We just spoof the WWS protocol when data requests are received from Swarm in order to play well with Swarm/ make things transparent to Swarm. 7 years ago when the Swarm code was not in github, it was just easier to it this way. Actually, I do not think we thought it was even possible to create a branch of Swarm that spoke directly to OWS and then send a merge request.

How OWS is different from WWS?: It gets its data from both SeedLink and the SeisComP Data Structure (SDS) miniSEED database. There is mysql waveform database involved.

I originally requested that "OSOP Wave Server (OWS)" appear in a separate tab just to make it easier for users to find it and configure things, mostly first time users. At the moment, users still get confused because there is no mention of OSOP Wave Server, only WWS. But it is a minor point, really.

Thank you guys for your support and for all of the recent enhancements to Swarm!

Yours, Branden