HITOMASTER - Hitomi Master Catalog

Overview

This table records high-level information for the observations obtained with Hitomi and provides access to the data archive. The Hitomi mission was launched on a JAXA H-IIA into low Earth orbit on February 17, 2016, at 5:45 pm JPS from Tanegashima Space Center.

Hitomi was equipped with four different instruments that together cover a wide energy range 0.3-600 keV. The Soft X-ray Spectrometer (SXS), which combined a lightweight Soft X-ray Telescope paired with a X-ray Calorimeter Spectrometer, provided non-dispersive 7-eV resolution in the 0.3-10 keV bandpass with a field of view of about 3 arcminutes. The Soft X-ray Imager (SXI) expanded the field of view with a new generation CCD camera in the energy range of 0.5-12 keV at the focus of the second lightweights Soft X-ray Telescope; the Hard X-ray Imager (HXI, two units) performed sensitive imaging spectroscopy in the 5-80 keV band; the non-imaging Soft Gamma-ray Detector (SGD, two units) extended Hitomi's energy band to 600 keV.

On March 27, 2016, JAXA lost contact with the satellite and, on April 28, announced the cessation of the efforts to restore mission operations.

At that time Hitomi was in check-out phase and had started the calibration observations. Data were collected from six celestial objects (Perseus, N132D, IGR_J16318-4848, RXJ1856.5-3754, G21.5-0.9, and Crab) as well as black sky for a total of about one month of data. The data from these observations were divided into intervals of one day if the observation of a specific pointing was longer that one day. A sequence number was assigned to each observing day and within data from all instruments are included. The day division was mainly to limit the data size within a sequence number.

There are in total 42 sequences, and each record in this database table is dedicated to a single sequence. The early observations do not contain data from all instruments and in cases the object was not always placed at the aim point. This database contains parameters to indicate which instrument was on and if the celestial source was in the field of view. The SXS was the first instrument to turn on and therefore all observations contain SXS data, although the thermal equilibrium was reached after March 4 2016. The second instrument was the SXI followed by the HXIs and, finally, the two SGDs.

Catalog Bibcode

2016SPIE.9905E..14A

Provenance

This database table was generated at the Hitomi Science Data Center processing site (Angelini, L., Terada, Y, et al., 2016, SPIE 9905E, 14) with additions to indicate which instrument was on and if the source was in the FOV. It was ingested into the HEASARC database in June 2017.

Parameters

Name
This is the name of the pointed target. Observations that look at black sky have names related to the type of operations that occurred during that period.

RA
Right Ascension of the pointing position. Note that the pointing position can be different from the target position.

Dec
Declination of the pointing position. Note that the pointing position can be different from the target position.

LII
Galactic Longitude of the pointing position. Note that the pointing position can be different from the target position.

BII
Galactic Latitude of the pointing position. Note that the pointing position can be different from the target position.

Roll_Angle
Roll angle of the observation given in degrees.

Time
The start time of the observation. Note: If the sequence contains the incoming slew, the start time corresponds to the start of the incoming slew.

Stop_Time
The time corresponding to the end of the observation.

ObsID
The unique number to identify an observation/sequence. This is a 9-digit number.

Exposure
The effective total observation exposure, in seconds. This time is calculated using the cleaned event file from the SXS instrument.

SXI_Expo
The effective exposure in seconds on source for the SXI when operating in WINDOW1 mode. This is calculated from GTI of the SXI cleaned events of the WINDOW1 mode. The value is set to 0 if the SXI was not operating.

SXI_Expo2
The effective exposure in seconds on source for the SXI when operating in WINDOW1BURST2. This is calculated from GTI of the SXI cleaned events of the WINDOWBURST2 mode. The value is set to 0 if the SXI was not operating.

HXI1_Expo
The effective exposure in seconds on source for the HXI1. This is calculated from GTI of the HXI1 cleaned events. The value is set to 0 if the HXI1 was not operating.

HXI2_Expo
The effective exposure in seconds on source for the HXI2. This is calculated from GTI of the HXI2 cleaned events. Set to 0 if the HXI2 is not operating.

SGD1_Expo
The effective exposure in seconds on source for the SGD1. The SGD consists of three different detectors. The exposure reported is the sum of the individual detector exposure from the GTI of the event files divided by the number of detectors actually operating. The value is set to 0 if the none of the individual detectors of the SGD1 were operating.

