CTIOPI FINDER GENERATION COOKBOOK

version 28 JUL 2005 by Jen Winters

---------------------------------------------------------------------------
FINDERS GENERATION FOR NON-DUMMIES ... A NAUSEATINGLY DETAILED COOKBOOK
---------------------------------------------------------------------------

1) Setting up:

   Open an iraf window ("xgterm -sb "&), "cl", "!ds9 &",
   cd to "/nfs/recons4/CTIOPI/regions/(star directory)"
   
   Throughout, I will use as an example g266-089ab, so in this case cd to
              "/nfs/recons6/CTIOPI/regions/00-02/g266-089ab"

2) Find the trail frame:

   You will need to discover the trail frame that was used. This frame has all the best
   parameters for use as a finder: good focus, good seeing, pi filter, an early frame if
   possible, and with all reference stars already tagged.
 
   to find the trail frame:
   type "more ctio.model". There will be a number in brackets further down the page.

   [17], in our example

   (q to quit)

   Sometimes the file 'ctio.model' does not exist in the star's home directory. It might
   exist in a 'final' or 'prelim' directory. If it does not exist in any directory, then
   no reduction has been done of this star, which means that there is no trail frame and
   therefore no appropriate frame available for the finder.
 
   Next, "emacs listfile" and scroll down to the line number (17 in this case) to find
   the o.fits file (the trail frame) that we will use; in our example, that would be
   20010829.09.102.o.fits.

   *** A note of caution: We've changed the naming format of these files, so you need to
   be sure that the file name looks like '20010829.09.102.o.fits'. Sometimes in a 
   'prelim' directory (that holds preliminary reduction data), there also exists a
   'listfile' file, but when you access it and scroll down to the proper line, you get
   something that looks like 'aug01s.7102.o.fits'. This is not useful.

3) Display your image:

   Make sure that you are in the home directory where the o.fits files are located.
   At this point, it is easier to have two windows open, one of which is the
   IRAF window and the other a normal terminal window.
   Then, "display 'starid'.o.fits 1 fil+".

   Now, you should alter the ds9 window: invert colormap, zoom to fit frame, and adjust
   the size of the ds9 window so that there is only a little white framing the window.
   Next, go to colormap parameters and select 3.0 contrast and 0.50 bias so that your 
   finder is consistent in look with the other finders and so that it is readable upon 
   print-out.If you are making multiple finders in one session, you will only need to do 
   this once.

   cp the .coord file to the directory where o.fits file is found, adding something to indicate
   that it is your working file.

	     In our example, "cp g266089.coord17  ./g266089.coord17.j"
 
4) Sort your reference stars:

   Next, sort the .coord file (g266089.coord17.j) by reference stars:
   ("control-space", then "alt-x sort-column"), making sure to move numbers 10+ to bottom of 
   the list.

   ---If your star is a binary, you will need to copy the last two tagged stars into a pi.coordAB
      file (as these are the A and B components; the flux counts will show which is which.) and
      then delete them from the main .coord file. Then, you should replace the flux column
      counts with A and B to denote each component.
 
   Close and save. 

5) Edit the reference star parameters:

   "epar tvmark" to edit the parameters:
   parameters for the reference stars should be:
		30  (radii)
		206 (blue-color)
		yes (to number marked coordinates)
		edit numbering to label pleasingly (to do this, you may want to play 
                     with the 'nxoffset' and 'nyoffset' values). 

   (ctrl-d to quit epar)

6) Number the reference stars:

   tvmark to display the reference stars on the finder:

       "tvmark 1 g266089.coord17.j"

   Check and adjust to be sure that the numbered reference stars are readable.Oftentimes, you 
   will have to sacrifice the numbering of one reference star because of its position at the 
   edge of the frame. We can hopefully assume that users of this digital finder will be able to 
   see the pattern of the numbering of the stars and figure out which number is missing.

7) Create a science star file:

   "emacs" a pi.coord17 file and copy your .coord17 file into it, deleting all but the last
   star, as it is usually the science star.

   ---If your star is a binary, you have already completed this step.

   Close and save.

8) Edit the science star parameters:

   "epar tvmark" to edit parameters
   parameters for the science star should be:
		40  (radii)
		206 (blue- color)
		no  (to number marked coordinates)

   ---If your star is a binary, you should also select
                yes (to label the marked coordinates)
     

9) Mark the science star:

   "tvmark 1 pi.coord17" (or "tvmark 1 pi.coordAB", if your star is a binary) to overlay the 
   science star on the reference star field.
   This creates a double circle around the science star.

   ---If your star is a binary, this also labels the components.

10)Save:

   Go to print- select as file, then "/nfs/morgan3/'yourdirectoryhere'/'starid'.ps"

***** When you save the finder as a .ps file, make sure that the name
      exactly matches the name in the file that Wei-Chun's script uses
      (the 'pi.result' file). And the script IS case sensitive, so
      watch out for that!

---------------------------------------------------------------------------------------------

NOTE:

   To run the script, you need the 'pi.result' file, the
   'ctiopi.finder.pl' file, and the 'ctiopi.finder.temp.tex' file. And
   the command is "perl ctiopi.finder.pl pi.result 'starid'".
 
---------------------------------------------------------------------------------------------