JmmcAsproDataModel < Jmmc/Software

Tags: view all tags

%TOC%

---+ Description

This topic is dedicated to the ASPRO data model describing both the interferometer (stations, instruments, configuration) and an observation using an interferometer configuration with user parameters.<br/>
This model is related to meta data describing how the observation is done and do not describe the data itself. Optical interfometry products (visibilities, phase closures) use the [[http://www.mrao.cam.ac.uk/research/OAS/oi_data/oifits.html][OIFits file format]] but its data model does not describe in depth the interferometer & instrument configurations.


---++ Interferometer

The interferometer is spread in two parts : a description with all possible elements (stations, delay lines, pops, switchyard, instruments ...) and one or more configurations to limit the real possibilities with these elements (instruments with their baselines ...).

---+++ Interferometer description

The interferometer description has the following elements :
   * observatory position
   * list of Telescopes (diameter / adaptiveOptics TBC)
   * list of Stations (relative Position / associated Telescope / fixed offset / horizon profile)
   * list of channels / beams
   * list of delay lines (maximum throw)
   * switchyard (fixed delay per [station / delay line] couple)
   * pops (fixed delay per [station / pop] couple)
   * list of instruments with their modes (wave length range)

---+++ Interferometer configurations

For now, interferometer configurations are really useful to model the VLTI restrictions associated to an ESO Call for Proposal Period like the list of allowed baselines per instrument.

<br/>The other interferometer have only one configuration listing all possible baselines per instrument.
 

---++ Observation

The observation is defined by an the observation setting with :
   * when : date
   * interferometer configuration reference
   * instrument reference + selected baseline (station list)
   * list of targets (ra, dec, magnitudes ...)
   * other parameters : TBC


---++ Data Model Xml Schema

The current data model is written as an XML schema and is provided below :

   Current Version : 8 Dec. 2009 :

   * [[%ATTACHURL%/AsproOIModel.xsd][AsproOIModel.xsd]]: Xml schema for the data model


---+ Sample documents

The following documents illustrate two interferometer description for the VLTI and the CHARA interferometers :

   * [[%ATTACHURL%/VLTI.xml][VLTI.xml]]: VLTI description

   * [[%ATTACHURL%/CHARA.xml][CHARA.xml]]: CHARA description


---+ Observation / Provenance Data models

The IVOA organisation defines several data models related to astronomical observations to be used in the context of the virtual observatory (VO) :
   * The [[http://www.ivoa.net/Documents/Notes/DMObs/DMObs-20050421.pdf][Observation DM]] is a working draft that provides a domain model for observations and so define common items (target, dataset characterization, provenance & curation)
   * The [[http://www.ivoa.net/Documents/latest/CharacterisationDM.html][Characterisation DM]] is an official recommendation that describes the characteristics of the dataset among several axes(spatial, time, spectral)
   * The Provenance DM is a work in progress and information can be found in the following documents (thanks to Juan de Dios Santander Vela) : [[http://www.eso.org/~jdedsant/thesis/radiovo-thesis.pdf][Radio VO Thesis]]

The Aspro Observation can be seen in the VO context with the following parts :
   * Curation : to describe the origin of the observation : DataID (proposal, project, identifier, creator, date of observation)
   * Provenance : interferometer and instrument description / Environment (partially as ASPRO observations are instead simulations)
   * Characterisation : spatial coordinates, time coverage with integration steps ...

The Provenance seems to be the common part where optical interferometer can be described in the VO context.

Here are several diagrams illustrating the Provenance data model :
   * Interferometer case :
<img src="%ATTACHURL%/Provenance_interferometer">
   * Radio (RADAMS) case :
<img src="%ATTACHURL%/Provenance_RADAMS" width="100%" height="100%">


UCD ?


-- Main.LaurentBourges - 08 Dec 2009


---+ First try to get the most VO compliant Aspro datamodel

Here comes two xml files which illustrate the VO model concept for Aspro. This is really simple because it only describes a couple of most important elements that must be associated to data. However it tries to illustrate our concern for reuse in the VO:
   * [[%ATTACHURL%/ProvenanceAspro_1.xml][ProvenanceAspro_1.xml]]: Xml fragment that could describe the configuration associated to data ( without VO effort ;) )

   * [[%ATTACHURL%/ProvenanceAspro_VO.xml][ProvenanceAspro_VO.xml]]: Xml document using a custom Provenance

Attachments

Topic attachments
I	Attachment	History	Action	Size	Date	Who	Comment
xsd	AsproOIModel.xsd	r3 r2 r1	manage	35.0 K	2009-12-08 - 15:17	LaurentBourges	Xml schema for the data model
xml	CHARA.xml	r2 r1	manage	10.9 K	2009-12-08 - 15:17	LaurentBourges	CHARA description
xml	ProvenanceAspro_1.xml	r2 r1	manage	0.6 K	2009-12-10 - 09:35	GuillaumeMella	Xml fragment that could describe the configuration associated to data ( without VO effort
xml	VLTI.xml	r3 r2 r1	manage	231.6 K	2009-12-08 - 15:17	LaurentBourges	VLTI description

Topic revision: r9 - 2009-12-10 - GuillaumeMella