Tags:
create new tag
view all tags

Data Centre Implementation Plan

US - Stanford

The SDO archive at Stanford will store level 0 level 3 data from HMI and AIA, including raw satellite data, magnetograms, low resolution images and movies, data cubes, Doppler velocity maps, quicklooks, and other data products. The majority of data products will be kept online for 3 months; selected products will be available online longer.

The SDO data centre at Stanford will make HMI and AIA level 1 3 online data products and quicklooks available to grid users with Astrogrid PAL software. Metadata for these products, including location information, will be stored in a relational database (PostgreSQL, MySQL, or Oracle). Data products will be available as compressed images, FITS files, or VOTable files. Other possible formats include CDF or HDF.

Tasks:

  1. Install PAL at Stanford (currently underway with snapshot release of Astrogrid PAL from January 2005): March June 2006
  2. Write Astrogrid registry entry for SDO PAL using IVOA VODescription schema. Metadata from the Stanford relational database will be used to populated table column names, units, and spatial / temporal / spectral coverage. Upload finished entry to registry. (Current Astrogrid status: 1 VODescription table required per database table. This is subject to change.): March June 2006
  3. Install CEA at Stanford and use to wrap data transfer tool: March June 2006
  4. Write Astrogrid registry entry for SDO CEA tool: March June 2006

Optional Tasks:

  1. Install Astrogrid MySpace instance at Stanford allocates storage space for VO user data storage: June July 2006
  2. Wrap SDO pipeline algorithms as CEA tools: June July 2006

People Involved:

UK MSSL or RAL

The solar algorithms written by the eSDO project will produce further high level data products and quicklooks external to the JSOC pipeline and archive. There are several issues currently on the fly:

  • will these products be generated automatically on a daily basis or on the fly for each user?
  • should these products be stored in a data centre regardless of how they are generated?
  • how long should these products be stored in a data centre should eSDO follow the 3 month limit of online products used by JSOC?
  • if a user attempts to execute an eSDO algorithm to produce a data product that has already been produced using the same input constraints, should the stored data product be returned to the user rather than generating the product again?
  • should eSDO quicklook products be stored for 3 months, for a longer but finite period, or indefinitely?

Tasks:

  1. Install database (relational or XML) to hold metadata about eSDO data products and quicklooks.
  2. Install PAL at MSSL or RAL (currently underway with snapshot release of Astrogrid PAL from January 2005): July-August 2006
  3. Write Astrogrid registry entry for eSDO PAL using IVOA VODescription schema. Use metadata stored in database to populate table column headers and spatial / temporal / spectral coverage. Upload finished entry to registry. July-August 2006
  4. Install CEA at MSSL or RAL and use to wrap data transfer tool: July-August 2006
  5. Write Astrogrid registry entry for SDO CEA tool: July - August 2006

People involved:

-- ElizabethAuden - 17 Feb 2005

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | More topic actions
Topic revision: r1 - 2005-02-17 - ElizabethAuden
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback