SERVOGrid Basics. SERVOGrid is our project to build a distributed computing infrastructure to support earthquake simulation codes. We use Web Services for this. We build portal interfaces to these web services out of portlets. Portlets for Java portals are standardized (JSR 168)
Implement Open Geospatial Consortium standards for Sensor Grids (see supplemental slides).
We are outlining a more ambitious integration of Robert Granat’s RDAHMM with GPS data.
I will be visiting JPL in early February.
Some questions we have are on the right.
Direct (or at least closer) access to GPS stations?
Any documentation on the filtering process?
What kind of filters are applied on the raw data? Can it be automated?
How is data stored, in a DB or just in files?
How do the stations communicate with the servers?
What protocols are being used for transport, etc?
Are there any web-based interfaces to stations or to the data stores?
Are the GPS stations configurable?
How often do they send out data, can you change the interval?
What are the most important data formats for you? (JPL,SOPAC,USGS)
Are there any other formats we need to support?
What (other) kinds of applications are there to use the GPS data?Next Steps and Questions (Jan)
Data is read / written from / to various data resources
Web Service EP
Data Flows as a stream of messages between WSProxies through the brokering network
Kernel connects to nearest broker and communicates with other kernels with messages
Handlers steer web services via simple SOAP requestsHPSearch Architecture
Actual Data Flow between components takes place through the brokering network
Virtual Data Flow between various components
Links between Brokers
WSProxy wrapped service
Kernel manages (steers) the various services
Matlab ScriptHPSearch for RDAHMM + GPS
Slides Prepared by Galip Aydin
A sample Sensor Web that utilizes Information Service and Narada Brokering.