HELIO Glossary
 
This document gives outline details s of the Services developed by HELIO and well as definition of other common terms.

Community Interaction Service (CIS)

While most HELIO services can be used without user authentication, there are advantages if the system knows who the user is – they are able to save preferences and return to long-running processes.

The CIS allows the user to authenticate and for the services that require user authorisation – the HPS and HSS – it passes the necessary tokens to the service

Context Service (CXS)

The CXS generates plots that are needed by different user interfaces within HELIO including the HELIO Front End (HFE) and the IDL/SolarSoft access code.

Coordinate Transformation Service (CTS)

While we try to condition pointing information as it is ingested into the HEC, not all data that must be used by HELIO is in the correct coordinate system. The purpose of the CTS is to do the necessary translation between different coordinate systems.

This service has still to be implemented.

Data Provider Access Service (DPAS)

The DPAS is used to retrieve the required data sets. The Service know how the data are stored and how to access them – this id defined in the Provider Access Table (PAT).

Heliophysics Event Catalogue (HEC)

The HEC contains event lists from various sources and domains; so far more than 40 different events lists have been added including numerous flare and CME catalogues.

Heliophysics Feature Catalogue (HFC)

The HFC contains lists that describe features detected in images at various wavelengths. The features currently included are Sunspots, Active Regions, Filaments, Coronal Holes and Type II and III events; generally the coverage is from 1996 to the current date.

HELIO Monitoring Service (HMS)

The monitoring service continuously checks on the status of the services listed in the HRS. Is purpose is to provide the Registry with information of which services are currently available.

HELIO Registry Service (HRS)

The Registry should be the first point of call for external services, it contains information about all the Services that have been created by HELIO or that HELIO knows about.

HELIO Processing Service (HPS)

The HPS provides access to high-performance processing capabilities in IDL, Java, etc. Currently only pre-canned routines can be run but eventually the user will be able to upload their own code.

In order to use this service the user must be authenticated and authorised.

HELIO Storage Service (HSS)

The HSS provides storage for data and results and for use in conjunction with the HPS.

In order to use this service the user must be authenticated and authorised.

Service Interface

xxx REST, SOAP,

Instrument Capabilities Service (ICS)

The ICS is a relational database that describes the capabilities of all the instruments that could be included in HELIO. This is at a very basic level, sufficient to allow searches based on type of observation, observing domains, common terms, etc.

Instrument Location Service (ILS)

The ILS is a relational database that holds information about the location of the planets and major heliospheric missions. We are currently in the process of adding details of selected missions that are in close planetary environments.

Observation Coverage Table (OCT)

The OCT is used to optimise a search for observations.

The table describes, at some granularity, whether an instrument is observing during a particular time interval. A single record covering the entire time interval that an instrument was operating is the coarsest resolution, but records could indicate at a resolution of a day, orbit or other suitable interval.

Provider Access Table (PAT)

The PAT defines where data from an observatory/instrument can be found and how they should be accessed. The PAT is used by the DPAS to determine how to fulfil a data request.

There can be multiple records in the PAT for an instrument if there are multiple sources of that particular data set; the protocol used for access may differ

Unified Observing Catalogue (UOC)

The UOC serves two purposes within the HELIO infrastructure:
  • It contains information related to instruments that are difficult to access for one reason or another. Currently this type of record includes i) planetary data from NASA's Planetary Data System (PDS) and ESA's Planetary Science Archive (PSA) and ii) h-alpha data in the Global H-Alpha Network (GHAN).
  • It contains records giving details of the modes of the pointed remote-sensing solar instruments – i.e. those with a limited field-of-view.

VOTable Format

The preferred output format for most if the HELIO Services is VOTable, a format define by the International Virtual Observatory Alliance (IVOA). This format has the advantage that the parameters can be unambiguously defined in the field definition statements using UCDs and utypes making is easier for other projects to use HELIO data products.

For more information see "VOTable Format Specification" in the IVOA Document Store.

Web Service

xxx