LBT Data Archive: PARTNER keyword definition

The LBT data archive needs some reliably-specified information in the image headers to know how to keep track of the data and where to send it amongst the distributed archive machines in the US, Germany, and Italy. These FITS header keywords include:

PARTNER - Specified the partner or partners for whom the data were taken
OBSERVER - Name of the responsible person at the telescope when data were taken
DATATYPE - Identifies data as either science data (OBJECT, or SCIENCE) or calibration (DARK, BIAS, etc.)
PI_NAME - Identifies the project principle investigator (arbitrary user-defined string)
PROPID - String identifying the project to the PI (arbitrary user-defined string)
OBJECT - Identifies the name of the source being observed (arbitrary user-defined string)

PARTNER

The PARTNER Keyword can assume any of the following single string values:

Primary partners: OSURC, LBTB, INAF, AZ

Telescope Commissioning and Technical Obs: LBTO

Instrument Engineering and Commissioning: COMMISSIONING (the instrument is specified in the INSTRUME keyword)

Unspecified default: NOPARTNER

Science Demonstration Time: LBTSDT

Implementation of the PARTNER string must follow these rules:

  • The default is NOPARTNER
  • Can be set in the UI and scripting, with script values overriding the UI setting
  • ALL CAPS in the image headers, but optionally accept any capitalization in UI/scripts
  • Accept comma-separated (no spaces) multiple partners, e.g.: OSURC,INAF
  • Data labeled NOPARTNER is held undistributed until properly identified

A complete set of the data taken at the LBT is kept in two locations, at the telescope and in Tucson, and on three machines, two at the LBT and one in Tucson. The PARTNER keyword will be used to determine distribution of the data to the archive mirrors in Germany and Italy as:
  • Germany mirror: receives all LBTB and LBTSDT data, plus COMMISSIONING data from Lucifer and Linc, and all calibration data from all partner observing blocks.
  • Italy mirror: receives all INAF and LBTSDT data, COMMISSIONING data from LBC, and all calibration data from all partner observing blocks.

OBSERVER

DATATYPE - Identifies data as either science data (OBJECT, or SCIENCE) or calibration (DARK, BIAS, etc.)

PI_NAME - Identifies the project principle investigator (arbitrary user-defined string)

PROPID - String identifying the project to the PI (arbitrary user-defined string)

OBJECT - Identifies the name of the source being observed (arbitrary user-defined string)

-- DavidThompson - 18 Mar 2010
Topic revision: r1 - 18 Mar 2010, DavidThompson
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback