NMISC -- Package of NOAO miscellaneous tasks This external package contains NOAO developed tasks which by themselves are too minor to form their own external package. These tasks are made available in this package prior to distribution as part of the standard IRAF core system or NOAO package. Thus the contents of this package will vary with time. The current contents of the package are: -- Beta version tasks for creating and using pixel masks -- ccdmask - Create a pixel mask from a CCD image fixpix - Fix pixels defined by a pixel mask text2mask - Convert text description to pixel mask -- Focusing and PSF measuring tasks -- kpnofocus - Determine the best focus from KPNO focus images psfmeasure - Measure PSF sizes from stellar images specfocus - Determine spectral focus and alignment variations starfocus - Determine direct focus variations from stellar images -- New version with additional FWHM measurements from the V2.11 TV package -- newimexamine - IMEXAMINE with new FWHM measurements -- New task from the V2.10.4 IMAGES package -- xregister - Register 1-D pr 2-D images using x-correlation techniques Below is a revision log for tracking the changes to this package. RELEASE INFORMATION =============================================================================== Archive 1/18/00: v12-p6 Removed tasks which are already in the standard IRAF release. These are surfit, astcalc, nsplot, and the automatic identify tasks. =============================================================================== Archive 10/7/98: V12-p5 One bug fix for profile fitting used in STARFOCUS and PSFMEASURE. =============================================================================== Archive 10/3/97: V12-p4 Various minor bug fixes. Binaries are linked statically against the V2.11 libraries. =============================================================================== Archive 10/24/96: V12-p3 Fixed a bug in fitting the parabola in STARFOCUS and KPNOFOCUS. This caused unstable values or crashes if the focus values were too large. =============================================================================== Archive 8/29/96: V12-p2 Fixed a bug affecting STARFOCUS, PSFMEASURE, and KPNOFOCUS in which a pixel scale other than 1 could produce incorrect results. mkpkg will now create architecture directories if not present. =============================================================================== Archive 4/12/96: V12-p1 Fixed a minor datatype mismatch in order to compile on Dec/Alpha. =============================================================================== Archive 4/4/96: V12 1. Fixed problem with the automatic identification tasks that did not allow them to be applied to absorption lines. 2. Changed filename and procedure names to avoid library name conflict. 3. NEWIMEXAME has Moffat profile fitting and iterative radius adjustment. 4. PSFMEASURE, STARFOCUS, KPNOFOCUS have Moffat profile fitting and various improvements. =============================================================================== Archive 2/5/96: V11 New version of SPLOT which includes Lorentzian and Voigt profile fitting and deblending. New and revised tasks from the V2.11 spectroscopy packages are AIDENTIFY, AREIDENTIFY, AUTOIDENTIFY, AIDPARS. These tasks use a new automatic line identification algorithm. The particular features are the 'b' key in AIDENTIFY (a version of IDENTIFY) the new task AUTOIDENTIFY, and new automatic zeropoint shift step in AREIDENTIFY (a version of REIDENTIFY). New tasks from the V2.11 ASTUTIL package are ASTCALC and ASTRADIUS. ASTCALC is an astronomical calculator which can be used interactively or from a command file, can take input from images, text files, and CL parameters, and has many astronomical functions. ASTRADIUS uses ASTCALC to compute the spherical distance of images containing coordinates from a specified point in the sky and prints the images which are within a specified radius. =============================================================================== Archive 11/21/95: V10 A new version of IMEXAMINE with new algorithms to measure the FWHM of objects. This is the version currently slated for V2.11. Changed the centering routine in STARFOCUS/PSFMEASURE to only use the data in the specified radius rather than the extended region including the sky. =============================================================================== Archive 6/26/95: V9 1. STARFOCUS, PSFMEASURE, KPNOFOCUS now check to see if the image is already displayed independent of the image extension. 2. SPECFOCUS now allows an image header keyword for specifying the focus. This previously did not work as intended. 3. Prototype version of tasks to create a mask from CCD flat fields and apply it to data. =============================================================================== Archive 10/28/94: Eighth release for changes noted below. Added saturation and ignore_sat parameters to allow detecting measurements with saturated pixels and either discarding the measurement or flagging it for the output log. =============================================================================== Archive 9/19/94: Seventh release for changes noted below. Added an "iteration" parameter that, if greater than 1, uses the previous FWHM estimate to adjust the "radius" parameter. The interpretation of the focus parameter in STARFOCUS did not work properly. =============================================================================== Archive 5/9/94: Sixth release for changes noted below. KPNOFOCUS now prints a little description of which stars to mark. This is a very minor change intended to avoid errors when used on Kitt Peak by new users. Also a typo in the message printed by STARFOCUS was fixed. =============================================================================== Archive 3/4/94: Fifth release for changes noted below. 1. The xregister tasks for registering lists of images using 1 and 2 D x-correlation techniques was added to the package in order to make it available to users prior to the iraf 2.10.3 release. Xregister will eventually reside in the images package. 2. The surfit tasks for fitting surfaces to (x,y,z) data and producing an image was added to the package in order to make it available to users prior to the 2.10.3 release. Surfit will enventually reside in the utilities package. =============================================================================== Archive xx/xx/xx: Fourth release for changes noted below. 1. A new parameter, fstep, was added to STARFOCUS to allow specifying the focus sequence as a starting value, by the focus parameter, and a step. 2. STARFOCUS was modified to allow specification of header keywords for the focus (this was true previously), the focus step, the number of exposures, and the multiple exposure shift. This allows multiple exposure images to be completely header drivien if the appropriate keywords are present. 3. A new task KPNOFOCUS was added. This is a script calling STARFOCUS with parameters set specifically for Kitt Peak headers containing the focus parameters in the header. Many of the parameters are fixed in the script and the task parameters are then simpler. 4. STARFOCUS/PSFMEASURE were modified to search all display frames for the requested image rather than just frame 1. 5. A new parameters, frame, was added to STARFOCUS/PSFMEASURE to specify the display frame to load if necessary. Previously it was always frame 1. 7. In STARFOCUS the default number of steps was changed to 7 and the default step size to 30. 8. Added a prompt for interactive display marking. =============================================================================== Archive 10/23/93: Third release for changes noted below. 1. The background estimation in STARFOCUS/PSFMEASURE could be systematically low for integer type data. 2. The output was reordered so the final answer is last. =============================================================================== Archive 7/7/93: Second release Beta testing for STARFOCUS/PSFMEASURE Please send comments to iraf@noao.edu Two new tasks have been added for measuring the width of stellar objects. One is PSFMEASURE and the other is STARFOCUS. The latter includes capabilities for analyzing focus variations. (7/25/93, Valdes) =============================================================================== Archive 10/27/92: First release consisting of just SPECFOCUS. =============================================================================== INSTALLATION INSTRUCTIONS FOR THE NMISC PACKAGE Installation of this external package consists of obtaining the files, creating a directory containing the package, compiling the executables or installing precompiled executables, and defining the environment to load and run the package. The package may be installed for a site or as a personal installation. If you need help with these installation instructions pr questions about the package please contact iraf@noao.edu or call the IRAF HOTLINE at 520-318-8160 [arch] In the following steps you will need to know the IRAF architecture identifier for your IRAF installation. This identifier is similar to the host operating system type. The identifiers are things like "ssun" for Solaris, "alpha" for Dec Alpha, and "linux" or "redhat" for most Linux systems. The IRAF architecture identifier is defined when you run IRAF. Start the CL and then type cl> show arch .ssun This is the value you need to know is without the leading '.'; i.e. the IRAF architecture is "ssun" in the above example. [1-site] If you are installing the package for site use login as the 'iraf' user and edit the IRAF file defining the packages, i.e. hlib$extern.pkg % cd $hlib % vi extern.pkg Define the environment variables nmisc to be the pathname to the nmisc package root directory. The UNIX pathnames MUST be terminated with a '/'. Edit extern.pkg to include the following. reset nmisc = //nmisc/ task nmisc.pkg = nmisc$nmisc.cl Where "" is the place you unpacked the package distribution files. Near the end of the extern.pkg file, update the definition of helpdb so it includes the nmisc help database, copying the syntax already used in the string. Add this line before the line containing a closing quote: ,nmisc$lib/helpdb.mip\ [1-personal] If you are installing the package for personal use define a host environment variable with the pathname of the directory where the package will be located (needed in order to build the package from the source code). Note that pathnames must end with '/'. For example: % setenv nmisc /local/nmisc/ In your login.cl or loginuser.cl file make the following definitions somewhere before the "keep" statement. reset nmisc = /local/nmisc/ task nmisc.pkg = nmisc$nmisc.cl printf ("reset helpdb=%s,nmisc$lib/helpdb.mip\nkeep\n", envget("helpdb")) | cl flpr If you will be compiling the package, as opposed to installing a binary distribution, then you need to define various environment variables. The following is for Unix/csh which is the main supported environment. # Example % setenv iraf /iraf/iraf/ # Example path to IRAF root % source $iraf/unix/hlib/irafuser.csh # Define rest of environment % setenv IRAFARCH ssun # IRAF architecture where you need to supply the appropriate path to the IRAF installation root in the first step and the IRAF architecture identifier for your machine in the last step. [2] Login into IRAF. Create a directory to contain the package files. These directory should be outside the standard IRAF dir- ectory tree. cl> mkdir nmisc$ cl> cd nmisc [3] The package is distributed as a tar archive for the sources and, as an optional convenience, a tar archive of the executables for select host computers. Note that IRAF includes a tar reader. The tar file(s) are most commonly obtained via anonymous ftp. Below is an example from a Unix machine where the compressed files have the ".Z" extension. Files with ".gz" or ".tgz" can be handled similarly. cl> ftp iraf.noao.edu (140.252.1.1) login: anonymous password: [your email address] ftp> cd iraf/extern ftp> get nmisc.readme ftp> binary ftp> get nmisc.tar.Z ftp> get nmisc-bin..tar.Z (optional) or .... ftp> get nmisc-bin..tar.gz (optional) ftp> quit cl> !uncompress nmisc.tar cl> !uncompress nmisc-bin..tar (optional) The readme file contains these instructions. The in the optional executable distribution is replaced by the IRAF architecture identification for your computer. Upon request the tar file(s) may be otained on tape for a service charge. In this case you would mount the tape use rtar to ext- ract the tar files. [4] Extract the source files from the tar archive using 'rtar". cl> softools so> rtar -xrf nmisc.tar so> bye On some systems, an error message will appear ("Copy 'bin.generic' to './bin fails") which can be ignored. Sites should leave the symbolic link 'bin' in the package root directory pointing to 'bin.generic' but can delete any of the bin. directories that won't be used. If there is no binary directory for the system you are installing it will be created when the package is compiled later or when the binaries are installed. If the binary executables have been obtained these are now extracted into the appropriate bin. directory. # Example of sparc installation. cl> cd nmisc cl> rtar -xrf nmisc-bin.sparc.tar # Creates bin.sparc directory The various tar files can be deleted once they have been successfully installed. [5] For a source installation you now have to build the package executable(s). First go to the package root directory with cl> cd nmisc If you are updating to a newer version and you earlier built the libraries and executables it is necessary to delete these. Otherwise, depending on the dates of files in the new version and the locally built libraries, it may cause the new version to be ignored. To do this the package is configured "generic" which puts all the binary files in one binary directory, the files are deleted and then you continue in the same way as a completely new installation. cl> mkpkg -p nmisc generic cl> delete bin./* # Substitute sparc, ssun, alpha, etc. Configure the package for the particular architecture to be built. cl> mkpkg -p nmisc # Substitute sparc, ssun, alpha, etc. This will change the bin link from bin.generic to bin.. The binary directory will be created if not present. If an error occurs in setting the architecture then you may need to add an entry to the file "mkpkg". Just follow the examples in the file. To create the executables and move them to the binary directory cl> mkpkg -p nmisc # build executables cl> mkpkg -p nmisc generic # optionally restore generic setting Check for errors. If the executables are not moved to the binary directory then step [1] to define the path for the package was not done correctly. The last step restores the package to a generic configuration. This is not necessary if you will only have one architecture for the package. This should complete the installation. You can now load the package and begin testing and use.