n. hurlburt, s. freeland, p. bose, m. woodward & g. slater...
TRANSCRIPT
CoSEC Workflow
N. Hurlburt, S. Freeland, P. Bose, M. Woodward & G. SlaterLockheed Martin Solar and Astrophysics Laboratory
http://cosec.LMSAL.com
Composite Provider
ManageComposite
uses
...ExecuteComp. X
ExecuteComp. Y
LM
Execution Agent(Web Services)
RequestExecution
uses U
Service Lookup Server(UDDI + WSDL)
Registration Search
uses C
Web GUI
User Agentuses
LM
LM
Knowledge BaseResult Markup + Domain Knowledge
(DAML)
Assert Query Event
usesC
Web Service
Execute
uses CWeb Service
Execute
uses C...
STATUS•Stable prototype CoSEC 0.9•Expanding number and variety of basic CoSEC services•Completing draft CoSEC 0.1 users/providers guide •Drafting schema for CoSEC service providers •Interoperate with CDAWeb at LWS Science Meeting
•CoSEC as client to Translator services•Prepare demonstration with VSO/EGSO
•CoSEC as client to VSO & EGSO•EGSO as client to SSW servers•VSO to simple SSW servers
The CoSEC 1.0 architecture will• Scale to SDO data rates, multi-spacecraft LWS missions and non-LWS data
sources and users• Leverage existing software frameworks, standards and datasets• Forge collaborative ventures between the LWS community: data analysts,
modelers, and downstream users.• Present integrated views of LWS data to all researchers.• Intelligently fuse and assimilate data from distributed heterogeneous
sources.The technologies which underpin CoSEC:• Exploit Sensorweb Architecture: We use our current sensorweb
architecture to incorporate data assimilation, task-driven dynamic integration and collaborative coordination of multiple PIs, multiple instruments
• Incorporate Advanced SolarSoft Services: On-going development of SolarSoft data analysis tools will be folded into the CoSEC system.
• Expand to non-SolarSoft services: Living with a Star science needs access to heterogeneous data sources. We are re-architecting the PSELWS prototype to support emerging web-service standards.
• Integrate with related solar efforts - EGSO, VSO: We work closely with the EGSO team on security and resource control issues, and the VSO team on data descriptions for collaboration.
• Develop “market” approach to LWS software and data services: We will jumpstart the CoSEC system by developing a base set of distributed services and by designing LWS-specific services for use and modification by the LWS community.
The Living With a Star program at NASA is well underway. In five years, a fully functional, cost-effective system must be in place for acquiring and analyzing the torrent of SDO data, and for integrating them with other SEC missions. The LWS Science Architecture Team has identified this as “… a critical management challenge for the LWS program...” (August 2001). With the anticipated launch date of SDO in August 2007, the system architecture needs to be well defined at the time that the science teams start detailed development of their data processing systems in 2005/6.
We are creating a test-bed system to do just this based upon the prototype, distributed data system architecture developed under the “Problem-Solving Environment for Living with a Star” LWS project; merging this system with the best attributes of the aligned efforts towards the Virtual Solar Observatory prototype and the European Grid of Solar Observations test-bed, and exploiting recent SolarSoft application development, to create the Collaborative Sun Earth Connector (CoSEC) for LWS. Our coordinated effort among these three teams will quickly bring a large fraction of solar data into the LWS community and create a cost-effective environment for assimilating data from LWS and related SEC spacecraft.
Here we demonstrate how CoSEC integrates data analysis of Solar, Heliospheric and MagnetosphericTransients.
CoSEC Service RegistrationWe define a service and datatype ontology to help in defining and coordinating services. Currently these are relevant primarily to SolarSoft, but others can easily be added. Here are the steps to registering a service:1. Define CoSEC name2. Identify service URL3. Provide description for user4. Select CoSEC service type from Service Ontology5. Define Input & Output names, and default values7. Select CoSEC data types from Data Ontology8. Select constraints9. View completed service
New Services for 2004• Potential Field extrapolations
• Entire SOHO mission online• 6 hour cadence• FOV, field density selectable
• File Conversion Services (courtesy CDAWeb)• FITS to CDF• CDF to FITS• CDF to ASCII• CDAWeb data (coming soon)
• Space Craft Services (courtesy SSCWeb)• Spacecraft location (coming soon)
Problem: How to locate, assemble and display data associated with a transient Event?
1. Find Starting point (GOES Database)2. Locate Source (SOHO/EIT Database)3. Track through Heliosphere (SOHO/LASCO)4. Identify Particle Fluxes (ACE, CDAWeb)5. Observe Geospace Response (IMAGE, CDAWeb)
EIT BracketEvent
EITCalibration
Event Locator
LASCOBracket
PotentialField Map
EIT Calibration
GOES Xray
After
Before
LASCOSpeed
HeliographicLocation
ACE Particles
IMAGE
Wind Extrapolation
SourceField
ParticleTrajectory
CMEVelocity
WindVelocity
CoSECService
NotIntegrated
TBD
ExpandTime
Flare Time
The Details:
CoSEC 1.0 Architecture