Open itjung opened 6 years ago
@itjung Unfortunately, we don't have a great solution for this right now. I'm working on a major update to the DRP which (among other things) would allow one to control which slits the DRP analyzes, but that is going to take a while because that change has tendrils which reach in to many parts of the DRP's code, so I wouldn't wait on that.
An alternative hack to skip that problematic slit that has been used is the past is to replace the data (the pixel values) on the input file(s) for that slit with data from another unvignetted slit. One could do this via various astropy
tools or via something like IRAF's imreplace
. That should allow the DRP to proceed even though that slit's results would be unusable.
Sorry, I wish we had better news.
@joshwalawender Thank you very much for the comment. I will try the alternative way, and I think that it should be enough to run the pipeline with my data. Thanks again!
Hello,
I have a question about the issue that I have with a slit (slit#30 below), maybe vignetted around the edge of the mask. While I am running the pipeline, it's stuck with the error message as below during the background subtraction procedure. Is there any way to skip the problematic slit to finish the entire reduction procedure? Or if I can get help to make a proper modification in the source code.
Thank you very much!
Best, Intae Jung