coordinates from phot
Angelap wrote on Apr 24, 2011
Hello,
I am using noao->digiphot->daophot to calculate the coordinates and the magnitudes of several stars in an image. I calculate the coordinate list using daofind and I use the output list to run phot and get the magnitudes. I noticed that the output of daofind (*.coo) gives the positions in pixels to 3 decimal places but the output of phot(*phot) gives the positions to 2 decimal places.
I was wondering why that happens, I would like to keep 3 decimal places in the positions. Is there any way to have phot keep the 3 decimal places from the .coo file? Is there a parameter (switch) in phot that I can change so that the output phot file keeps the 3 decimal places from the .coo file?
Thank you.
I am using noao->digiphot->daophot to calculate the coordinates and the magnitudes of several stars in an image. I calculate the coordinate list using daofind and I use the output list to run phot and get the magnitudes. I noticed that the output of daofind (*.coo) gives the positions in pixels to 3 decimal places but the output of phot(*phot) gives the positions to 2 decimal places.
I was wondering why that happens, I would like to keep 3 decimal places in the positions. Is there any way to have phot keep the 3 decimal places from the .coo file? Is there a parameter (switch) in phot that I can change so that the output phot file keeps the 3 decimal places from the .coo file?
Thank you.
Mike Fitzpatrick wrote on Apr 24, 2011
This is not something that can be changed by a parameter, you would need to make a code change and recompile the task. Post back if you're comfortable doing this and I can send instructions.
Angelap wrote on Apr 24, 2011
Thank you for the response. I have never done a code change before but if that is the only way to do this I would appreciate the help.
Mike Fitzpatrick wrote on Apr 24, 2011
Would you mind posting a snippet of the output file in question and let me know what IRAF version you're using? The code I'm looking at should already be printing the coords to 3 decimal places so either you're using an older version of the code or I'm looking at a different place that writes the coords.
Last post on Apr 24, 2011