Run the phot2 routine on a list of FITS images. The phot2 measures aperture magnitudes for a subset of the the images sources sources detected by image_catalogs. Actually, the primary photometry tool that is run is apphot_interactive.

The names of the FITS images can use any path (we'll just use the image basename) but the code must be run in the reuduction subdirectory (i.e. where the ./locaal_red/ subdirectory resides). In the example below, where I process just one image, I show how my original image location is in some unfamiliar location (phot2_check_3/PHOT2_local/20191018T084754.9_acm_sci.fits) but as long as I am in the roriginal reuction directory (.../ACM_work_Oct2019/red_20191018) I will have access to the files I need (image catlogs, processed images, etc....).

 

% phot2_fitslist --help      

Usage: phot2_fitslist list.in 0.05 3  -i
arg1 - list of FITS images to be processed
arg2 - maximum allowd ZP error (0.05)  
arg3 - minimum allowed number of calibrating sources (3) 
Additional options: 
     -i = run in interactive mode (ds9 and plot reviews) 
 --help = view a help document

Example:
% cd /home/sco/ACM_work_Oct2019/red_20191018
% ls
bias_20191018/	local_red/  S/	Save/  S_jun03/  Store_DSS/
% cat ./S_jun03/list.good_focus
/home/sco/ACM_work_Oct2019/phot2_check_3/PHOT2_local/20191018T084754.9_acm_sci.fits

% phot2_fitslist ./S_jun03/list.good_focus 0.05 3 
Not in interactive mode, so you must have apphot.config 

What the heck is an "apphot.config" file? I'll just run the code interactively 
and perhaps make one appear. 

% phot2_fitslist ./S_jun03/list.good_focus 0.05 3 -i 

In the example above, when I ran the code in an interactive mode, I was asked the size of the aperture to use and the number of minimum number of pixels I wanted to use in selecting targets from the moments-based catalogs of image_catalogs. I was also asked for a couple other values, but you can read about that in the documentation for phot2. The figure below summarizes our example 1 run.

The acm image reduced in example 1. The green markers show ALL of the images sources detected with image_catalogs. The size of each green circle is set using the number of pixels composing each threshhol-deteced source. The cyan markers denote the PS1 (PANSTARRS) sources collected for this image field (in the Store_DSS/ subdirectory). Finally, the blue regions are the apertures used to measure the selected targets. A 10" radius aperture is used here becasue that is what I spectfied interactively when the program queried me for an aperture size. I also specified that I wanted to perform a coordinate macth between my imag and the PS1 catalog using a 3" match radius. Using only sources with at least 8 pixels, an aperture radius of 10", and a match radius of 3", I found: Median ZP = -2.649 Mean ZP = -2.650 -+ 0.015 g SSB = 19.330 -+ 0.015 mag per sq.arcsec Before we freak out about the bright g-band sky surface brightness, let's look at part of the final FITS image header we just made: % ls ./local_red/PHOT2/20191018T084754.9_acm_sci.fits ./local_red/PHOT2/20191018T084754.9_acm_sci.fits % imhead ./local_red/PHOT2/20191018T084754.9_acm_sci.fits ZPSEC = -2.6495 / ZP for a 1-sec exposure ZPERR = 0.0150 / mean error of ZPSEC NUMZP = 6 / number of calbrating sources PSYSNAME= g / name of photometric system SKYMEAN = 473.66736 / mean sky in adu (skymap2) SKYME = 0.04068 / error of mean sky in adu SKYSIG = 30.96039 / sigma about mean sky in adu SKYSB = 19.3300 / sky surface brightness (mags per sq.arcsec) SKYSBERR= 0.0150 / mean error of SKYSB NUMBOX = 8 / number of sky boxes measured RSTRT = -1185.8464 / Radius position of tracker at start (mm) MILLUM = 84.1000 / percentage moon illumination PHIMOON = 48.1138 / angle of separation to moon (deg) VSKYSB = 18.8870 / predicted V sky surface brightness