February 17, 2015 at 9:18 am #802
For those who are looking for some examples of FLAMINGOS-2 data reduction, I’m attaching some slides shown at the “New Opportunities with Gemini and SOAR instruments” meeting in Brazil, last year (2014).
It has a step-by-step explanation for both Imaging and Long-slit (LS) data processing.
Felipe NavareteFebruary 21, 2015 at 1:39 pm #812
Would you mind posting a script for how to handle K-band calibrations? I’m not sure which options to set in niflat to create the flat when I only have the “lamp-off” images for K.
Also, can you show how to deal with images where the sky background is above the nonlinear cutoff? I think I need to set things in f2prepare to handle this, but haven’t figured out the correct combination. At the moment I’m getting a sky flat that is essentially all 0s.
Thanks for the help,
Matthew KnightFebruary 25, 2015 at 8:01 pm #816
I think I’ve solved both of these problems, but I’d still be interested if a more experienced user has comments. Here’s what I did:
1. For K-band calibrations, I treated the dome flat (lamp off) images like twilight flats and used equal length darks. I didn’t change any options in any of the routines.
2. To handle non-linear data I set fl_nonlinear=no and fl_correct=no in f2prepare. In one set of images where the sky was quite close to the saturation limit I also set fl_saturated=no. Presumably the resulting images can’t be flux calibrated but are useful for morphological assessment.
As a follow up to #2, the documentation to f2prepare says that the flag fl_correct has not been implemented. I am wonder if this is still accurate for Gemini IRAF v1.12? If there actually is nonlinear correction available then I’m guessing I should be using fl_correct=yes but fl_nonlinear=no?
Matthew KnightSeptember 15, 2015 at 8:35 pm #965
I’ve been trying to modify your example for H and Ks band imaging and am having lots of errors. Would you be able to upload your cl scripts for those bands too? It would be very helpful. I did manage to get the J band imaging to reduce but I had to modify your script somewhat to do so, I’m not sure if I turned anything important off in the process though.
I also have a question about what values we should select when the interactive window pops up. What exactly are we trying to achieve here?
It’s not obvious what a “good” value would be for either the high or low counts.
You must be logged in to reply to this topic.