NuSTAR Quicklook Products:

This page contains links to data products for ToO observations that have been triggered in the last 30 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 30 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 for detailed analysis.

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.

For timing analysis, we also note that the NuSTAR Clockfile is most accurate after long-term trends have been removed. This means that the clock solution will tend to get better over time, especially for observations taken from the ~two weeks prior to the generation of the clockfile. For rapid analysis of ToO's we urge that caution should be taken when interpreting timing analysis on timescales shorter than 10s of ms.

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.tgz.gpg

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

Target Name Sequence ID Observation Start Observation End Status Datafile
Holmberg_II_X1907013220012021:201:23:29:222021:203:06:15:00Public 90701322001_v6.tgz
Ho_II_X1_SADA_21201907010220012021:201:23:13:532021:201:23:25:00Public 90701022001_v1.tgz
Sol_21201_DL807010010022021:201:15:01:352021:201:15:15:00GO 80701001002_v1.tgz.gpg
Sol_21201807102000012021:201:00:01:332021:201:14:30:00GO 80710200001_v6.tgz.gpg
Sol_21201_SADA807010020012021:200:23:36:352021:200:23:50:00GO 80701002001_v1.tgz.gpg
Sol_21201_DL807010010012021:200:23:18:002021:200:23:30:00GO 80701001001_v1.tgz.gpg
NGC1052907016240022021:198:05:55:052021:198:17:10:00Public 90701624002_v4.tgz
GRS_1915p105907013230022021:195:06:35:132021:195:19:10:00Public 90701323002_v5.tgz
NGC_4656507600010022021:190:14:50:022021:194:17:10:00GO 50760001002_v9.tgz.gpg
4U_1543m475807023170082021:189:00:35:072021:189:11:40:00GO 80702317008_v10.tgz.gpg
4U_1543m475807023170062021:182:04:25:082021:182:15:20:00GO 80702317006_v7.tgz.gpg