SGD2_Expo
The effective exposure in seconds on source for the SGD2. The SGD consists of three different detectors. The exposure reported is the sum of the individual detector exposure from the GTI of the event files divided by the number of detectors actually operating. The value is set to 0 if the none of the individual detectors of the SGD2 were operating.

SXSifonfov
Two-character code to indicate if the instrument is operating and if the source is in the field of view (FOV). The first character may have the following values: Y=the instrument is on; N= the instrument is off; W=the instrument is in waiting mode. The second character may have the following values: Y=source in the FOV; N=source is not in the FOV; P=the source is partially in the FOV; I=irrelevant given to background observation; and D=valid only for the SXI if the source is in the FOV of the SXI but not at the aim point and therefore not seen by the other instruments.

SXIifonfov
Two-character code to indicate if the instrument is operating and if the source is in the field of view (FOV). The first character may have the following values: Y=the instrument is on; N=the instrument is off; W=the instrument is in waiting mode. The second character may have the following values: Y=source in the FOV; N=source is not in the FOV; P=the source is partially in the FOV; I=irrelevant given to background observation; and D=valid only for the SXI if the source is in the FOV of the SXI but not at the aim point and therefore not seen by the other instruments.

HXI1ifonfov
Two characters code to indicate if the instrument is operating and if the source is in the field of view (FOV). The first character may have the following values: Y=the instrument is on; N= the instrument is off; W=the instrument is in waiting mode. The second character may have the following values: Y=source in the FOV; N=source is not in the FOV; P=the source is partially in the FOV; I=irrelevant given to background observation; and D=valid only for the SXI if the source is in the FOV of the SXI but not at the aim point and therefore not seen by the other instruments.

HXI2ifonfov
Two-character code to indicate if the instrument is operating and if the source is in the field of view (FOV). The first character may have the following values: Y=the instrument is on; N= the instrument is off; W=the instrument is in waiting mode. The second character may have the following values: Y=source in the FOV; N=source is not in the FOV; P=the source is partially in the FOV; I=irrelevant given to background observation; and D=valid only for the SXI if the source is in the FOV of the SXI but not at the aim point and therefore not seen by the other instruments.

SGD1ifonfov
Two-character code to indicate if the instrument is operating and if the source is in the field of view (FOV). The first character may have the following values: Y=the instrument is on; N= the instrument is off; W=the instrument is in waiting mode. The second character may have the following values: Y=source in the FOV; N=source is not in the FOV; P=the source is partially in the FOV; I=irrelevant given to background observation; and D=valid only for the SXI if the source is in the FOV of the SXI but not at the aim point and therefore not seen by the other instruments.

SGD2ifonfov
Two-character code to indicate if the instrument is operating and if the source is in the field of view (FOV). The first character may have the following values: Y=the instrument is on; N= the instrument is off; W=the instrument is in waiting mode. The second character may have the following values: Y=source in the FOV; N=source is not in the FOV; P=the source is partially in the FOV; I=irrelevant given to background observation; and D=valid only for the SXI if the source is in the FOV of the SXI but not at the aim point and therefore not seen by the other instruments.

SXS_Datamode
The name of the SXS datamode for this observation.

SXS_ADR
This flag parameter indicates if an ADR cycle occurred during the observation.

SXS_Fil_Fe55
This flag parameter indicates if the observation was collected with the Fe55 filter on. The following filters are on-board: Beryllium, Neutral Density, Polymide, Open position (no filters), and the Fe55. Only the Fe55 and the Open filters were used. All observations were taken with the gate valve on.

SXS_Fil_Open
This flag parameter indicates if the observation was collected with the Open filter on. The following filters are on-board: Beryllium, Neutral Density, Polymide, Open position (no filters), and the Fe55. Only the Fe55 and the Open filters were used. All observations were taken with the gate valve on.

SXS_Thr
Code to indicate the SXS threshold used within the observation.

SXI_Datamode1
Name of the SXI 1st datamode for this observation.

