I’ve had a couple of tweet replies from Raspishake asking why I don’t use Dataview. Well I do, but I find SWARM more convenient for a lot of what I do.
I have a Shake and Boom. When I open SWARM I usually tile both helicorders across one 4K screen so I can easily compare the seismic and infrasound signals. Often I’m looking for meteors and if I find a likely meteor signal, I check the seismic trace to make sure it’s not triggered from a seismic event. As far as I know ATM Dataview can’t have two helicorders side by side.
When it comes to features to enhance Dataview perhaps some way to identify cross channel triggering (particularly for the shake and boom) would be nice. That’s essentially what I’m doing with the helicorders side by side (to make it easier for me to manually choose the right times to compare the waveforms in detail also side by side). However, the ability to plot both channels on the one helicorder and wave detail in different colours might be another but better simple way to do it.
I have toyed with other ideas for checking for cross channel triggering/interference such as writing python code to compare the change in both channels (essentially the derivative of the one channel divided by the other) but that a bit beyond me yet.
That’s the main technical reason I use SWARM in preference to Dataview (though I still use Dataview for a calibrated air pressure signal of a meteor signal). Apart from that, it’s simply familiarity and convenience - I have it open looking for meteors, so use it.
The only other reason SWARM may be more useful is IF I HAVE IT OPEN and I hear something that might be an interesting infrasound signal (or one I’d like to be able to identify later) I can watch the trace in SWARM with (I think) less lag than Dataview.
Al.