Problem with ccfind in V2.14 of IRAF?
emma wrote on May 28, 2008
Hi there,
I am having a problem with ccfind. I have just received some new NIRI data and I have just tried running ccfind (using V2.14 of IRAF) in the same way as I had done previously using V2.12.2a of IRAF (by matching objects in the field with 2MASS objects) but it claims:
Skipping object 1 in file FILENAME: off image FILENAME.fits
for all the objects in the field (normally if I've got a rotation wrong or something similar it still manages to match *something*, but it's not matching anything) (and before anyone asks yes I have checked the rotations!) ;) When I overlay the positions of 2MASS objects over the image they match pretty well with the positions of the objects in the image, so ccfind really should be matching them (I have increased the box size just to make sure). Then, I tried re-running ccfind on the previous NIRI data I have (which it had done happily in V2.12.2a) but it didn't work. But when I tried running it on older FLAMINGOS data that I have it worked fine! So I'm guessing it's not the task itself, but something specific to the NIRI data. I have set the "usewcs" parameter to "no", but does ccfind read anything else from the header (maybe ccfind is looking for a new header keyword that NIRI data doesn't have, but FLAMINGOS data does??). Following on from this, I was wondering what changes had been made to ccfind between the two versions of IRAF (if any), as I didn't have any problems when using V2.12.2a?
I'm hoping someone has come across this problem before as I'm stumped!
Thanks!
Emma :)
I am having a problem with ccfind. I have just received some new NIRI data and I have just tried running ccfind (using V2.14 of IRAF) in the same way as I had done previously using V2.12.2a of IRAF (by matching objects in the field with 2MASS objects) but it claims:
Skipping object 1 in file FILENAME: off image FILENAME.fits
for all the objects in the field (normally if I've got a rotation wrong or something similar it still manages to match *something*, but it's not matching anything) (and before anyone asks yes I have checked the rotations!) ;) When I overlay the positions of 2MASS objects over the image they match pretty well with the positions of the objects in the image, so ccfind really should be matching them (I have increased the box size just to make sure). Then, I tried re-running ccfind on the previous NIRI data I have (which it had done happily in V2.12.2a) but it didn't work. But when I tried running it on older FLAMINGOS data that I have it worked fine! So I'm guessing it's not the task itself, but something specific to the NIRI data. I have set the "usewcs" parameter to "no", but does ccfind read anything else from the header (maybe ccfind is looking for a new header keyword that NIRI data doesn't have, but FLAMINGOS data does??). Following on from this, I was wondering what changes had been made to ccfind between the two versions of IRAF (if any), as I didn't have any problems when using V2.12.2a?
I'm hoping someone has come across this problem before as I'm stumped!
Thanks!
Emma :)
emma wrote on May 28, 2008
Well, I think that's a sign that I need to get some sleep!! The problem has been solved - it was a stupid mistake on my part! :oops:
Mike Fitzpatrick wrote on May 28, 2008
Glag you got it sorted.
For the record, the only change to CCFIND since v2.12 is a bug fix that only affects images using the ZPN projection.
Cheers,
-Mike
For the record, the only change to CCFIND since v2.12 is a bug fix that only affects images using the ZPN projection.
Cheers,
-Mike
Last post on May 28, 2008