Feature #591

Investigate how GammaLib can be made VO compliant.

Added by Knödlseder Jürgen over 11 years ago. Updated over 7 years ago.

Status:In ProgressStart date:02/20/2013
Priority:UrgentDue date:03/29/2015
Assigned To:-% Done:

76%

Category:-
Target version:-
Duration: 768

Description

Ultimately, GammaLib should be VO compliant.

It should be possible to access event data through a VO compliant interface. Also observations should be defined in a VO compliant format.

GammaLib results, such as images, spectra, should also be VO compliant. For example, it should be possible to visualize spectra using VOspec.

An investigation should be conducted on how VO compliance can be achieved. An inventory of tools and interfaces is needed, to define what exactly should be implemented.


Recurrence

No recurrence.


Subtasks

Action #780: Display skymap using AladdinClosedLouge Thierry

Action #781: Design SAMP usage in GammaLibClosedKnödlseder Jürgen

Action #1170: Add object to coordinate transformation using VO services...NewLouge Thierry

Action #1229: Design and implement GVOHub classClosedLouge Thierry

Action #1231: Design and implement GVOTable classIn Progress

History

#1 Updated by Knödlseder Jürgen over 11 years ago

  • Description updated (diff)

#2 Updated by Knödlseder Jürgen about 11 years ago

A possible Use Case to start with would be the display of a skymap by Aladdin using the SAMP protocol. Aladdin can be used as a FITS map display tool using the SAMP protocol. Expertise on this topic exists apparently at the CDPP (IRAP).

#4 Updated by Knödlseder Jürgen about 11 years ago

  • Target version set to 00-08-00

#5 Updated by Knödlseder Jürgen about 11 years ago

  • Status changed from New to In Progress

Started to implement VO module.

#6 Updated by Knödlseder Jürgen over 10 years ago

  • Target version deleted (00-08-00)

#7 Updated by Knödlseder Jürgen over 9 years ago

  • Due date set to 06/20/2014

due to changes in a related task

#8 Updated by Knödlseder Jürgen over 9 years ago

  • Due date set to 01/01/2015

due to changes in a related task

#9 Updated by Knödlseder Jürgen over 9 years ago

  • Due date changed from 12/31/2014 to 01/01/2015

due to changes in a related task

#10 Updated by Knödlseder Jürgen over 9 years ago

  • Due date changed from 12/31/2014 to 02/27/2015

due to changes in a related task

#11 Updated by Knödlseder Jürgen over 9 years ago

  • Due date changed from 02/27/2015 to 03/29/2015

due to changes in a related task

Also available in: Atom PDF