The integration of the data from Telescope ROA Montsec to the - - PowerPoint PPT Presentation

▶
the integration of the data from telescope
SMART_READER_LITE
LIVE PREVIEW

The integration of the data from Telescope ROA Montsec to the - - PowerPoint PPT Presentation

Nov 29, 2023 417 likes •1.04k views

The integration of the data from Telescope Fabra The integration of the data from Telescope ROA Montsec to the Virtual Observatory Fabra ROA Montsec to the Virtual Observatory Data centre overview Type of data to be published in Octavi

slide-1
SLIDE 1

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

The integration of the data from Telescope Fabra ROA Montsec to the Virtual Observatory

Octavi Fors1,2, Guillem Pérez3 & rest of TFRM team1,2,4

1Departament d’Astronomia i Meteorologia, Universitat de Barcelona 2Observatori Fabra 3Escola Tècnica Superior d’Enginyeria Informàtica, Universitat Autònoma

de Barcelona

4Real Observatorio de la Armada

EuroVO CoSADIE, Heidelberg 10-11 Jun 2013

slide-2
SLIDE 2

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Index

Data centre overview Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

slide-3
SLIDE 3

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Index

Data centre overview Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

slide-4
SLIDE 4

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Index

Data centre overview Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

slide-5
SLIDE 5

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Index

Data centre overview Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

slide-6
SLIDE 6

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Index

Data centre overview Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

slide-7
SLIDE 7

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Index

Data centre overview Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

slide-8
SLIDE 8

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Location

Montsec Astronomical Observatory at Pre-Pyrenees range φ = 42.

  • 0516 N, λ = 0.
  • 7293 E, h = 1570 m HMSL
slide-9
SLIDE 9

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Location

Telescope Fabra ROA Montsec (TFRM)

http://www.am.ub.edu/bnc Fors, O. et al. 2013 PASP, 125, 927 (in press, arXiv:1211.5581)

slide-10
SLIDE 10

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description

◮ Optic design: refigured Baker-Nunn Camera. ◮ Focal ratio: f/0.96. ◮ 0.5m three-element corrector cell and 0.78m primary

spherical mirror.

◮ FoV: 4.

  • 4x4.
  • 4.

◮ Pixel scale: 3.9′′. ◮ Spider vanes and focus system with ±10µm or better

focus repeatability.

slide-11
SLIDE 11

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description

Layout of the corrected Baker-Nunn Camera design.

slide-12
SLIDE 12

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description

Design and manufacture of spider vanes and CCD focus system.

slide-13
SLIDE 13

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description

Huge 4.

  • 4x4.
  • 4 FoV with outstanding image quality through all the CCD.
slide-14
SLIDE 14

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description: observational programs

◮ TFRM-PSES: TFRM-Preselected Super-Earths Survey. ◮ Optical asset for Space Situational Awareness/Space

Surveillance and Tracking (SSA/SST) of GEO ring space debris (in collaboration to ESA and ISON).

◮ NEOs survey.

slide-15
SLIDE 15

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description: observational programs

◮ TFRM-PSES: TFRM-Preselected Super-Earths Survey. ◮ Optical asset for Space Situational Awareness/Space

Surveillance and Tracking (SSA/SST) of GEO ring space debris (in collaboration to ESA and ISON).

◮ NEOs survey.

slide-16
SLIDE 16

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description: observational programs

◮ TFRM-PSES: TFRM-Preselected Super-Earths Survey. ◮ Optical asset for Space Situational Awareness/Space

Surveillance and Tracking (SSA/SST) of GEO ring space debris (in collaboration to ESA and ISON).

◮ NEOs survey.

slide-17
SLIDE 17

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description: robotic operations & insfrastructure

◮ TFRM remote and robotic control software based on

INDI protocol.

◮ robotic observations are formalized in XML files. ◮ symmetric 100 Mbps fiber cable Internet connection. ◮ data archive stored at site in a NAS RAID system. ◮ 140,000 useful science images per year (4.5

Tb/year).

