Hello all,
I am using ws-timeseries to plot trace data in a time window from 5 min
before to 20 min after picks made in the Early-est real-time system
(http://early-est.alomax.net)
If I run ws-timeseries for a channel right after it is picked, then I
get a plot from 5 min before the pick to some small interval T1 after
the pick. If I then wait some time and re-run ws-timeseries for the
channel, I would expect to get data from 5 min before the pick until
some interval T2>T1 after the pick. Instead, the plot always ends at
interval T1 after the pick. The plotted time window remains the same
even if I add filtering to the ws-timeseries request or if I try the
same ws-timeseries request in a different browser, so this behavior
seems to originate on the server side.
(you can reproduce this behavior this at
http://early-est.alomax.net/warning_list.html, ws-timeseries is invoked
by the "BRB" and "HF" links in the "stream" column).
Any suggestions on how to disable this apparent caching?
Or is this something that is inherent in the web-services back-end?
Perhaps behind the scenes ws-timeseries is caching the data window found
for my first request, and using this data window for all later requests
for the same channel, without recognizing that more of the requested
data has become available. If so, for real-time work it would be useful
that new data is returned as it becomes available.
Thanks,
Best regards,
Anthony
--
Sent from my iClayTablet
*Anthony Lomax*
*161 Allée du Micocoulier, 06370 Mouans-Sartoux, France*
*tel: +33 (0)4 93 75 25 02 e-mail:****alomax<at>free.fr*
<alomax<at>free.fr>***web:****http://www.alomax.net*
http://www.alomax.net/**
*ALomax Scientific****http://www.alomax.net/alss***
*Science & Special Topics****http://www.alomax.net/science***
I am using ws-timeseries to plot trace data in a time window from 5 min
before to 20 min after picks made in the Early-est real-time system
(http://early-est.alomax.net)
If I run ws-timeseries for a channel right after it is picked, then I
get a plot from 5 min before the pick to some small interval T1 after
the pick. If I then wait some time and re-run ws-timeseries for the
channel, I would expect to get data from 5 min before the pick until
some interval T2>T1 after the pick. Instead, the plot always ends at
interval T1 after the pick. The plotted time window remains the same
even if I add filtering to the ws-timeseries request or if I try the
same ws-timeseries request in a different browser, so this behavior
seems to originate on the server side.
(you can reproduce this behavior this at
http://early-est.alomax.net/warning_list.html, ws-timeseries is invoked
by the "BRB" and "HF" links in the "stream" column).
Any suggestions on how to disable this apparent caching?
Or is this something that is inherent in the web-services back-end?
Perhaps behind the scenes ws-timeseries is caching the data window found
for my first request, and using this data window for all later requests
for the same channel, without recognizing that more of the requested
data has become available. If so, for real-time work it would be useful
that new data is returned as it becomes available.
Thanks,
Best regards,
Anthony
--
Sent from my iClayTablet
*Anthony Lomax*
*161 Allée du Micocoulier, 06370 Mouans-Sartoux, France*
*tel: +33 (0)4 93 75 25 02 e-mail:****alomax<at>free.fr*
<alomax<at>free.fr>***web:****http://www.alomax.net*
http://www.alomax.net/**
*ALomax Scientific****http://www.alomax.net/alss***
*Science & Special Topics****http://www.alomax.net/science***
-
Anthony.
This is a bug with ws-dataselect. It defaults to using the cached data
if it's less than one hour old.
I'm not sure how that got left in there. I see that it's supposed to
go look at the data and decide if a
rebuild of cache is warranted.
Cheers,
-Bruce
On Feb 28, 2012, at 12:48 AM, Anthony Lomax wrote:
Hello all,
I am using ws-timeseries to plot trace data in a time window from 5
min before to 20 min after picks made in the Early-est real-time
system (http://early-est.alomax.net)
If I run ws-timeseries for a channel right after it is picked, then
I get a plot from 5 min before the pick to some small interval T1
after the pick. If I then wait some time and re-run ws-timeseries
for the channel, I would expect to get data from 5 min before the
pick until some interval T2>T1 after the pick. Instead, the plot
always ends at interval T1 after the pick. The plotted time window
remains the same even if I add filtering to the ws-timeseries
request or if I try the same ws-timeseries request in a different
browser, so this behavior seems to originate on the server side.
(you can reproduce this behavior this at http://early-est.alomax.net/warning_list.html
, ws-timeseries is invoked by the "BRB" and "HF" links in the
"stream" column).
Any suggestions on how to disable this apparent caching?
Or is this something that is inherent in the web-services back-end?
Perhaps behind the scenes ws-timeseries is caching the data window
found for my first request, and using this data window for all later
requests for the same channel, without recognizing that more of the
requested data has become available. If so, for real-time work it
would be useful that new data is returned as it becomes available.
Thanks,
Best regards,
Anthony
--
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; min-
height: 14.0px} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px
Helvetica; color: #cc0000} p.p3 {margin: 0.0px 0.0px 0.0px 0.0px;
font: 12.0px Helvetica; color: #666666} p.p4 {margin: 0.0px 0.0px
0.0px 0.0px; font: 12.0px Helvetica; color: #009900} p.p5 {margin:
0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; color: #0000ee}
span.s1 {color: #000000} span.s2 {text-decoration: underline ;
color: #0000ee} span.s3 {color: #009900} span.s4 {font: 12.0px
Times; color: #000000} span.s5 {text-decoration: underline} table.t1
{background-color: #000000} td.td1 {width: 567.0px; background-
color: #ffffff; margin: 0.5px 0.5px 0.5px 0.5px; padding: 10.0px
10.0px 10.0px 10.0px}
Sent from my iClayTablet
Anthony Lomax
161 Allée du Micocoulier, 06370 Mouans-Sartoux, France
tel: +33 (0)4 93 75 25 02 e-mail: alomax<at>free.fr web: http://www.alomax.net
ALomax Scientific http://www.alomax.net/alss
Science & Special Topics http://www.alomax.net/science
_______________________________________________
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
-
Thanks Bruce... this will be important for some upcoming additions to our
EPO Jamaseis software.
Glenn
On Tue, Feb 28, 2012 at 10:40 AM, Bruce Weertman
<bruce<at>iris.washington.edu>wrote:
Anthony.
This is a bug with ws-dataselect. It defaults to using the cached data if
it's less than one hour old.
I'm not sure how that got left in there. I see that it's supposed to go
look at the data and decide if a
rebuild of cache is warranted.
Cheers,
-Bruce
On Feb 28, 2012, at 12:48 AM, Anthony Lomax wrote:
Hello all,
I am using ws-timeseries to plot trace data in a time window from 5 min
______________________________**_________________
before to 20 min after picks made in the Early-est real-time system (
http://early-est.alomax.net)
If I run ws-timeseries for a channel right after it is picked, then I get
a plot from 5 min before the pick to some small interval T1 after the pick.
If I then wait some time and re-run ws-timeseries for the channel, I would
expect to get data from 5 min before the pick until some interval T2>T1
after the pick. Instead, the plot always ends at interval T1 after the
pick. The plotted time window remains the same even if I add filtering to
the ws-timeseries request or if I try the same ws-timeseries request in a
different browser, so this behavior seems to originate on the server side.
(you can reproduce this behavior this at http://early-est.alomax.net/**
warning_list.html http://early-est.alomax.net/warning_list.html,
ws-timeseries is invoked by the "BRB" and "HF" links in the "stream"
column).
Any suggestions on how to disable this apparent caching?
Or is this something that is inherent in the web-services back-end?
Perhaps behind the scenes ws-timeseries is caching the data window found
for my first request, and using this data window for all later requests for
the same channel, without recognizing that more of the requested data has
become available. If so, for real-time work it would be useful that new
data is returned as it becomes available.
Thanks,
Best regards,
Anthony
--
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;
min-height: 14.0px} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px
Helvetica; color: #cc0000} p.p3 {margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica; color: #666666} p.p4 {margin: 0.0px 0.0px 0.0px 0.0px;
font: 12.0px Helvetica; color: #009900} p.p5 {margin: 0.0px 0.0px 0.0px
0.0px; font: 12.0px Helvetica; color: #0000ee} span.s1 {color: #000000}
span.s2 {text-decoration: underline ; color: #0000ee} span.s3 {color:
#009900} span.s4 {font: 12.0px Times; color: #000000} span.s5
{text-decoration: underline} table.t1 {background-color: #000000} td.td1
{width: 567.0px; background-color: #ffffff; margin: 0.5px 0.5px 0.5px
0.5px; padding: 10.0px 10.0px 10.0px 10.0px}
Sent from my iClayTablet
Anthony Lomax
161 Allée du Micocoulier, 06370 Mouans-Sartoux, France
tel: +33 (0)4 93 75 25 02 e-mail: alomax<at>free.fr web:
http://www.alomax.net
ALomax Scientific http://www.alomax.net/alss
Science & Special Topics http://www.alomax.net/science
______________________________**_________________
webservices mailing list
webservices<at>iris.washington.**edu <webservices<at>iris.washington.edu>
http://www.iris.washington.**edu/mailman/listinfo/**webserviceshttp://www.iris.washington.edu/mailman/listinfo/webservices
webservices mailing list
webservices<at>iris.washington.**edu <webservices<at>iris.washington.edu>
http://www.iris.washington.**edu/mailman/listinfo/**webserviceshttp://www.iris.washington.edu/mailman/listinfo/webservices
-
Hi Bruce,
On 2012/02/28 17:40, Bruce Weertman wrote:
Anthony.
OK. Good to hear that this is a "bug", so that it will eventually go
This is a bug with ws-dataselect. It defaults to using the cached data
if it's less than one hour old.
I'm not sure how that got left in there. I see that it's supposed to
go look at the data and decide if a
rebuild of cache is warranted.
away. But no rush for a fix with regards to my application in
Early-est, it is only an issue of elegance, for the most part!
Thanks,
Ciao,
Anthony
Cheers,
--
-Bruce
On Feb 28, 2012, at 12:48 AM, Anthony Lomax wrote:
Hello all,
_______________________________________________
I am using ws-timeseries to plot trace data in a time window from 5
min before to 20 min after picks made in the Early-est real-time
system (http://early-est.alomax.net)
If I run ws-timeseries for a channel right after it is picked, then I
get a plot from 5 min before the pick to some small interval T1 after
the pick. If I then wait some time and re-run ws-timeseries for the
channel, I would expect to get data from 5 min before the pick until
some interval T2>T1 after the pick. Instead, the plot always ends at
interval T1 after the pick. The plotted time window remains the same
even if I add filtering to the ws-timeseries request or if I try the
same ws-timeseries request in a different browser, so this behavior
seems to originate on the server side.
(you can reproduce this behavior this at
http://early-est.alomax.net/warning_list.html, ws-timeseries is
invoked by the "BRB" and "HF" links in the "stream" column).
Any suggestions on how to disable this apparent caching?
Or is this something that is inherent in the web-services back-end?
Perhaps behind the scenes ws-timeseries is caching the data window
found for my first request, and using this data window for all later
requests for the same channel, without recognizing that more of the
requested data has become available. If so, for real-time work it
would be useful that new data is returned as it becomes available.
Thanks,
Best regards,
Anthony
--
p.p1 {margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica;
min-height: 14.0px} p.p2 {margin: 0.0px 0.0px 0.0px 0.0px; font:
12.0px Helvetica; color: #cc0000} p.p3 {margin: 0.0px 0.0px 0.0px
0.0px; font: 12.0px Helvetica; color: #666666} p.p4 {margin: 0.0px
0.0px 0.0px 0.0px; font: 12.0px Helvetica; color: #009900} p.p5
{margin: 0.0px 0.0px 0.0px 0.0px; font: 12.0px Helvetica; color:
#0000ee} span.s1 {color: #000000} span.s2 {text-decoration: underline
; color: #0000ee} span.s3 {color: #009900} span.s4 {font: 12.0px
Times; color: #000000} span.s5 {text-decoration: underline} table.t1
{background-color: #000000} td.td1 {width: 567.0px; background-color:
#ffffff; margin: 0.5px 0.5px 0.5px 0.5px; padding: 10.0px 10.0px
10.0px 10.0px}
Sent from my iClayTablet
Anthony Lomax
161 Allée du Micocoulier, 06370 Mouans-Sartoux, France
tel: +33 (0)4 93 75 25 02 e-mail: alomax<at>free.fr web:
http://www.alomax.net
ALomax Scientific http://www.alomax.net/alss
Science & Special Topics http://www.alomax.net/science
_______________________________________________
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
Sent from my iClayTablet
*Anthony Lomax*
*161 Allée du Micocoulier, 06370 Mouans-Sartoux, France*
*tel: +33 (0)4 93 75 25 02 e-mail:****alomax<at>free.fr*
<alomax<at>free.fr>***web:****http://www.alomax.net*
http://www.alomax.net/**
*ALomax Scientific****http://www.alomax.net/alss***
*Science & Special Topics****http://www.alomax.net/science***
-
Hello all,
As an experiment in interactive viewing of seismograms on web-enabled,
mobile devices, I have developed a simple tool, SeisGramWeb, to view
trace data using ws-timeseries. SeisGramWeb uses only simple and basic
HTML and Javascript, relying on ws-timeseries for the heavy work of
trace processing and plotting, and the layout of SeisGramWeb is designed
for both large and small screens.
(Note also that at the current time, Java is not available on devices
such as iPhone, iPod and iPad...)
SeisGramWeb can be launched from the Early-est, Event/Pick List page at
http://early-est.alomax.net/warning_list.html (invoked by the "BRB" and
"HF" links in the "stream" column). This is part of the INGV, Early-est
real-time system (http://early-est.alomax.net).
Here is a direct link to a sample trace:
http://alomax.free.fr/webtools/sgweb.html?http://www.iris.edu/ws/timeseries/query?net=GT&sta=CPUP&loc=00&cha=BHZ&start=2012-03-05T07:45:35&dur=257
I would be interested in any feedback about how this approach works on
different devices, or any other comments about this tool or working with
mobile devices.
Thanks very much,
Anthony
PS - In continuing my work with the timeseries ws, I found that changing
the starttime prevents using the cached data.
On 2012/02/28 17:46, Anthony Lomax wrote:
Hi Bruce,
--
On 2012/02/28 17:40, Bruce Weertman wrote:
Anthony.
OK. Good to hear that this is a "bug", so that it will eventually go
This is a bug with ws-dataselect. It defaults to using the cached
data if it's less than one hour old.
I'm not sure how that got left in there. I see that it's supposed to
go look at the data and decide if a
rebuild of cache is warranted.
away. But no rush for a fix with regards to my application in
Early-est, it is only an issue of elegance, for the most part!
Thanks,
Ciao,
Anthony
Cheers,
_______________________________________________
-Bruce
On Feb 28, 2012, at 12:48 AM, Anthony Lomax wrote:
Hello all,
_______________________________________________
I am using ws-timeseries to plot trace data in a time window from 5
min before to 20 min after picks made in the Early-est real-time
system (http://early-est.alomax.net)
If I run ws-timeseries for a channel right after it is picked, then
I get a plot from 5 min before the pick to some small interval T1
after the pick. If I then wait some time and re-run ws-timeseries
for the channel, I would expect to get data from 5 min before the
pick until some interval T2>T1 after the pick. Instead, the plot
always ends at interval T1 after the pick. The plotted time window
remains the same even if I add filtering to the ws-timeseries
request or if I try the same ws-timeseries request in a different
browser, so this behavior seems to originate on the server side.
(you can reproduce this behavior this at
http://early-est.alomax.net/warning_list.html, ws-timeseries is
invoked by the "BRB" and "HF" links in the "stream" column).
Any suggestions on how to disable this apparent caching?
Or is this something that is inherent in the web-services back-end?
Perhaps behind the scenes ws-timeseries is caching the data window
found for my first request, and using this data window for all later
requests for the same channel, without recognizing that more of the
requested data has become available. If so, for real-time work it
would be useful that new data is returned as it becomes available.
Thanks,
Best regards,
Anthony
_______________________________________________
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
webservices mailing list
webservices<at>iris.washington.edu
http://www.iris.washington.edu/mailman/listinfo/webservices
Sent from my iClayTablet
*Anthony Lomax*
161 Allée du Micocoulier, 06370 Mouans-Sartoux, France
tel: +33 (0)4 93 75 25 02 e-mail: anthony<at>alomax.net
<anthony<at>alomax.net> web: http://www.alomax.net
http://www.alomax.net/
Science & Special Topics http://www.alomax.net/science
ALomax Scientific http://www.alomax.net/alss
-
Hi Anthony-
This tool seems like it would make for a convenient viewer to replace
an older applet tool we've been using for the BUD for some time
(wiggles) as we migrate to Linux. Would it be possible for us to get
a copy of this for use in IRIS web pages, or is there some kind of
contractual thing we would need to work out? We can, of course, leave
the logos, credits, and attribution in place since it's your work.
-Rob
On Mar 6, 2012, at 6:35 AM, Anthony Lomax wrote:
Hello all,
As an experiment in interactive viewing of seismograms on web-
enabled, mobile devices, I have developed a simple tool,
SeisGramWeb, to view trace data using ws-timeseries. SeisGramWeb
uses only simple and basic HTML and Javascript, relying on ws-
timeseries for the heavy work of trace processing and plotting, and
the layout of SeisGramWeb is designed for both large and small
screens.
(Note also that at the current time, Java is not available on
devices such as iPhone, iPod and iPad...)
SeisGramWeb can be launched from the Early-est, Event/Pick List page
at http://early-est.alomax.net/warning_list.html (invoked by the
"BRB" and "HF" links in the "stream" column). This is part of the
INGV, Early-est real-time system (http://early-est.alomax.net).
Here is a direct link to a sample trace: http://alomax.free.fr/webtools/sgweb.html?http://www.iris.edu/ws/timeseries/query
?net=GT&sta=CPUP&loc=00&cha=BHZ&start=2012-03-05T07:45:35&dur=257
I would be interested in any feedback about how this approach works
on different devices, or any other comments about this tool or
working with mobile devices.
Thanks very much,
Anthony
PS - In continuing my work with the timeseries ws, I found that
changing the starttime prevents using the cached data.
-
Anthony Lomax
2013-01-22 02:17:30Hello all,
I have recently updated the SeisGramWeb, browser-based seismogram viewer:
1. The viewer javascript code is now developed using Google Web Toolkit
(https://developers.google.com/web-toolkit/). The use of GWT gives
easier development of more sophisticated code, graphics and user
interfaces, explicit support for different platforms and devices,
... GWT should make much easier and robust future additions such
are plotting time-series from raw SAC or other data files, complex
interaction with the time-series and more processing options.
2. Making use of the GWT features, I have added mouse-based, trace
zooming: click on the trace image at two successive points in time
to define a zoom window.
See below for general information and links.
Any comments are always appreciated,
Best regards,
Anthony
On 2012/03/06 15:35, Anthony Lomax wrote:
Hello all,
--
As an experiment in interactive viewing of seismograms on web-enabled,
mobile devices, I have developed a simple tool, SeisGramWeb, to view
trace data using ws-timeseries. SeisGramWeb uses only simple and
basic HTML and Javascript, relying on ws-timeseries for the heavy
work of trace processing and plotting, and the layout of SeisGramWeb
is designed for both large and small screens.
(Note also that at the current time, Java is not available on devices
such as iPhone, iPod and iPad...)
SeisGramWeb can be launched from the Early-est, Event/Pick List page
at http://early-est.alomax.net/warning_list.html (invoked by the "BRB"
and "HF" links in the "stream" column). This is part of the INGV,
Early-est real-time system (http://early-est.alomax.net).
Here is a direct link to a sample trace:
http://alomax.free.fr/webtools/sgweb.html?http://www.iris.edu/ws/timeseries/query?net=GT&sta=CPUP&loc=00&cha=BHZ&start=2012-03-05T07:45:35&dur=257
I would be interested in any feedback about how this approach works on
different devices, or any other comments about this tool or working
with mobile devices.
Thanks very much,
Anthony
Sent from my iClayTablet
------------------------------------------------------------------------
*Anthony Lomax*
*161 Allée du Micocoulier, 06370 Mouans-Sartoux, France*
*tel: +33 (0)4 93 75 25 02 e-mail: anthony<at>alomax.net
<anthony<at>alomax.net> web: http://www.alomax.net
http://www.alomax.net/ *
*Science & Special Topics: * *http://www.alomax.net/science*
*ALomax Scientific: * *http://www.alomax.net/alss*
------------------------------------------------------------------------
-
Robert Casey
2013-01-22 17:14:20
Hi Anthony-
Thanks for the update, I see that your updated app is at the same URL
as your sample trace example below. I was able to figure out how to
do the two-tap zoom. Looks great! Where do you think you'll take
things from here?
-Rob
On Jan 21, 2013, at 9:17 AM, Anthony Lomax wrote:
Hello all,
I have recently updated the SeisGramWeb, browser-based seismogram
viewer:
The viewer javascript code is now developed using Google Web Toolkit
(https://developers.google.com/web-toolkit/). The use of GWT gives
easier development of more sophisticated code, graphics and user
interfaces, explicit support for different platforms and
devices, ... GWT should make much easier and robust future
additions such are plotting time-series from raw SAC or other data
files, complex interaction with the time-series and more processing
options.
Making use of the GWT features, I have added mouse-based, trace
zooming: click on the trace image at two successive points in time
to define a zoom window.
See below for general information and links.
Any comments are always appreciated,
Best regards,
Anthony
On 2012/03/06 15:35, Anthony Lomax wrote:
Hello all,
--
As an experiment in interactive viewing of seismograms on web-
enabled, mobile devices, I have developed a simple tool,
SeisGramWeb, to view trace data using ws-timeseries. SeisGramWeb
uses only simple and basic HTML and Javascript, relying on ws-
timeseries for the heavy work of trace processing and plotting,
and the layout of SeisGramWeb is designed for both large and
small screens.
(Note also that at the current time, Java is not available on
devices such as iPhone, iPod and iPad...)
SeisGramWeb can be launched from the Early-est, Event/Pick List
page at http://early-est.alomax.net/warning_list.html (invoked by
the "BRB" and "HF" links in the "stream" column). This is part of
the INGV, Early-est real-time system (http://early-est.alomax.net).
Here is a direct link to a sample trace: http://alomax.free.fr/webtools/sgweb.html?http://www.iris.edu/ws/timeseries/query
?net=GT&sta=CPUP&loc=00&cha=BHZ&start=2012-03-05T07:45:35&dur=257
I would be interested in any feedback about how this approach works
on different devices, or any other comments about this tool or
working with mobile devices.
Thanks very much,
Anthony
Sent from my iClayTablet
Anthony Lomax
161 Allée du Micocoulier, 06370 Mouans-Sartoux, France
tel: +33 (0)4 93 75 25 02 e-mail: anthony<at>alomax.net web: http://www.alomax.net
Science & Special Topics: http://www.alomax.net/science
ALomax Scientific: http://www.alomax.net/alss
-
Anthony Lomax
2013-07-04 22:01:09Hello all,
I have recently updated the SeisGramWeb, browser-based and mobile-device
ready seismogram viewer:
1. The viewer now supports using
http://service.iris.edu/irisws/timeseries/1/ as well as the
deprecated, legacy http://www.iris.edu/ws/timeseries/.
2. To demonstrate trace processing in SeisGramWeb, I have added a
sub-menu "Filter" to access the subset of IRISWS timeseries Filter
options that use only a true/false parameter.
See http://alomax.free.fr/webtools/resources/info.html for general
information and links.
One some devices you may need to clear your browser cache before the
changes will appear.
Any comments are always appreciated,
Best regards,
Anthony
On 2013/01/21 18:17, Anthony Lomax wrote:
Hello all,
--
I have recently updated the SeisGramWeb, browser-based seismogram viewer:
1. The viewer javascript code is now developed using Google Web
Toolkit (https://developers.google.com/web-toolkit/). The use of
GWT gives easier development of more sophisticated code, graphics
and user interfaces, explicit support for different platforms and
devices, ... GWT should make much easier and robust future
additions such are plotting time-series from raw SAC or other data
files, complex interaction with the time-series and more
processing options.
2. Making use of the GWT features, I have added mouse-based, trace
zooming: click on the trace image at two successive points in time
to define a zoom window.
See below for general information and links.
Any comments are always appreciated,
Best regards,
Anthony
On 2012/03/06 15:35, Anthony Lomax wrote:
Hello all,
--
As an experiment in interactive viewing of seismograms on
web-enabled, mobile devices, I have developed a simple tool,
SeisGramWeb, to view trace data using ws-timeseries. SeisGramWeb uses
only simple and basic HTML and Javascript, relying on ws-timeseries
for the heavy work of trace processing and plotting, and the layout
of SeisGramWeb is designed for both large and small screens.
(Note also that at the current time, Java is not available on devices
such as iPhone, iPod and iPad...)
SeisGramWeb can be launched from the Early-est, Event/Pick List page
at http://early-est.alomax.net/warning_list.html (invoked by the
"BRB" and "HF" links in the "stream" column). This is part of the
INGV, Early-est real-time system (http://early-est.alomax.net).
Here is a direct link to a sample trace:
http://alomax.free.fr/webtools/sgweb.html?http://www.iris.edu/ws/timeseries/query?net=GT&sta=CPUP&loc=00&cha=BHZ&start=2012-03-05T07:45:35&dur=257
I would be interested in any feedback about how this approach works
on different devices, or any other comments about this tool or
working with mobile devices.
Thanks very much,
Anthony
Sent from my iClayTablet
------------------------------------------------------------------------
*Anthony Lomax*
*161 Allée du Micocoulier, 06370 Mouans-Sartoux, France*
*tel: +33 (0)4 93 75 25 02 e-mail: anthony<at>alomax.net
<anthony<at>alomax.net> web: http://www.alomax.net
http://www.alomax.net/ *
*Science & Special Topics: * *http://www.alomax.net/science*
*ALomax Scientific: * *http://www.alomax.net/alss*
------------------------------------------------------------------------
Sent from my iClayTablet
------------------------------------------------------------------------
*Anthony Lomax*
*161 Allée du Micocoulier, 06370 Mouans-Sartoux, France*
*tel: +33 (0)4 93 75 25 02 e-mail: anthony<at>alomax.net
<anthony<at>alomax.net> web: http://www.alomax.net
http://www.alomax.net/ *
*Science & Special Topics: * *http://www.alomax.net/science*
*Software: * *http://www.alomax.net/software* *- updates: *
*https://twitter.com/ALomaxNet*
------------------------------------------------------------------------
-
-
-
-
Bruce Weertman
Glenn Kroeger
