Versions Compared

Old Version 14

changes.mady.by.user Brian Kent

Saved on

compared with

New Version Current

changes.mady.by.user Brian Kent

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Project Charter

Long Description

This project deals with the ingest of FITS data cubes, catalogs, and spectra, and providing access to the products from the archive.  For details of the ALFALFA project see the project web page.

...

From the SRDP perspective, the set of all ALFALFA data products is a collection.

Publications

The main catalog paper by Haynes et al. (2018).

The long and continually growing list of ALFALFA publications.

ALFALFA Data Products

1. Spectral Data Cubes, Spectral Weights, Continuum Maps, Continuum Weights

...

    Spectral data cubes:       144 RA pixels  x 144 Decl. pixels  x  1024 frequency channels   x   2 polarizations   (Example spectral line data cube/lustre/aoc/sciops/bkent/grids/1220+27a_spectral.fits)

    Spectral weights:             144 RA pixels  x 144 Decl. pixels  x  1024 frequency channels   x   2 polarizations    (Example spectral line weights - also a cube/lustre/aoc/sciops/bkent/grids/1220+27a_spectralweights.fits)

    Continuum maps:            144 RA pixels  x 144 Decl. pixels  x 2 polarizations   (Example continuum FITS image/lustre/aoc/sciops/bkent/1220+27a_continuum.fits)

    Continuum weights:        144 RA pixels  x 144 Decl. pixels  x 2 polarizations   (Example continuum weights/lustre/aoc/sciops/bkent/1220+27a_continuumweights.fits)

Volume of data (< ~ 10 TB)

Frequency range:  1335 to 1445 MHz (L-band)

...

Each detection has a single FITS file with a binary table extension, containing the X-Y points of the spectrum and associated metadata.  Number: ~30,000 FITS files.  Total volume: ~ 1 Gigabyte.

Archive Access to ALFALFA Data Products

Modalities (up for discussion) for the discovery and filtering of ALFALFA data sets in the Archive.

  1. Any primary project that has an associated ALFALFA "product" (a set of cubes, catalog entry, or spectrum) should show the ALFALFA results as a related product in the project view.  
    • This should be displayed in a similar manner to any Images or other SRDP related products, but clearly show that it is an ALFALFA product.
  2. In the observation view ALFALFA  data cube sets are displayed and filtered with the other EBs stored in the archive.
    •  A column showing that they belong to the ALFALFA collection should be optionally displayed 
    • The user should be able to suppress display of members of the ALFALFA (or any other) collection.
    • No reprocessing capabilities (e.g. optimized imaging) should be provided for data cubes from the ALFALFA collection (the project is COMPLETEDCOMPLETE).
  3. A dedicated "ALFALFA" view of the archive, that enables searches on the ALFALFA specific meta-data columns.
    • A cone search of the RA and Dec fields (as described in the above catalog description) should be supported.
    • Searching on ranges of heliocentric redshift (in the above table) should could be supported.
    • The ALFALFA view should also provide links to the ALFALFA project, and publications explaining the processing and data products (ALFALFA publications).

End user manipulation

The expectation is that a user would search for a position on the sky, or via a galaxy name (NED resolver, etc.).     For instance, if one searches on the position 12h20m00s, +09d00m00s, four data cubes, each with three additional ancillary products, would be returned (16 totals hits, total volume would be ~ 1.6 GB). 

At the most basic level, using AstroPy, we would expect an end user to download a set of ALFALFA files and manipulate them with some simple Python or a Jupyter notebook (Example demo: ReadTheDocs).
This is out of the archive scope, but is useful so that we all know what the data look like.

Stakeholders

Brian Kent, NRAO, Project Sponsor and Technical Expert

...

Martha Haynes, Cornell, ALFALFA PI and Technical Expert

Others?

Prerequisites

The ALFALFA project will provide to NRAO the FITS spectral data cubes and ancillary products, data cube index,  extragalactic catalog, and HI spectra FITS files.

Examples will be provided to the SSA team for comments on header metadata keywords, to ease archive ingestion.

Requirements

Must haves:

  • Ingest of ALFALFA spectral data cubes and for each cube, three ancillary spectral products (spectral weights, continuum maps, continuum weights)
  • Ingest of the ALFALFA extragalactic catalog
  • Ingest of the ALFALFA spectral line profiles
  • Harvest and persistence of relevant generic and collection specific metadata.
  • Ability to filter on Collection in observation view (both: "must be in" and "must not be in" semantics) in Archive Interface
  • Ability to search on position, data cube name.

...

  • Search on frequency range?
  • Search via object name (extragalactic NED resolver)?
  • Search via heliocentric redshift?



Implementation Plan

Risk Assessment

The ALFALFA data represent a low-risk, completed, and mature dataset that will be useful to the astronomical community.  The data are not going to be remade or regridded, and will be ingested into the archive only one time.