Difference: VOtheorySynthesis (2 vs. 3)

Revision 32005-09-28 - EnriqueSolano

  Back to IVOA Theory: Science Use Cases
Changed:
<
<
>
>

Use case: Comparison/use of evolutionary synthesis models

Deleted:
<
<
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 A: Evolutionary synthesis model expert user

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

Added:
>
>
All the information exchange between the synthesis model server and VOSpec is done using the TSAP protocol.
 Case A:

  1. User logins in VOSpec and selects the corresponding service.
Changed:
<
<
  1. In response to the "format=metadata" query, the service sends a VOTable to VOSpec with the parameters
space that defines the grid of models.
  1. The user selects the desired parameters, and VOSpec send them back to the
>
>
  1. 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.
  2. The user selects the desired parameters/values, and VOSpec send them back to the service.
  3. 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.
Deleted:
<
<
service.
  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.
  Case B (includes Case A, plus):
Changed:
<
<
  1. The user chooses an observation with VOSpec
  2. Models and observations are plotted and normalized to a common scale

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

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

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

Changed:
<
<
  1. How to evaluate if the resulting model (final product of a mathematical
>
>
  1. How to evaluate if the resulting model (final product of a mathematical algorithm) has a physical meaning? Use of cautions, warnings etc...?
Deleted:
<
<
algorithm) has a physical meaning? use of cautions, warnings etc...?
 
Added:
>
>
Originally sent by M. Cerviņo - 27 Sep 2005
Last modified: E. Solano - 28 Sep 2005
 
Please add comments below. This area should be used for refinement of the above document. If you want to ask questions or start a dialogue with the author, please use the theory mailing list.
Deleted:
<
<

 
Changed:
<
<
-- Miguel Cerviņo - 27 Sep 2005
>
>
 


<--  
-->
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback