From the nustar-idl repo, issue with badpixels...

[bwgref]

This was the issue:

We've recently figured out that nuskybgd assumes that all pixels that are found in the "badpix" files created by the NuSTARDAS pipeline are permanently bad. This is true when the pipeline is run at the NuSTAR SOC from Level 1 files. However, when the files are downloaded from the HEASARC the "badpix" files contain pixels that are temporarily bad (e.g. flickering pixels, etc). Since nuskybgd turns these all off by default, this results in a spotty background map which will create problems.

I can't remember if this was fixed or not.

[bwgref]

Not fixed.

[XiaonaS]

Dear Dr. Grefenstette, I want to use nuskybgd (IDL, the pynuskybgd doesn't work now, right? ) to extract the background for Nustar data, when I perform: "IDL> dir='./' IDL> obsid='60002025002' IDL> nuskybgd_instrmap,dir,obsid,'A','bgd' " It shows: % Compiled module: MRD_STRUCT. % Attempt to subscript INSTRMAP with II is out of range. % Execution halted at: NUSKYBGD_INSTRMAP 127 /home/sun/AnalysisTools/nuskybgd/pro/nuskybgd_instrmap.pro % $MAIN$

I don't know how to solve it, and could you please tell me how to fix it? Thanks in advance! Xiaona Sun

[XiaonaS]

And could you please provide us the data in git, such as 50002031004, in this case, I will understand them more fluently and clearly. Thanks!

[bwgref]

Hi Xiaona,

You're right, the python version is still in development and doesn't work yet.

Putting the 50002031004 example data in git is, unfortunately, not practical because the data volume is large (a couple of GB). You can download these from the HEASARC if you want to test using the ABC guide.

Your particular example is sometimes caused when the observation accidentally includes some "slew" data. See #14 for more details on this.

-BG

[XiaonaS]

Okey, thanks Dr. Grefenstette~