NuSTAR Quicklook Products:

This page contains links to data products for ToO observations that have been triggered in the last 14 days. The datafiles are produced automatically as the data are processed by the NuSTAR pipeline. Data files downloaded from this location must be processed using NuSTARDAS as they do not include the /event_cl subdirectory with high level data products. Each tar file will contain a version number appended to the sequence ID to indicate when a file has been updated.

We do not recommend using these data for anything other than quicklook analysis of the data. Each tar file contains two files (MET_gaps.txt and EVT_gaps.txt) which contain the start/stop times (in both UTC and NuSTAR MET seconds) of any gaps in the file. If there are large gaps in the observation then it is likely that the data have not yet been fully downloaded from the satellite and the user is advised to proceed with caution.

IMPORTANT NOTE: Data files on this page will be automatically purged after 14 days, by which time the data should be available via BROWSE at the HEASARC. The SOC does not archive the individual versions of these datafiles, so these files should not be used for end-result science (i.e., papers). Always obtain the final data products from the HEASARC.

SECOND NOTE: As of 12/24/2018 all version numbers were reset to v1 on the quicklook files and all of the tar files below were re-generated. If you are unsure of whether you the latest data, please re-download the tar file below.

CAVEAT EMPTOR: Data files obtained in this directory have not been vetted by the NuSTAR Science Operations Team for Quality Assurance. If you encounter a problem with the data, we recommend waiting until a new tar file has been produced after the next data downlink or waiting until the data are available from the HEASARC.

Guest Observer (GO) observations are enrcypted using GPG with an encryption key sent to the PI when the observation is scheduled. Instructions for installing GPG are provided by the HEASARC.

To decrypt the files, use the following command (here using 80301306002 as an example sequence ID):

gpg --batch --yes --passphrase "<passphrase>" -o 80301306002_v1.tgz -d 80301306002_v1.gpg

...where "<passphrase>" is provided by the SOC.

Target Name Sequence ID Observation Start Observation End Status Datafile
GRB_190829A905023410022019:255:19:10:072019:256:14:05:00Public 90502341002_v7.tgz
GRB_190829A905023410012019:255:19:04:062019:255:19:10:00Public 90502341001_v1.tgz
Cyg_X2805113010042019:255:02:05:112019:255:14:40:00GO 80511301004_v5.tgz.gpg
Cyg_X2805113010022019:253:13:05:102019:254:00:05:00GO 80511301002_v6.tgz.gpg
SN2019esa804024140042019:250:19:30:132019:251:21:25:00GO 80402414004_v5.tgz.gpg
SN2019esa804024140032019:250:19:20:072019:250:19:30:00GO 80402414003_v1.tgz.gpg