ccdrev

Review contents of a FITS image.


% ccdrev ast1.fits
1992,1992,11:23:54.810,+03:18:23.40,NGC3664_R,lf1_0004,

% ccdrev dss.fits

In the second example, we get an empty line since the DETECTOR keyword is not present in a DSS FITS image.

The output of the script is typically pumped into the python code ccdrev_pfc.py. If the DETECTOR value is recognized, then a plate scale is assumed and the image size in arcminutes is predicted. So a typical run might be:

%  ccdrev ast1.fits >testo
% ccdrev.py testo

NAXIS1,NAXIS2 = 1992 1992
Ra,Dec (strings): 11:23:54.810 +03:18:23.40
Ra,Dec (Degrees): 170.978375000 3.306500000
Ra,Dec (Hrs,Deg): 11.398558333 3.306500000
Object: NGC3664_R        Detector: lf1_0004
X,Y in arcmin: 44.820 44.820

Use arguments in "args_for_skygrab" to run skygrab

NOTE: Output format of ccdrev.py may change!

The last message reminds us that the python script ccdrev.py, in addition to writing useful information to standard out, has also written useful information to the local file "args_for_skygrab". This is a file that will be accessed by skygrab, the script script that will actually call the various catalog servers that will provide our calibration data.

The values in "args_for_skygrab" are the Ra,Dec of the image (in sexigecimal form) and the linear size of the image in units of arcminutes:

 
% cat args_for_skygrab
11:24:24.800 +03:19:39.00 29.133

 


 
  

 Back to SCO CODES page