EUROVO FC

AVO
SWG
Management
Science
Standards
Technology
Reports&Minutes
Forum
Events
Contacts
Help

EGG

Main

Know

Test

TWiki

Applications and Services for AVO Demo 2005

About

Below is a list of applications and free space to insert information about

• general applicability/restrictions
• configuration parameters
• system requirements
• misc.

The named persons are requested to review applications and collect relevant information.

PaulHarrison will support the technical integration and hence should be contacted to clarify questions about what exactly is needed if unclear.

1. Catalogue generation

1.1 CDS Xmatch tool (doc of plug-in version) / SebastienDerriere

The cross-match tool exists in 2 versions:

• a built-in function in the AVO prototype (Aladin)
• a remote HTTP service

The built-in Xmatch uses a function: xMatch(plane1, plane2, coo1, coo2, thresholds, method) parameters are:

• the 2 planes that will be x-matched
• coo1[2], coo2[2] arrays contaning indices of columns with position (e.g. coo1={3,4} if RA and DEC are in columns 3 and 4 for plane1)
• thresholds[2] contains the 2 extreme search radii in arcsec
• method is one of {bestMatch=1, allMatch=2, noMatch=4}, or a combination (or'ed) of these (e.g. bestMatch and noMatch => 5)

It creates a new catalogue plane as a result, with an extra column indicating the distance between the associated sources.

The remote service is a servlet on the cdsws machine (mirrored at CfA). It can be invoked by HTTP POST method:

1.2 VizieR Proxy / MartinHill

The VizieR Proxy allows to access VizieR catalogs within a workflow.

It is a CEA web service that converts an ADQL query to the VizieR equivalent and triggers its execution. The results are returned from VizieR to the proxy which stores them in MySpace and communicates to the Job Execution System (JES) that it has completed.

VizieR contact persons: SebastienDerriere, FrancoisOchsenbein

Note: The question of how to distinguish VizieR resources that are accessible via the VizieR Proxy from those that are not and from non VizieR resources is part of Task 4.4 population of registry .

Checking whether VizieR data has been registered can be done through the portal as part of selecting the table, or on the hydra registry on the keyword search page. The service is registered on hydra as DSA_Vizier/ceaService etc.

Querying:
The quickest way to do this is directly on the PAL-VizieR proxy site at:

http://grendel12.roe.ac.uk:8080/pal-vizier/adqlSqlForm.jsp

by cut and pasting something like this:

SELECT * FROM ELAIS WHERE CIRCLE('J2000',7.5,-42,1)

and adding constraints on Jmag, etc, eg:

SELECT * FROM ELAIS WHERE CIRCLE('J2000',7.5,-42,1) AND (ELAIS.Jmag > 5)

However you can't do nested boolean constraints (such as x AND (y OR (z AND a)) ) because of the limitations of the Vizier ASU query format as far as I understand it. Also, substitute whatever you like for ELAIS, eg table name, or other catalogue.

2. Spectral Synthesis Codes

2.1 Pegase / MarkAllen

• PegaseTests.txt

The example output files generated in these tests are available in the following tar file:

• PegaseTestOutputs.tar.gz

Note that there is a online version of PEGASE version 1 which uses forms to input the parameters, and outputs FITS files. This version does not have the full flexibility of the command line version, but is more user friendly.

Online PEGASE version 1

• Tests of comparing SEDs from the ELAIS final merged band

2.2 Starburst99 / NicholasWalton

Starburst99 is a web based software and data package designed to model spectrophotometric and related properties of star-forming galaxies.

Starburst99 can be compared to PEGASE above. Starburst99 uses Geneva group tracks, whilst PEGASE uses those from Padova. Starburst version 4.0 allows the use of fully line-blanketed WR model atmospheres and non-LTE O-star atmospheres (Smith, Norris, & Crowther, 2002, MNRAS, 337, 1309).

As for PEGASE, Starburst99 follows theoretical stellar tracks from the zero-age main sequence (ZAMS) to their final stages. These stages include the asymptotic giant branch (AGB) and post-AGB phases for intermediate-mass stars.

A description of the format of the input and output files is given at http://www.stsci.edu/science/starburst99/docs/code.html

The attached README from the version 4.0 code distribution, gives details on the code, inputs, outputs, directory structure and so forth.

A more detailed run through of a starburst99 model is given at AvoDemo2005StarburstTest

2.3 Galaxev / PieroRosati

• tar file with source code
• example input and output files
• VOTable conversion utility Galevot

3. Spectral plotting, SED visualisation

3.1 Specview / MarkusDolensky

3.2 VOSpec / PedroOsuna

• VOSpec_AVO.pdf: VOSpec: ESAC Tool for VO Spectra Handling
• Java tool
• Preparing VOSpec input

Optional Tools

Photometric redshift determination

• Hyperz
• Bpz
• ANNz

Principal Component Analysis (PCA) - to determine galaxy redshift

• Madgwick, D. et al, 2002
• Folkes, S, et al, 1999

Catalog Creation

• SWarp
• SExtractor

Model/Data visualisation

• Mirage
• see also VO enabled Mirage