| Search in Xamin or Browse... |
XRISMMASTR - XRISM Master Catalog |
HEASARC Archive |
Overview
The X-Ray Imaging and Spectroscopy Mission (XRISM) is an international mission led by Institute of Space and Astronautical Science (ISAS) of Japan Aerospace Exploration Agency (JAXA). XRISM was launched on 2023 September 6 (UT) into a near-circular orbit with an apogee of ~575 km, an inclination of ~31 degrees, and an orbital period of about 96 minutes. During the performance verification (PV) phase, targets selected by the XRISM science team are being observed. Subsequently, it will become a general observatory with annual call for proposals open to all astronomers.XRISM has two co-aligned instruments that are used concurrently: Resolve, a soft X-ray spectrometer, and Xtend, a wide field-of-view imager. Resolve uses an X-ray microcalorimeter with ~5 eV spectral resolution withs a 3x3 arcmin field of view. It is currently operating with the Gate Valve closed, which limits its effective bandpass to 1.7-12 keV. Xtend is an X-ray CCD instrument with a 38 x 38 arcmin2 field of view.
This table contains a list of observations that have taken place as well as those that have been accepted and planned. The latter includes pre-approved targets for TOO observations and priority C targets whose observations are not guaranteed.
Catalog Bibcode
2020SPIE11444E..5DLBulletin
The XRISMMASTR database table was last updated on 15 November 2024.References
XRISM: X-ray imaging and spectroscopy mission
Tashiro, M. S.
<International Journal of Modern Physics D, Volume 31, id. 2230001>
=2022IJMPD..3130001T
DOI: 10.1142/S0218271822300014
Provenance
This database table is based on information supplied by the XRISM Science Data Center at NASA/GSFC. It is updated automatically on a regular basis.Parameters
ObsID
This parameter contains a unique, 9-digit observation number.
Name
The name of the target of observation. In the majority of cases, this is
the commonly accepted designation of the object. It is also not uncommon
for additional information to be included in this filed, such as a location
within an extended object or the phase or the state of a variable object.
RA
The Right Ascension of the pointing position.
Dec
The Declination of the pointing position.
LII
The Galactic Longitude of the pointing position.
BII
The Galactic Latitude of the pointing position.
Roll_Angle
This parameter contains the roll angle of the observation. It is defined as
the angle that the Detector's Y-axis takes from celestial north, measured
counterclockwise when looking up on the sky.
Time
The start time of the observation, not including spacecraft slew, in UTC.
End_Time
The stop time of the observation, not including spacecraft slew, in UTC.
Duration
The total elapsed time from start to end of observation, including data gaps,
in seconds.
Exposure
Total exposure time calculated using the good-time intervals for the cleaned
Resolve (or Xtend, if Resolve is not operating) event file.
Xtd_Expo
The total Xtend on-source exposure in seconds using the good-time intervals from
the cleaned Xtend event file, or 0 if Xtend is not operating.
Rsl_Datamode
This parameter contains Resolve's data mode. Possible values are PX_NORMAL,
PX_MIDRES+MASPIXEL, OFF, and STANDBY (or possibly null if not yet observed).
Rsl_ADR
Resolve's ADR mode. Possible values are HELIUM and CRYOFREE (or possibly null
if not yet observed).
Rsl_Fil_Be
This parameter contains the Resolve filter wheel's Beryllium filter status.
The value is 'Y' if the filter is set to 'Be' during any part of the
observation; otherwise, it is 'N' (or possibly null if not yet observed).
Rsl_Fil_Fe55
The Resolve filter wheel Fe55 source status. Possible values: 'Y' or 'N' (or
possibly null if not yet observed).
Rsl_Fil_Nd
The Resolve filter wheel neutral density filter status. Possible values: 'Y'
or 'N' (or possibly null if not yet observed).
Rsl_Fil_Poly
The Resolve filter wheel polyimide filter status. Possible values: 'Y' or 'N'
(or possibly null if not yet observed).
Rsl_Fil_Open
The Resolve filter wheel open position status. Possible values: 'Y' or 'N'
(or possibly null if not yet observed).
Rsl_Fil_Undef
The Resolve filter wheel undefined indicator. The value is 'Y' if the
filter's position is undefined; otherwise, it is N. (The value can be null if
not yet observed.)
Rsl_Gateval
The Resolve gate valve closed indicator: 'Y' (meaning the gate valve is
closed) or 'N' (or possibly null if not yet observed).
Rsl_MXS1
The Resolve MXS source 1 status. Possible values are OFF, STANDBY, DIM,
MEDIUM, BRIGHT (or possibly null if not yet observed).
Rsl_MXS2
The Resolve MXS source 2 status. Possible values are OFF, STANDBY, DIM,
MEDIUM, BRIGHT (or possibly null if not yet observed).
Rsl_MXS3
The Resolve MXS source 3 status. Possible values are OFF, STANDBY, DIM,
MEDIUM, BRIGHT (or possibly null if not yet observed).
Rsl_MXS4
The Resolve MXS source 4 status. Possible values are OFF, STANDBY, DIM,
MEDIUM, BRIGHT (or possibly null if not yet observed).
Rsl_Thr
The Resolve pulse threshold version name. Possible values include A75a and
A120a.
Rsl_Shp
The Resolve pulse shape template name. Values are a date in the form
'YYYYMMDD'.
Xtd_Num_Modes
The number of Xtend modes: 0, if Xtend is not operating; otherwise, 1 or 2.
Xtd_Datamode1
The Xtend data mode for file(s) 1. This is for CCDs 1 and 2, and possible
values are Window1, Window2, Window1Burst, Window2Burst, Standby, and Off.
Xtd_Datamode2
The Xtend data mode for file(s) 2. This is for CCDs 3 and 4, and possible
values are Window1, Standby, and Off.
Xtd_Dataclas1
The Xtend data class for file(s) 1. This is an 8-digit code that describes
the CCDs used and their configuration for CCDs 1 and 2. It has the form
'zdmcccca', where:
z = placeholder always set to 3 for Xtend in-flight data
d = DETNAM: 0 = CCD, 1 = CCD12, 2 = CCD34
m = DATAMODE: 0 = WINDOW1 (full window), 1 = WINDOW2 (1/8 window),
2 = WINDOW1BURST (full window + 0.1 sec burst mode),
3 = WINDOW2BURST (1/8 window + 0.1 sec burst mode)
cccc = hexadecimal encoding of on-board instrument settings (thresholds, area
discrimination, ADC chains used, readout nodes used, charge injection
settings, etc.)
a = reserved bit, 0 for now.
Xtd_Dataclas2
The Xtend data class for file(s) 2. Similar to xtd_dataclas2, but this is for
CCDs 3 and 4.
Xtd_Exp_Win1
The Xtend exposure calculated using the good-time intervals from the cleaned
event file when the datamode is Window1. This is set to 0 if Xtend is not
operating in Window1 mode.
Xtd_Exp_Win2
The Xtend exposure calculated using the good-time intervals from the cleaned
event file when the datamode is Window2. This is set to 0 if Xtend is not
operating in Window2 mode.
Xtd_Exp_Win1b
The Xtend exposure calculated using the good-time intervals from the cleaned
event file when the datamode is Window1Burst. This is set to 0 if Xtend is
not operating in Window1Burst mode.
Xtd_Exp_Win2b
The Xtend exposure calculated using the good-time intervals from the cleaned
event file when the datamode is Window2Burst. This is set to 0 if Xtend is
not operating in Window2Burst mode.
Xtdcode
This is a 5-digit integer code that identifies the type of data present for
Xtend. Each digit is set to 1 (present) or 0 (absent). The five digits are
for science data, exposure data, HK data, hot pixel data, and a spare (i.e.,
the 5th digit is currently not used and always set to 0).
Rslcode
This is a 5-digit integer code that identifies the type of data present for
Resolve. The first digit is 1 if only pixel data are present, 2 if only
antico data are present, and 3 if both are present. The second digit is 1 if
lost GTI are present. The third digit is 1 if only Resolve HK1 data are
present, 2 if only HK2 data are present, and 3 if both are present. The
fourth digit is one if pixel noise record data re present, 2 if pixel pulse
record data are present, 3 if pixel wfrb record data re present, 4 if all
pixel diagnostic data are present, 5 if pixel noise and wfrb data are
present, 6 if pixel noise and pulse data are present, and 7 if pixel wfrb and
pulse data are present. The fifth digit is 1, if antico noise data are
present; 2, if antico wfrb data are present; and 3, if both are present.
Gencode
This is a 5-digit integer code that identifies the type of general auxiliary
data present in the observation. The first digit is 1 if attitude data are
present. The second digit is 1 if orbit data are present. The third digit is
1, if only HK1 data are present; 2, if only HK2 data are present; and 3, if
both are present. The 4th digit is 1 if the time ("TIM") file is present. The
fifth digit is currently unused.
Status
The status of the observation. Possible values are accepted, scheduled,
observed, preprocessed, processed, distributed, and archived.
Processing_Status
The processing status field can have values of either 'PROCESSED' or
'NOTPROCESSED'. If the former, the processing_date, the distribution_date,
and the public_date parameters are also set.
Processing_Date
This parameter contains the date when the data for this observation were last
processed.
Public_Date
This is the date when the data became or will become public.
Distribution_Date
This is the date when the data were first distributed to the PI, equivalent
to the first processing date plus one day.
Processing_Version
This parameter contains the version of the processing script used.
Num_Processed
The number of times this sequence was processed within a given processing
version.
CALDB_Version
The version of CALDB used in processing.
Software_Version
The version of the software used in the pipeline to process the data.
Prnb
This parameter contains the proposal number of the observation.
Abstract
The full text of the proposal abstract.
Subject_Category
The object category type of the target of the observation. Possible values are:
Solar System
Stellar Coronae, Winds, and Young Stars,
Accreting White Dwarfs and Novae
BH and NS Binaries
Non-Accreting Neutron Stars
Supernova Remnants
Galactic Diffuse Emission and Surveys
Normal Galaxies: Integrated Emission
Extragalactic Transients: SNe, GRBs, GW Events, and TDEs
Blazars and Other Jet-Dominated AGN
Non-Jet-Dominated AGN
Groups and Clusters of Galaxies
Extragalactic Diffuse Emission and Surveys
Astrophysical Processes
Time_Awarded
The total time awarded to the proposal for observing this target, in seconds.
Category_Code
The first digit of the ObsID, corresponding to PV, normal GO, calibration, etc.
Priority
The priority of the target: A, B, or C. Priority C targets are schedule
fillers and not guaranteed to be observed.
PI_LName
The last name of the Principal Investigator of the proposal for the target.
PI_FName
The first name of the Principal Investigator of the proposal for the target.
CoPI_LName
For merged proposals, the last name of the co-Principal Investigator.
CoPI_FName
For merged proposals, the first name of the co-Principal Investigator.
Country
International origin of proposal (Japan, US, Europe, or some combination for
merged proposals). Allowed values are JAP, USA, EUR, JUS, USJ, EUJ, JEU, USE,
EUS, and SWG. The value of SWG stands for Science Working Group, for
observations awarded to the XRISM Science Team outside the GO proposal
process.
Cycle
This parameter contains the proposal cycle number, or 0 for observations made
before the start of the XRISM Guest Observer Program.
Obs_Type
This parameter contains the type of observation. Allowed values are
NOR/NOR-TOO (for normal and normal TOO, respectively), LAR/LAR-TOO
(large/large TOO), KEY/KEY-TOO (key project/key project TOO), CAL/CAL-TOO
(calibration/calibration TOO), DDT/DDT-TOO (director's discretionary
time/TOO).
Title
The title of the proposal from which the target originated.
Remarks
Remarks taken from observation or pre-pipeline logs.
Contact Person
Questions regarding the XRISMMASTR database table can be addressed to the HEASARC Help Desk.Page Author: Browse Software Development Team
Last Modified: Monday, 16-Sep-2024 17:37:35 EDT
- HEASARC Director: Dr. Andy Ptak
- NASA Official: Dr. Andy Ptak
- Web Curator: J.D. Myers
- Last Modified: 16-Sep-2024