◮ plus calibration images, robotic operations exceed

6.5Tb/year.

slide-18
SLIDE 18

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description: robotic operations & insfrastructure

◮ TFRM remote and robotic control software based on

INDI protocol.

◮ robotic observations are formalized in XML files. ◮ symmetric 100 Mbps fiber cable Internet connection. ◮ data archive stored at site in a NAS RAID system. ◮ 140,000 useful science images per year (4.5

Tb/year).

◮ plus calibration images, robotic operations exceed

6.5Tb/year.

slide-19
SLIDE 19

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description: robotic operations & insfrastructure

◮ TFRM remote and robotic control software based on

INDI protocol.

◮ robotic observations are formalized in XML files. ◮ symmetric 100 Mbps fiber cable Internet connection. ◮ data archive stored at site in a NAS RAID system. ◮ 140,000 useful science images per year (4.5

Tb/year).

◮ plus calibration images, robotic operations exceed

6.5Tb/year.

slide-20
SLIDE 20

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

TFRM description: robotic operations & insfrastructure

◮ TFRM remote and robotic control software based on

INDI protocol.

◮ robotic observations are formalized in XML files. ◮ symmetric 100 Mbps fiber cable Internet connection. ◮ data archive stored at site in a NAS RAID system. ◮ 140,000 useful science images per year (4.5

Tb/year).

◮ plus calibration images, robotic operations exceed

6.5Tb/year.

slide-21
SLIDE 21

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Type of data to be published in the VO

◮ Raw Science and calibrated & WCS Science images, via

Simple Image Acces Protocol (SIAP).

◮ TFRM-PSES lightcurves (not started yet) .

Raw Science Calibrated & WCS Science

slide-22
SLIDE 22

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Why to publish data in the VO?

◮ TFRM huge FoV + moderate limiting magnitude +

high temporal cadence of TFRM programs open the window to record a wide range of astrophysical transient phenomena.

◮ For example, in the case of TFRM-PSES, ∼10 new

variables/night are common.

◮ To promote the scientific throughput of the TFRM.

slide-23
SLIDE 23

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Why to publish data in the VO?

◮ TFRM huge FoV + moderate limiting magnitude +

high temporal cadence of TFRM programs open the window to record a wide range of astrophysical transient phenomena.

◮ For example, in the case of TFRM-PSES, ∼10 new

variables/night are common.

◮ To promote the scientific throughput of the TFRM.

slide-24
SLIDE 24

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Why to publish data in the VO?

◮ TFRM huge FoV + moderate limiting magnitude +

high temporal cadence of TFRM programs open the window to record a wide range of astrophysical transient phenomena.

◮ For example, in the case of TFRM-PSES, ∼10 new

variables/night are common.

◮ To promote the scientific throughput of the TFRM.

slide-25
SLIDE 25

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Aims

Principal Implementation of a VO service for the TFRM archive. Secondaries

◮ Applications and Database design. ◮ Service Implementation. ◮ Service Testing. ◮ Integration at in-situ TFRM computers.

slide-26
SLIDE 26

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Aims

Principal Implementation of a VO service for the TFRM archive. Secondaries

◮ Applications and Database design. ◮ Service Implementation. ◮ Service Testing. ◮ Integration at in-situ TFRM computers.

slide-27
SLIDE 27

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Aims

Principal Implementation of a VO service for the TFRM archive. Secondaries

◮ Applications and Database design. ◮ Service Implementation. ◮ Service Testing. ◮ Integration at in-situ TFRM computers.

slide-28
SLIDE 28

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Aims

Principal Implementation of a VO service for the TFRM archive. Secondaries

◮ Applications and Database design. ◮ Service Implementation. ◮ Service Testing. ◮ Integration at in-situ TFRM computers.

slide-29
SLIDE 29

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Aims

Principal Implementation of a VO service for the TFRM archive. Secondaries

