SVO - ESAVO Use case: Comparison of evolutionary synthesis models

Description

A user wants to compare the results given by different grids of evolutionary synthesis models (produced by different developers/groups) with observational data.

primary actor

Evolutionary synthesis model user.

End result:

Plot by VOSpec of results of theoretical and real data.

Other actors:

- Evolutionary synthesis model server

- VO Registry

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid of models (not known a priori).

Flow of events

All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.

1. User logins in VOSpec and makes a query by object
2. Among the SSA and theoretical services provided by VOSpec the user selects those of interest.
3. In response to the "format=metadata" query, the selected theoretical services send a VOTable to VOSpec with the parameter space (and the associated valid values) that defines the grid of models.This information is displayed by VOSpec
4. The user selects the desired parameters/range of values, and VOSpec send them back to the theoretical service.
5. The service returns a VOTable with the results to be displayed by VOSpec. Depending on the server, the results can be obtained from a pre-computed grid of models or on-the-fly.
6. Models and observations are displayed. Using VOSpec both datasets can be normalized to a common scale.

Post-condition

1. Results provided in VOTable format.

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?

"The service returns a VOTable with the results..." Consider returning this table to a VOStore. This lets the derivation of the table run asynchronously from VOSpec, which may be useful if the model has to be recomputed to produce the result. Note that VOspec and similar applications can get to the storage via the AstroGrid Client Runtime.

-- GuyRixon - 04 Oct 2005

SVO - ESAVO Use case: Comparison of evolutionary synthesis models

Description

A user wants to compare the results given by different grids of evolutionary synthesis models (produced by different developers/groups) with observational data.

primary actor

Evolutionary synthesis model user.

End result:

Plot by VOSpec of results of theoretical and real data.

Other actors:

- Evolutionary synthesis model server

- VO Registry

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid of models (not known a priori).

Flow of events

All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.

1. User logins in VOSpec and makes a query by object
2. Among the SSA and theoretical services provided by VOSpec the user selects those of interest.
3. In response to the "format=metadata" query, the selected theoretical services send a VOTable to VOSpec with the parameter space (and the associated valid values) that defines the grid of models.This information is displayed by VOSpec
4. The user selects the desired parameters/range of values, and VOSpec send them back to the theoretical service.
5. The service returns a VOTable with the results to be displayed by VOSpec. Depending on the server, the results can be obtained from a pre-computed grid of models or on-the-fly.
6. Models and observations are displayed. Using VOSpec both datasets can be normalized to a common scale.

Post-condition

1. Results provided in VOTable format.

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?

"The service returns a VOTable with the results..." Consider returning this table to a VOStore. This lets the derivation of the table run asynchronously from VOSpec, which may be useful if the model has to be recomputed to produce the result. Note that VOspec and similar applications can get to the storage via the AstroGrid Client Runtime.

-- GuyRixon - 04 Oct 2005

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Description

A user wants to compare the results given by different grids of evolutionary synthesis models (produced by different developers/groups) with observational data.

primary actor

Evolutionary synthesis model user.

End result:

Plot by VOSpec of results of theoretical and real data.

Other actors:

- Evolutionary synthesis model server

- VO Registry

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid of models (not known a priori).

Flow of events

All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.

1. User logins in VOSpec and makes a query by object
2. Among the SSA and theoretical services provided by VOSpec the user selects those of interest.
3. In response to the "format=metadata" query, the selected theoretical services send a VOTable to VOSpec with the parameter space (and the associated valid values) that defines the grid of models.This information is displayed by VOSpec
4. The user selects the desired parameters/range of values, and VOSpec send them back to the theoretical service.
5. The service returns a VOTable with the results to be displayed by VOSpec. Depending on the server, the results can be obtained from a pre-computed grid of models or on-the-fly.
6. Models and observations are displayed. Using VOSpec both datasets can be normalized to a common scale.

Post-condition

1. Results provided in VOTable format.

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?

"The service returns a VOTable with the results..." Consider returning this table to a VOStore. This lets the derivation of the table run asynchronously from VOSpec, which may be useful if the model has to be recomputed to produce the result. Note that VOspec and similar applications can get to the storage via the AstroGrid Client Runtime.

-- GuyRixon - 04 Oct 2005

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Mexican VO - SVO - ESAVO Use case: Comparison of evolutionary synthesis models

Description

A user wants to compare the results given by different grids of evolutionary synthesis models (produced by different developers/groups) with observational data.

primary actor

Evolutionary synthesis model user.

End result:

Plot by VOSpec of results of theoretical and real data.

Other actors:

- Evolutionary synthesis model server

- VO Registry

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid of models (not known a priori).

Flow of events

All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.

1. User logins in VOSpec and makes a query by object
2. Among the SSA and theoretical services provided by VOSpec the user selects those of interest.
3. In response to the "format=metadata" query, the selected theoretical services send a VOTable to VOSpec with the parameter space (and the associated valid values) that defines the grid of models.This information is displayed by VOSpec
4. The user selects the desired parameters/range of values, and VOSpec send them back to the theoretical service.
5. The service returns a VOTable with the results to be displayed by VOSpec. Depending on the server, the results can be obtained from a pre-computed grid of models or on-the-fly.
6. Models and observations are displayed. Using VOSpec both datasets can be normalized to a common scale.

