Make a table file using RC3 data.
% rc3_table_make.sh --help
usage: rc3_table_make.sh rc3_name_match.indexrc3 PARAMS EX1.images [-v] [-h]
arg1 - input file listing RC3 index numbers (e.g. rc3_name_match.indexrc3)
arg2 - file listing names of desired RC3 parameters
arg3 - file listing image names (e.g. EX1.images, can be "none")
Additional options:
-v = print verbose comments and run in debug mode
-h = just show usage message
If the input list file does not exist, then the code operates in interactive mode.
The rc3gal script I used to use that runs rc3tools to identify RC3 galaxies remains avaliable, but rc3_name_match.sh can be used for this also. Here is a complete example.
% rc3_name_match.sh none N *** Running in INTERACTIVE mode. **** Filling GCATS (names) array GCATS name array is filled. Enter galaxy name (N221, blank to stop): N4618 Catalog name = NGC number = 4618 indexrc3 = 13769 NGC 4618 UGC 7853 VV 73 PGC 42575 12:41:33.00 +41:09:03.0 J2000.0 Type = .SBT9.. Bt = 11.22 Ab(gal) = 0.00 Dia (arcmin) = 4.17 b/a = 0.813 V (km/s) = 592.0 T, (B-V)t, (U-B)t = 9.00 0.44 -0.19 Enter galaxy name (N221, blank to stop): I enter a blank return to indicate a STOPThis is alll a little klugy compared to the NED and AladinLite tools available on the web. However, this is a self-contained resources that runs in my system without internet access. It is also extrenely fast.
Bleow I show In example I ran in Oct2020 to find the rc2 matches to my PFC image data base. The EX1 table file contains the object card names that were pulled to the file "Object.Names".
% ls EX1.images EX1.parlab EX1.table list.pfc Object.Names PARAMS rc3_name_match.indexrc3 % rc3_table_make.sh rc3_name_match.indexrc3 PARAMS EX1.images % ls EX1.images EX1.table Object.Names rc3_name_match.indexrc3 RC3TAB.parlab EX1.parlab list.pfc PARAMS RC3TAB.images RC3TAB.table