◮ Applications and Database design. ◮ Service Implementation. ◮ Service Testing. ◮ Integration at in-situ TFRM computers.

slide-30
SLIDE 30

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Basic solution diagram

slide-31
SLIDE 31

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Developed solution

Archive Database which storages TFRM images and metadata associated needed for an optimal comunication with VO. Ingestor Java application which inserts TFRM images and metadata to archive. Comunicator WebService to comunicate with VO via Simple Image Access Protocol (SIAP).

slide-32
SLIDE 32

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Developed solution

Archive Database which storages TFRM images and metadata associated needed for an optimal comunication with VO. Ingestor Java application which inserts TFRM images and metadata to archive. Comunicator WebService to comunicate with VO via Simple Image Access Protocol (SIAP).

slide-33
SLIDE 33

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Developed solution

Archive Database which storages TFRM images and metadata associated needed for an optimal comunication with VO. Ingestor Java application which inserts TFRM images and metadata to archive. Comunicator WebService to comunicate with VO via Simple Image Access Protocol (SIAP).

slide-34
SLIDE 34

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Archive

Database implemented in PostgreSQL.

slide-35
SLIDE 35

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Archive

◮ PostgreSQL was chosen, among other reasons, because

it includes the module pgSphere, specifically designed for spherical coordinades data types, operators, etc. Hence, it provides uniform access to spherical data.

◮ The database design was the most intensive and decisive

process of the project.

slide-36
SLIDE 36

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Archive

◮ PostgreSQL was chosen, among other reasons, because

it includes the module pgSphere, specifically designed for spherical coordinades data types, operators, etc. Hence, it provides uniform access to spherical data.

◮ The database design was the most intensive and decisive

process of the project.

slide-37
SLIDE 37

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-38
SLIDE 38

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-39
SLIDE 39

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-40
SLIDE 40

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-41
SLIDE 41

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-42
SLIDE 42

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-43
SLIDE 43

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-44
SLIDE 44

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-45
SLIDE 45

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-46
SLIDE 46

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-47
SLIDE 47

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-48
SLIDE 48

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

◮ Java application. ◮ Inserts all images taken by TFRM into the Archive

database.

◮ Automatic daily execution. ◮ Easily configurable. ◮ Internal functionality.

◮ Image processing system.

  • 1. To locate FITS images on the disks array.
  • 2. To extract FITS header information.
  • 3. To process and formalize such FITS header metadata.
  • 4. To insert such metadata into the Archive database.

◮ Testing system. ◮ Errors system. ◮ Critical errors. ◮ Warnings.

slide-49
SLIDE 49

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Ingestor

Java classes diagram of the Ingestor application.

slide-50
SLIDE 50

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

SIAP communicator

  • A. SIAP communicator a two-fold WebService, compliant to

SIAP protocol:

◮ Management of queries for images search and its

response to the client.

  • 1. Query from VO client –> Region of Interest (ROI).
  • 2. TFRM SIAP communicator returns XML file with the

images meeting that query.

◮ SIAP communicator receives specific queries of full

images to be downloaded.

  • 1. Query from VO client –> Identificator of the requested

image.

  • 2. Download of requested image from TFRM SIAP

communicator to the client.

  • B. SIAP communicator must be registered at EURO-VO

Registry Pages (in our case this step is not done yet).

slide-51
SLIDE 51

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

SIAP communicator

  • A. SIAP communicator a two-fold WebService, compliant to

SIAP protocol:

◮ Management of queries for images search and its

response to the client.

  • 1. Query from VO client –> Region of Interest (ROI).
  • 2. TFRM SIAP communicator returns XML file with the

images meeting that query.

◮ SIAP communicator receives specific queries of full

images to be downloaded.

  • 1. Query from VO client –> Identificator of the requested

image.

  • 2. Download of requested image from TFRM SIAP

communicator to the client.

  • B. SIAP communicator must be registered at EURO-VO

Registry Pages (in our case this step is not done yet).

slide-52
SLIDE 52

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

SIAP communicator

  • A. SIAP communicator a two-fold WebService, compliant to

SIAP protocol:

◮ Management of queries for images search and its

response to the client.

  • 1. Query from VO client –> Region of Interest (ROI).
  • 2. TFRM SIAP communicator returns XML file with the

images meeting that query.

◮ SIAP communicator receives specific queries of full

images to be downloaded.

  • 1. Query from VO client –> Identificator of the requested

image.

  • 2. Download of requested image from TFRM SIAP

communicator to the client.

  • B. SIAP communicator must be registered at EURO-VO

Registry Pages (in our case this step is not done yet).

slide-53
SLIDE 53

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

SIAP communicator

  • A. SIAP communicator a two-fold WebService, compliant to

SIAP protocol:

◮ Management of queries for images search and its

response to the client.

  • 1. Query from VO client –> Region of Interest (ROI).
  • 2. TFRM SIAP communicator returns XML file with the

images meeting that query.

◮ SIAP communicator receives specific queries of full

images to be downloaded.

  • 1. Query from VO client –> Identificator of the requested

image.

  • 2. Download of requested image from TFRM SIAP

communicator to the client.

  • B. SIAP communicator must be registered at EURO-VO

Registry Pages (in our case this step is not done yet).

slide-54
SLIDE 54

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Problems faced and help received from VO experts

  • A. Help (∼2 weeks visits and considerable remote support)

was required from SVO team to:

◮ design of a well structured database. ◮ proper understanding of SIAP communicator.

  • B. Future needs:

◮ design and implementation of archive for TFRM-PSES

lightcurves.

◮ advise and support about which protocol (SSAP or

TAP?) should be implemented for the WebService communicator.

◮ advise for use of VOEvents.

slide-55
SLIDE 55

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Problems faced and help received from VO experts

  • A. Help (∼2 weeks visits and considerable remote support)

was required from SVO team to:

◮ design of a well structured database. ◮ proper understanding of SIAP communicator.

  • B. Future needs:

◮ design and implementation of archive for TFRM-PSES

lightcurves.

◮ advise and support about which protocol (SSAP or

TAP?) should be implemented for the WebService communicator.

◮ advise for use of VOEvents.

slide-56
SLIDE 56

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Problems faced and help received from VO experts

  • A. Help (∼2 weeks visits and considerable remote support)

was required from SVO team to:

◮ design of a well structured database. ◮ proper understanding of SIAP communicator.

  • B. Future needs:

◮ design and implementation of archive for TFRM-PSES

lightcurves.

◮ advise and support about which protocol (SSAP or

TAP?) should be implemented for the WebService communicator.

◮ advise for use of VOEvents.

slide-57
SLIDE 57

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Problems faced and help received from VO experts

  • A. Help (∼2 weeks visits and considerable remote support)

was required from SVO team to:

◮ design of a well structured database. ◮ proper understanding of SIAP communicator.

  • B. Future needs:

◮ design and implementation of archive for TFRM-PSES

lightcurves.

◮ advise and support about which protocol (SSAP or

TAP?) should be implemented for the WebService communicator.

◮ advise for use of VOEvents.

slide-58
SLIDE 58

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Conclusions

◮ Nearly complete implementation of a VO archive for the

TFRM is done.

◮ Only installation in TFRM computers remains to be

done.

slide-59
SLIDE 59

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Conclusions

◮ Nearly complete implementation of a VO archive for the

TFRM is done.

◮ Only installation in TFRM computers remains to be

done.

slide-60
SLIDE 60

The integration

  • f the data from

Telescope Fabra ROA Montsec to the Virtual Observatory Data centre

  • verview

Type of data to be published in the VO Why to publish data in the VO? Experience Problems faced and help received from VO experts Conclusions

Questions

Thanks for your time. Questions?