ATCA VO information

From: Anita Richards <amsr-at-jb.man.ac.uk>
Date: Fri, 6 Jun 2003 12:47:06 +0100 (BST)

Completed by Peter Lamb

  1. Name and nature of observatory and/or facility

ATNF (ATCA radio interferometer)

2. Current archive status and description: a) How are data stored?

Observation data in RPFITS files; metadata in Oracle database.

b) How are data catalogued?

Oracle database that provides references to the data file names.

c) do you provide information about sources (as distinct from about

    observations) e.g. calibrator lists, target properties, and if so     is this:
    i) catalogued information?
   ii) plots?

Not yet, but we intend to. A catalog of sources, names, position and parameters is available but not yet online (it should be online). The archive contains all observed data including calibration data, but the metadata differentiating observations from flux (primary) and phase (secondary) calibrators is patchy at best.

3. What can be accessed on-line?

All recorded observation data from the Australia Telescope Compact Array from 1990-06-03 to 2003-02-15.

4. Who can access it?

Currently accessible only to queries from within csiro.au. Intention is to allow access to any registered user. The archive will contain non-public data; access policies are currently being defined by data owner; assess to non-public data will only be available to authorised registered users; user groups for non-public data access are foreseen.

5. What are the methods of access?

Currently search and download via HTTP/HTTPS protocols. Search results can be returned as HTML or VOTable. Results contain HTTPS links to data files. Search by HTML post method.

6. What search parameters are available?

Instrument name (currently only ATCA - Australia Telescope Compact Array)
ATNF project code
Observation date range
Observer ID
Source name (as recorded in RPFITS metadata, not a spatial lookup) Cone search on pointing centre (RA, DEC, window: hms, dms, arcmin)

7. What is your Archive Policy?

Not yet fully determined. We intend to add regular updates from ATCA, but mechanisms & frequency not yet decided. We intend to keep the "archive everything" policy.

8. What software do you use?

Native file system for data storage; Oracle for metadata Apache & Tomcat web servers
MIRIAD and AIPS++ for astronomical data processing

9. What software do users need, and can you provide it?

Link page under development

10.What format(s) are your data in (or can be translated into)?

RPFITS native. Can translate via MIRIAD or AIPS++ to FITS.

11.Do you use pipelines?

Currently have experimental imaging/source extraction pipeline using MIRIAD. 12.How far are data normally reduced before being supplied to the

    user?

Currently only visibility data is available. Plans are to make online reduction to (at least) intensity maps available, and access to extracted sources. Imaging used for source extraction will be saved and be available to for users to view (what did the image look like that this source was extracted from? access to a fast database of intensity images)

13.Are these stages:
a) documented?

MIRIAD records processing steps and parameters

b) reversible?

Only by obtaining original visibility data.

14.Can data be processed remotely?

Not yet. Online processing is planned.

15.What Virtual Observatory projects (if any) are you involved in?

Archive is an Aus-VO project. Active in the Data Modelling group in IVOA.

16.Do you use explicitly any interoperability tools, e.g. data models,

    UCDs, VOTable?

Current and intended data model under development.

17.Do you publish any data via existing VO-like facilities e.g. CDS,

    MAST? No

18.Making data acess easier for a wider range of astronomers - what are

    your views on whether/how these suggestions should be impliments: a) Using a VO interface to radio observatories/data centres to run

    hidden software to provide required image, light curve,     visibilities etc.?

See above

b) Supplying information about hidden processing (software, versions,

    parameterisation, etc)?

Preserve MIRIAD HISTORY in images; make available through metadata interface.

c) Standardising the software in use at radio observatories/ data

    centres?
d) Standardising the format of data products?

Standards are good. We should use as many as possible :-)

19.What do you think astronomers want from your data?

20.What are your plans for archive development or any other relevant

    suggestions?

Project description and other project documentation available online.

peter.lamb-at-csiro.au

Group Leader, Grid Computing
CSIRO Mathematical and Information Sciences PO Box 664 Tel: +61 2 6216 7047
Canberra ACT 2601, Australia Fax: +61 2 6216 7111 Received on 2003-06-10Z13:09:16