Post-condition

1. Results provided in VOTable format.

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Description

A user wants to compare the results given by different grids of evolutionary synthesis models (produced by different developers/groups) with observational data.

primary actor

Evolutionary synthesis model user.

End result:

Plot by VOSpec of results of theoretical and real data.

Other actors:

- Evolutionary synthesis model server

- VO Registry

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid of models (not known a priori).

Flow of events

All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.

1. User logins in VOSpec and makes a query by object
2. Among the SSA and theoretical services provided by VOSpec the user selects those of interest.
3. In response to the "format=metadata" query, the selected theoretical services send a VOTable to VOSpec with the parameter space (and the associated valid values) that defines the grid of models.This information is displayed by VOSpec
4. The user selects the desired parameters/range of values, and VOSpec send them back to the theoretical service.
5. The service returns a VOTable with the results to be displayed by VOSpec. Depending on the server, the results can be obtained from a pre-computed grid of models or on-the-fly.
6. Models and observations are displayed. Using VOSpec both datasets can be normalized to a common scale.

Post-condition

1. Results provided in VOTable format.

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

SVO - ESAVO Use case: Comparison of evolutionary synthesis models

Description

A user wants to compare the results given by different grids of evolutionary synthesis models (produced by different developers/groups) with observational data.

primary actor

End result:

Plot by VOSpec of results of theoretical and real data.

Other actors:

- Evolutionary synthesis model server

- VO Registry

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid of models (not known a priori).

Flow of events

All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.

1. The service returns a VOTable with the results to be displayed by VOSpec. Depending on the server, the results can be obtained from a pre-computed grid of models or on-the-fly.

Post-condition

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Description

primary actor

End result:

Other actors:

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option)

Flow of events

All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.

1. User logins in VOSpec and selects the corresponding service.
2. In response to the "format=metadata" query, the service sends a VOTable to VOSpec with the parameter space (and the associated valid values) that defines the grid of models.
3. The user selects the desired parameters/values, and VOSpec send them back to the service.
4. The service returns a VOTable with the results to be displayed by VOSpec. Depending on the server, the results can be obtained from a pre-computed grid of models or on-the-fly.

1. The user chooses an spectroscopic observation with VOSpec.
2. Models and observations are plotted and normalized to a common scale.

Post-condition

1. Results provided in VOTable format

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

Description

Case A: A user with deep knowledge of evolutionary synthesis models wants to compare the results given by different grids of models (produced by different developers/groups) for the same set of input parameters.

Case B: A user wants to retrieve an specific evolutionary synthesis model to perform a simple comparison (overplot) with real data.

primary actor

Case B: Evolutionary synthesis model standard user

End result:

Case A: Plot by VOSpec of results obtained from different grids of models with the same input parameters (age and metallicity).

Case B: Plot by VOSpec of results of theoretical and real data.

Other actors:

Case A: Evolutionary synthesis model server

Case B: Evolutionary synthesis model server, observational data server

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid (not known a priori).

Flow of events

1. User logins in VOSpec and selects the corresponding service.

Post-condition

1. Results provided in VOTable format

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->

UNDER CONSTRUCTION

Use cases: Comparison/use of evolutionary synthesis models

Description

Case A: A user with deep knowledge of evolutionary synthesis models wants to compare the results given by different grids of models (produced by different developers/groups) for the same set of input parameters.

Case B: A user wants to retrieve an specific evolutionary synthesis model to perform a simple comparison (overplot) with real data.

primary actor

Case B: Evolutionary synthesis model standard user

End result:

Case A: Plot by VOSpec of results obtained from different grids of models with the same input parameters (age and metallicity).

Case B: Plot by VOSpec of results of theoretical and real data.

Other actors:

Case A: Evolutionary synthesis model server

Case B: Evolutionary synthesis model server, observational data server

- VOSpec

Pre-conditions

1 Existence of a protocol (e.g. TSAP) that explores (using the "format=metadata" option) the parameter space of the theoretical grid (not known a priori).

Flow of events

Case A:

1. User logins in VOSpec and selects the corresponding service.
2. In response to the "format=metadata" query, the service sends a VOTable to VOSpec with the parameters

1. The user selects the desired parameters, and VOSpec send them back to the

1. The service returns a VOTable with the results to be displayed by VOSpec. Depending on

Case B (includes Case A, plus):

1. The user chooses an observation with VOSpec
2. Models and observations are plotted and normalized to a common scale

Post-condition

1. Results provided in VOTable format

Basic assumptions

Synthesis models mix the results of two types of theoretical results: evolutionary tracks and atmosphere models.

Alternative flows

Open Issues

1. How to evaluate if the resulting model (final product of a mathematical

<-- 

 

 

 Set ALLOWTOPICRENAME = TWikiAdminGroup
 
 
-->