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.

Note for HEASOFT 6.34 For heasoft-6.34 installations, users should use the check_metsim_files=no when processing the data using nupipeline. A new optional flag was introduced in heasoft-6.34 that may result in a crash unless you use the above option.

Note about filename extensions: Some browsers rename .gpg downloaded files to .gz - to fix this just rename the files back to .gpg

Target Name Sequence ID Observation Start Observation End Status Datafile
AT2019wey912013350022026:224:23:45:052026:225:05:55:00Public 91201335002_v2.tgz
EP260531a812023320022026:222:02:50:032026:222:12:10:00GO 81202332002_v5.tgz.gpg
NGC5907_ULX1312020240022026:215:08:35:242026:217:18:50:00GO 31202024002_v6.tgz.gpg
EP260302a812024160022026:213:22:45:072026:214:09:55:00GO 81202416002_v6.tgz.gpg
EP260302a812024160012026:213:22:37:512026:213:22:45:00GO 81202416001_v2.tgz.gpg
EP251020a912016340022026:212:06:55:112026:213:05:15:00Public 91201634002_v8.tgz
EP260628c811023130082026:205:22:05:122026:206:20:05:00GO 81102313008_v6.tgz.gpg
EP260628c811023130062026:201:00:45:042026:201:03:20:00GO 81102313006_v6.tgz.gpg
EP260628c811023130052026:201:00:35:222026:201:00:45:00GO 81102313005_v6.tgz.gpg
1H0419m577811026430022026:199:17:05:152026:200:23:55:00GO 81102643002_v6.tgz.gpg
LSXPS_J1709p2651912016320022026:195:05:50:092026:195:16:40:00Public 91201632002_v4.tgz