Building and using a PFC table file.
Updated: Oct27,2020

In Oct2020 I resumed using the CCDRED-processed galaxy images that are located on sco2019 at /media/sco/DataDisk1/sco/AD/PFC/Red_PhaseI_Data.

  1. Where was this work started?
  2. Making the table file.
  3. Appendix: Older (2018) methods.



Where was this work started?

I found a PFC work directory from July 2019.

  % echo $HOST 
sco2019
% pwd 
/home/sco
% ls -lt |grep PFC 
drwxr-xr-x  5 sco sco    4096 Jul  7  2019 PFC/

Then I found some notes: 
% pwd 
/home/sco/PFC/Image_Cat/S
% ls 
PARAMS	READE.PFC_Image_Cat  Rules.1


Rather than try to keep track of the README file, I am reviewing the steps as I compose this web doc.

Return to top of page.



Making the table file.

I have a document on gathering images that covers the procedures below.

  
% fitsfind /media/sco/DataDisk1/sco/AD/PFC/Red_PhaseI_Data > list.pfc  
% survey_headers.sh list.pfc EX1 N 
% table_column_pull EX1 object N Object.Names N 
% rc3_name_match.sh Object.Names N 

# Create a file that lists the RC2 parameters we want to gather 
% cat PARAMS 
B(T)_RC3  
(B-V)t    
(U-B)t    
logD25    
logR25    
Type_RC3  

% rc3_table_make.sh rc3_name_match.indexrc3 PARAMS EX1.images  
% table_merge EX1 RC3TAB PFCRC3 N 


The fitsfind step takes a second or two and gathers a list of 2022 PFC images. The run of survey_headers.sh takes 18 seconds (faster on subsequent runs) and results in a table file (EX1) with 2022 entries:
  
% ls 
EX1.images  EX1.params	EX1.parlab  EX1.table  list.pfc  subdir.path

% table_checker EX1 N
2022 8 

% cat EX1.parlab
im         image table number 
uthrs      UT time (floating point hours)  
d2000      Days since Jan2,2000 (floating point days)  
fil        filter name  
source     image source  
isoobs     observation time in ISO8601 format  
object     object name    
imbase     FITS image basename  

# To make a plot 
% Generic_Points N
% getrc
% xyplotter_auto EX1 im uthrs 1 N                     
 
The table_column_pull command runs almots instantaneously, and the rc3_name_match is also extremely fast. Here is what we have after those steps:
  
 % ls 
EX1.images  EX1.parlab	EX1.table  list.pfc  Names.Not_Recognized  Object.Names  rc3_name_match.indexrc3

The file "rc3_name_match.indexrc3" ist the important one in this case as it lists the RC2 index position for each image in our list of 2022 images. In the remainder of the process we'll use this cross-id set to build a table file that hase image and RC2 information combined.

The rc3_table_make takes about 2 seconds to run and builds a table (RC3TAB) that contains the requested RC3 parameters (specified in PARAMS) for each of our 2022 images. Here is what that looks like:

 
% ls 
EX1.images  EX1.parlab	EX1.table  list.pfc  Object.Names  PARAMS  rc3_name_match.indexrc3  s/

% rc3_table_make.sh rc3_name_match.indexrc3 PARAMS EX1.images   
tabmake.params is present.

% ls 
EX1.images  EX1.table  Object.Names  rc3_name_match.indexrc3  RC3TAB.parlab  s/
EX1.parlab  list.pfc   PARAMS	     RC3TAB.images	      RC3TAB.table

Finally, the last routine in the process, table_merge combines the two tables (EX1 and RC3TAB) to make a single table (PFCRC3). This takes less than a second to run.




Back to calling page