SXI_Dclass1_Thr
This parameter contains the dataclass and event threshold values encoded as AAAAAAAA-BBBB a BBBB [h]. More than one dataclass and threshold maybe be present within an observation. The first 8 digits (AAAAAAAA) identify the overall setting of the dataclass and second value up to 4 digits (BBBB) indicate the event threshold. The meaning of the 1st 8 digit value is the following: 1st digit always set to 1; 2nd indicates the CCD in use, if 0 all CCDs are in use, if 1 only CCD 1 and 2 are in use, if 2 only CCD 2 and 3 are in use; 3rd digit indicates the datamode, if 0=window1 (full mode), if 1=window2 (1/8 window), if 2=window1burst (full window + burst), 3=window2burst (1/8 window + burst); 4-7 digits indicate the dataclass; the last 8th digit indicates if the area discriminator is off/on for the +/- Z, if 0 is off, if 1 is on. The second value (BBBB) is just the event threshold and corresponds to the first PHA in use. If the aim point has a different threshold compared to the other CCD segments this is indicated by "a BBBB". Finally, the "h", if present, indicates that only half of the CCDs are on.

SXI_Datamode2
Name of the SXI 2nd datamode for this observation.

SXI_Dclass2_Thr
This parameter contains the dataclass and event threshold values encoded as AAAAAAAA-BBBB a BBBB [h]. More than one dataclass and threshold may be present within an observation. The first 8 digits (AAAAAAAA) identify the overall setting of the dataclass and second value up to 4 digits (BBBB) indicate the event threshold. The meaning of the 1st 8-digit value is the following: The 1st digit is always set to 1; the 2nd digit indicates the CCD in use, if 0 all CCDs are in use, if 1 only CCD 1 and 2 are in use, if 2 only CCD 2 and 3 are in use; the 3rd digit indicates the datamode, if 0=window1 (full mode), if 1=window2 (1/8 window), if 2=window1burst (full window + burst), 3=window2burst (1/8 window + burst); 4-7 digits indicate the dataclass; the last 8th digit indicates if the area discriminator is off/on for the +/- Z, if 0 is off, if 1 is on. The second value (BBBB) is just the event threshold and corresponds to the first PHA in use. If the aim point has a different threshold compared to the other CCD segments, this is indicated by "a BBBB". Finally, the "h", if present, indicates that only half of the CCDs are on.

HXI1_Datamode
Name of the HXI1 datamode for this observation.

HXI2_Datamode
Name of the HXI2 datamode for this observation.

SGD1_Datamode
Name of the SGD1 datamode for this observation.

SGD2_Datamode
Name of the SGD2 datamode for this observation.

SGD1_Exp_Cc1
Each SGD has three Compton Camera detectors. This is the exposure time of the Compton Camera 1 in the SGD1.

SGD1_Exp_Cc2
Each SGD has three Compton Camera detectors. This is the exposure time of the Compton Camera 2 in the SGD1.

SGD1_Exp_Cc3
Each SGD has three Compton Camera detectors. This is the exposure time of the Compton Camera 3 in the SGD1.

SGD2_Exp_Cc1
Each SGD has three Compton Camera detectors. This is the exposure time of the Compton Camera 1 in the SGD2.

SGD2_Exp_Cc2
Each SGD has three Compton Camera detectors. This is the exposure time of the Compton Camera 2 in the SGD2.

SGD2_Exp_Cc3
Each SGD has three Compton Camera detectors. This is the exposure time of the Compton Camera 3 in the SGD2.

HXIcode
This is a five-digit number, ABCDE, to identify the type of data present for the HXI. The values for A indicate if the HXI science data are present: A=1 for only HXI1 data, A=2 for only the HXI2 data, A=3 for both HXI1 and HXI2. The values for B indicate if the CAMS data are present: B=1 only CAMS1 data, B=2 for only the CAMS2 data, B=3 for both CAMS1 and CAMS2 and B=4 if the CAMS data are simulated. The values for C indicate if the HXI housekeeping data are present: C=1 for only HXI1 data, C=2 for only the HXI2 data, C=3 for both HXI1 and HXI2. D and E are not used and set to 0.

