The ASDC SED Builder Milvia Capalbi (INAF-ASDC) in collaboration with Paolo Giommi (ASI-ASDC), Giulia Stratta (INAF-ASDC), Roberto Primavera (ElsagDatamat)

The ASDC SED BuilderThe ASDC SED Builder

Milvia Capalbi (INAF-ASDC)

in collaboration withPaolo Giommi (ASI-ASDC), Giulia Stratta (INAF-ASDC),

Roberto Primavera (ElsagDatamat)with some inputs from other scientists @ASDC

http://www.asdc.asi.it

SED Builder v1.3

WEB based application available at :http://tools.asdc.asi.it/SED/

•MySQL database system•Java code•Query to ASDC catalogs and external catalogs/services•Possibility to upload user data•Manage private catalogs – login authentication, users can share own data with a predefined group

In the following, I will show the main functionalities of the tool and the steps to make it VO compliant.

Building a SED • Input name or RA/Dec and search

radius in the query form• Choose the catalogs in a set covering the energy spectrum from radio to gamma ray• Click on ‘Load Data’ button

Choose the catalogsRadio catalogsKUEHR

PKSCAT90

DIXON

GB6

SUMSS

NVSS

FIRST

VLSS

CRATES

PMN

WENSS

NORTH20CM (flux 20 cm)

NORTH20CM (flux 6 cm)

NORTH20CM (flux 80 cm)

WMAP5 (Freq. 23e9)

WMAP5 (Freq. 33e9)

WMAP5 (Freq. 41e9)

WMAP5 (Freq. 61e9)

WMAP5 (Freq. 94e9)

Infrared catalogs

AKARIPSC

AKARIBSB

X-Ray catalogs

IPCSLEW

IPC

RASS

WGACAT2

WFCCAT

XRTDEEP

TWOXMMICAT

Gamma catalogs

EGRET3

BAT39MCAT (15-30keV)

BAT39MCAT (14-50keV)

Fermi1FGL (200 Mev)

Fermi1FGL (600 Mev)

Fermi1FGL (2Gev)

Fermi1FGL (6Gev)

Fermi1FGL (60Gev)

IBISSG4CAT (20-40 keV)

IBISSG4CAT (40-100 eV)

AGILE Grid

External services access

NED

2Mass

SDSS7

USNOB1

USNO A2.0

Plot data and look at data tables

Overlay instrument sensitivitySensitivity of instruments collecting data from space and from ground (some Cherenkov telescopes) can be added to the plot.

Fitting dataData can be fit with a polynomial function (more functions to be added soon)

Draw a Model An SSC model, analytical or numerical, can be added to the plot (computed with

model parameters input by the user). Different models can be added and combined.

Luminosity scale

Y scale can be changed from Flux to Luminosity and frequencies from observed to rest frame (Redshift to be provided).

Adding Templates

Templates (QSO or a giant elliptical galaxy spectrum) can be added to the plot

Plot options• The marker type, color and size for

each catalog can be chosen by the user

• Change axis interval• Export data in an ascii file• Save image in PNG format• Background color can be changed• and others……….

Time filtering of data (still in devel area)

Making ASDC-SED VO compliant

Planned steps:

• Save data as VOTable

• Change query to DB: access of data via VO protocols instead of direct SQL access in our database

• Query the registry

– Identify data useful to build a SED – via e.g. TAP

– Get the necessary info to apply specific operations on data, when needed (*)

• Communicate with other VO tools using the SAMP protocol

• In addition to the WebApp: develop a stand-alone tool (study phase)

First steps will be implemented by the end of the spring

Making ASDC-SED VO compliant(*)

Currently

• some of the catalogs we use (mainly X-ray catalogs included in our database) don’t contain flux information but count rates

• we calculate the flux density using information on instrument response and assuming a spectral model (and we correct for the galactic absorption)

In the VO environment• Querying the VO registry, we should get the necessary information to

calculate the flux density with instrument-specific functions (we should support more missions/instruments)

Further improvement• Allow the user to specify an energy index (e.g. to model the

spectrum used to determine the flux)

Summary

Current status

• current functionality of SED Builder shown

• the tool uses some catalogs containing instrument measurements NOT in physical units

• the tool is used by some instrument teams (e.g. AGILE, Fermi, Swift-XRT) since we manage some password-protected catalogs

Future

• project to make the tool VO compliant

• we would like to find the best strategy to proceed and interoperate with other VO tools

THANK YOU