Solar / STP Event Coincidence SD

Introduction

A solar astronomer or solar terrestrial physicist wants to identify solar events that correspond to magnetosphere disturbances or other STP events. After identifying a time interval (and possibly location) for an STP event, the physicist can enter these parameters into a model that would advise likely intervals for time and origin of solar events that might have caused the STP event. The solar event time and position information then be used to search solar event catalogues for matching flares, CME's, and other events observed at the time and location predicted by the model.

Flow of Events (Revised)

1. First the physicist searches the registry catalogue for solar event catalogues via PerformRegistrySearch.

2. Astrogrid returns a list of solar event catalogues, such as the BATSE Solar Flare Server, via MySpaceStoreResults.

3. The physicist selects one or more solar event catalogues via SelectCatalogue.

4. The selected catalogues are searched for solar event time and position information via PerformCatalogueSearch.

5. A list of solar event times and positions is returned via MySpaceStoreResults.

6. Next, the physicist searches the registry catalogue for Solar-STP models event via PerformRegistrySearch.

7. Astrogrid returns a list of Solar-STP models via MySpaceStoreResults.

8. The physicist selects a model via DetermineModel.

9. The physicist selects 1 set of solar event times and positions via SelectDataset to enter as input parameters into a Solar-STP model.

10. The model processes the data via NegotiateAccessToJob.

11. The modelled data is returned to the astronomer and stored on MySpace via MySpacePublishDerivedData.

12. The physicist now searches for STP event catalogues via PerformRegistrySearch.

13. A list of STP event catalogues, such as Cluster Identified Scientific Event Catalogue, is returned.

14. The physicist performs a complex query, searching all solar event catalogues for events matching the STP event times and positions returned by the Solar-STP model via ComplexQuery.

15. All matching STP events are returned to the astronomer and stored on MySpace via MySpaceStoreResults.

Sequence Diagram

• Revised sequence diagram produced using Together:
  

UseCases:

These use cases are the ones that will be needed to deliver this case.

1. AuthenticateIdentity
2. PerformRegistrySearch
3. NegotiateAccessToResource
   • AuthenticateIdentity
   • DetermineAuthority
4. PerformCatalogueSearch
5. SelectCatalogue
6. MySpaceStoreResults
   • NegotiateAccessToResource
     • AuthenticateIdentity
     • DetermineAuthority
7. DetermineModel
   • DetermineProgram
     • AccessLibraryFunction
       • NegotiateAccessToResource
         • AuthenticateIdentity
         • DetermineAuthority
     • AccessWebService
       • NegotiateAccessToResource
         • AuthenticateIdentity
         • DetermineAuthority
     • UploadUserCode
       • NegotiateAccessToResource
         • AuthenticateIdentity
         • DetermineAuthority
       • MySpaceStoreResults
         • NegotiateAccessToResource
           • AuthenticateIdentity
           • DetermineAuthority
     • NegotiateAccessToJob
   • NegotiateAccessToJob
8. MySpacePublishDerivedData
9. ComplexQuery

Comments:
Chris Perry: When mapping back from STP events to Solar observations the time scales are dependent on the phenomena/measurement. In the case of CMEs propagation time is several days and highly variable dependent on the corresponding solar wind velocity (which may change by a factor of 5 between different events). Ideally you would like to take the measured solar wind velocity for an event and use this to calculate a propagation time. This maybe a requirement on the STP event catalogue rather than directly on AstroGrid but you will not be able to satisfy the science goal without this additional information.