Hi Chad,
Thanks for the info.
The collaborative approach seems more in line with the spirit of R, which
has seen exponential growth in user-contributions (see, for example,
http://r4stats.com/2013/03/19/r-2012-growth-exceeds-sas-all-time-total/).
If you do plan to release it, I would argue for CRAN (
http://cran.us.r-project.org/).
It's difficult to say how may people might use it; there are seismologists
that actively maintain packages though (e.g., Jonathan Lees).
-Andy
On Mon, Apr 21, 2014 at 10:56 PM, Chad Trabant <chad<at>iris.washington.edu>wrote:
Hi Andy,
To fill in some gaps there, we have an internal data processing system
that uses R and a library/module has been developed to fetch data from our
web service interfaces. We’ve discussed the possibility of releasing it
but have not come to any conclusion yet. I imagine it might best work as a
collaborative development/maintenance, where we release what we’ve got and
let the community of R users build on it. I’m curious how many R users
would use a web service access library?
If you do end up creating web service access code for R you might consider
releasing it in SeisCode (https://seiscode.iris.washington.edu/) or
having a bookmark in SeisCode to help folks find your work.
regards,
Chad
On Apr 19, 2014, at 10:12 AM, andy barbour <andy.barbour<at>gmail.com> wrote:
I can't say I wouldn't be curious to see an 'official' set of R codes...
I'll stay tuned.
On Fri, Apr 18, 2014 at 3:27 PM, Robert Casey <rob<at>iris.washington.edu>wrote:
I wonder if we should at all make mention of our R code for MUSTANG? I
don't think that Jon has made his version of the code public yet.
Just thinking out loud. Maybe better to keep it internal until we start
talking about a distributed MUSTANG-lite. Andy might feel better about
using a WADL for his stuff anyway.
-RobC
On Apr 18, 2014, at 2:37 PM, andy barbour wrote:
Hi Bruce,
OK, good to know.
In regards to the .wadl files... I'm developing a package for the R
programming language, and I use the wadl files to generate a list of query
parameters for a given webservice (so I don't have to remember them, or
visit the webpage each time). If you're interested the code is being
developed here: https://github.com/abarbour/irisws
thanks,
Andy
_______________________________________________
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
Andrew Barbour
Bruce Weertman
Robert Casey
Chad Trabant