SGDcode
This is a five-digit number, ABCDE, to identify the type of data present for the SGD. The values for A indicate if the SGD1 science data are present: A=1 only CC1 data, A=2 only the CC2 data, A=3 only CC3, A=4 ALL CC, A=5 only CC1 and CC2, A=6 only CC1 and CC3, A=7 only CC2 and CC3. The values for B indicate if the SGD2 science data are present: B=1 only CC1 data, B=2 only the CC2 data, B=3 only CC3, B=4 ALL CC, B=5 only CC1 and CC2, B=6 only CC1 and CC3, B=7 only CC2 and CC3. The values for C indicate if the SGD housekeeping data are present: C=1 for only SGD1 data, C=2 for only the SGD2 data, C=3 for both SGD1 and SGD2. D and E are not used and set to 0.

SXIcode
This is a five-digit number, ABCDE, to identify the type of data present for the SXI. The value A=1 indicates if the SXI science data are present. The value B=1 indicates if the SXI exposure is present. The value C=1 indicates if SXI HK is present and D=1 if the hot pixel table is present. E is not used and set to 0.

SXScode
This is a five-digit number, ABCDE, to identify the type of data present for the SXS. The values for A indicate if the SXS science data are present: A=1 only SXS pixel data, A=2 only the SXS antico data, A=3 both are present. The value B=1 indicates if the SXS lost GTIs are present. The values for C indicate if the SXS housekeeping data are present: C=1 means only SXS HK1 data, C=2 means only the SXS HK2 data, and C=3 means both HK1 and HK2 are present. The value for D indicates if other diagnostic data associated with the pixel array: D=1 for noise data, D=2 for pulse data, D=3 for wfrb, D=4 all, D=5 for noise and wfrb, D=6 for noise and pulse, and D= 7 for wfrb and pulse. The value for E indicates if other diagnostic data associated with the antico array: E=1 for noise data, E=2 for wfrb, E=3 for both.

Gencode
This is a five-digit number, ABCDE, to identify the general auxiliary type of data present in the observation. The value A=1 indicates if the attitude data are present. The value B=1 indicates if the orbit data are present. The value of C is for the HK: C=1 for the HK1, C=2 for the HK2 and C=3 for both. The value D=1 indicates if the time file is present. E is not used and set to 0.

Processing_Date
This parameter records the date when the data were last processed.

Public_Date
This is the date when the data became public. All observations were made public on the same date.

Distribution_Date
This records the date when the data were first distributed to the SWG which corresponds to the first time the data have been processed. Following this first processing the data were reprocessed other three times to include the latest instrument calibrations, software changes and latest attitude.

Processing_Version
This records the version of the processing script used in the pipeline to generate the data products for the observation.

CALDB_Version
This records the version of the CALDB Hitomi version for each of the instrument and used in the processing pipeline. The version is encoded as genYYYYMMDD_hxiYYYMMDD_sgdYYYMMDD_sxiYYYYMMDD_sxsYYYYMMDD. The date corresponds to the date to when the CALDB index was created.

Software_Version
This records the version of the HEAsoft and Hitomi software used in the processing pipeline to generate the data products of the observation.

Abstract
This parameter contains a short description of the aim of the observation.

Subject_Category
The subject category of the observation. The following are the possible subject categories: non-pointing data; calibration; galactic point sources; galactic diffuse emission; extragalactic compact sources; extragalactic diffuse sources; Gamma-ray bursts and other non-proposed TOOs.

Category_Code
Each subject category is assigned a code, as follows: 0=non-pointing data; 1=calibration; 4=galactic point sources; 5=galactic diffuse emission; 7=extragalactic compact sources; 8=extragalactic diffuse sources; 9=Gamma-ray bursts and other non-proposed TOOs.

PI_LName
The last name of the proposal's Principal Investigator. This is set to 'SWG' for observation taken during the SWG time frame.

PI_FName
The first name of the proposal's Principal Investigator.

Country
The country of the proposal's Principal Investigator. This is a string with the following possible values: USA (PI from U.S.), JAP (PI from Japan), EUR (PI from Europe), JUS (merged proposal: PI from Japan, Co-PI from USA), USJ (merged proposal: PI from US, Co-PI from Japan). Set to SWG for to the early observation.

Title
The title of the proposal that originated the observation.

Contact Person

Questions regarding the HITOMASTER database table can be addressed to the HEASARC Help Desk.

Page Author: Browse Software Development Team
Last Modified: Monday, 16-Sep-2024 17:28:48 EDT