PFC: 2022 UBVR images from McD PFC.
Updated: June 26, 2019

The PhaseI PFC images are CCD-processed, but require astrometric and photometric calibration. Most of the useful info (object name, approximate position, time of observation, etc...) are in the FITS headers.


I do this work in:    $scohtm/scocodes/finding_images/three_sets/pfc/work1

I start with the file listing the galaxy images: 
% fitsfind /media/sco/DataDisk1/sco/AD/PFC/Red_PhaseI_Data > list.pfc     
**** This make a list of the fullpath image names. 

I make a table file of images based on general FITS header information: 
% survey_headers.sh list.pfc EX1 N 
*** This takes about 19 seconds for the 2022 pfc images on sco2019 

% ls  
EX1.images  EX1.parlab	EX1.table  list.pfc  S/  survey_headers.output
% cat EX1.parlab  
im         image table number 
uthrs      UT time (floating point hours)  
fil        filter name  
source     image source  
isoobs     observation time in ISO8601 format  
object     object name    
imbase     FITS image basename  
% head -5 EX1.table  
# data
    1   4.936695 B     pfc      2005-01-16T04:56:12.18 N2655                Rsco3815                      
    2   7.376361 R     pfc      2005-01-14T07:22:34.92 N1961                Rsco3681                      
    3   3.711139 R     pfc      2005-01-15T03:42:40.12 M42                  Rsco3731                      
    4   4.575444 R     pfc      2005-01-16T04:34:31.61 N2655                Rsco3813               

*** I can make a point_selector run (that is not terribly useful)"
% point_selector EX1 im uthrs N  
    
I can view images effectively, but there is clearly not much use in viewing the image number vs. UT time in hours for the parameter space used by point_selector. I want a method for cross-matching to the RC3.

Since the PFC headers had useful OBJECT cards in the headers, the EX1 table made above contains the galaxy names. I can extract these names and build a corresponding RC3 table (RC3TAB).


I make a list of names using the EX1 table 
% table_column_pull EX1 object N Galaxy.Names N   
% head -5 Galaxy.Names 
  N2655
  N1961
  M42
  N2655
  N1961

I cross-match these names to get the RC3 index values
% rc3_name_match.sh Galaxy.Names N 
*** This makes :  rc3_name_match.indexrc3
Note: see the file Names.Not_Recognized

I assemble the file of RC3 parameeters based on the RC3 index values from above
The quanitites I want are in the file = PARAMS 
% cat PARAMS 
B(T)_RC3  
(B-V)t    
(U-B)t    
logD25    
logR25    
Type_RC3  
% rc3_table_make.sh rc3_name_match.indexrc3 list.EX1 PARAMS N 
*** This also takes just a few seconds to run on sco2019 and creates the table file: RC3TAB

I merge the two tables to make one large database that cross-matched the 
PFC and RC3 catalogs. 
% table_merge EX1 RC3TAB PFCRC3 N 

NOTE:  The parlab file in RC3TAB has the short parameter names repeated twice on each line. 
       Once the PFCRC3 file is made, it is useful to edit PFCRC3.parlab and install more 
       descriptive label names. 

**** At this stage I can make a plot and view images with point_selector:
%  point_selector PFCRC3 Type_RC3 B-Vt N    

***** I get nice plots, and the galaxy images have types that seem 
      to correspond well with the x-axis values in the plot. 
    

This all runs very quickly (second on sco2019), but is not great practical use. What could be useful now are scripts that operate on the RC3TAB table file to gather images of certain types: selection by galaxy name, PGC number, filter type(s), etc.... Maybe something that selects only certain galaxies, and then I could review this set of galaxy images with point_selector. This is looking useful.




Back to SCO CODES page