PDS_VERSION_ID = PDS3 RECORD_TYPE = STREAM OBJECT = TEXT PUBLICATION_DATE = 1999-08-12 NOTE = "NAIF Toolkit Installation Instructions for the Sun. Structure, contents, and installation for other platforms will be similar; see TK_FTP.TXT for information on obtaining other versions." END_OBJECT = TEXT END NAIF Toolkit Installation Instructions for the Sun/Solaris =========================================================================== This document describes how to install the SPICE TOOLKIT package on Sun Computers using the SOLARIS operating system. We recommend that at a minimum you look over the sections "System Requirements" and "Installing the SPICE TOOLKIT Package" before you begin installing the SPICE TOOLKIT package. Other Files In addition to this document there are four text files that may be of interest. They are available via anonymous ftp on naif.jpl.nasa.gov (128.149.126.23) under the path pub/naif/toolkit/Sun_Solaris. dscriptn.txt contains a description of the directory structure and contents of the SPICE TOOLKIT package. naif0007.tls is a leapseconds kernel. Most SPICE-based applications require such a file. It is used in converting time between Coordinated Universal Time (UTC) and ephemeris time (ET). Note that Leapseconds files become outdated with time. This is because new leapseconds occur on a more or less annual basis (either at the last second of June 30 or the last second of December 31 UTC). The agency responsible for determining the occurrence of leapseconds (the International Earth Rotation Service) announces when a leapsecond will occur several months in advance of the leapsecond. When this announcement is released, NAIF prepares a new leapseconds kernel that reflects the announced leapseconds. This file is expected to accurately reflect the leapseconds that will have occurred prior to June 30, 1999. pck00006.tpc is a Planetary Constants Kernel. It is used in determining the shape and orientation of planets and satellites. This file is used in computing the transformations from various inertial frames to bodyfixed frames and for determining quantities such as solar incidence angles, sub-spacecraft points, latitude and longitude of boresight intercepts, etc. whats.new describes new features available in this version of the SPICE TOOLKIT package. System Requirements -------------------------------------------------------- Before you begin installing the SPICE TOOLKIT package, you should make sure that you have approximately 70 Megabytes of free diskspace. After the toolkit has been installed you can delete the file toolkit.tar which will free up approximately 34 MegaBytes of space. WARNING If you are using the new Sun OS TMPFS filesystem (included in Sun OS 4.1 and higher), you may run into problems. There is a bug in the TMPFS that causes the Fortran compiler to incorrectly compile DATA statements when the TMPFS filesystem is mounted on /tmp. (Fortran creates intermediate compilation files in /tmp.) The solution to this problem is to create the intermediate compilation files in another directory. The compiler option ``-temp=(alternate tmp directory path)'' does this. Because the vanilla Fortran 1.3.1 does not support this option, you need to obtain a patched version of ``f77pass1'' (first pass of the Fortran compiler). Contact your Sun representative to obtain the patched version. The Patch-ID number is 100507-04. Time for Installation. The amount of time required to perform the installation varies, but installation typically takes approximately 25 minutes. If you already have a SPICE TOOLKIT Package You should backup and move (or remove) any previous editions of the SPICE TOOLKIT Package from the directory where you plan to install this toolkit. Otherwise this toolkit may be merged with the previous edition leading to unpredictable results. Installing the SPICE Package -------------------------------------------------------- You should move the following files to the directory where you want to install the SPICE TOOLKIT Package. toolkit.tar.Z install.csh (Note: If you are copying the ".tar.Z" file via ftp you should copy it in "binary" mode. Use "ascii" mode to copy the ".csh" file.) Now type the following command. /bin/csh -f install.csh The script install.csh will uncompress and untar the toolkit and, as needed, compile and link all source code products. If you experience problems with the installation process, first refer to the section at the end of this document entitled "Installation Problems". If you can't resolve the installation problem there, contact NAIF for assistance. After the Installation -------------------------------------------------------- After the software has been installed successfully, you should convert the example SPK and CK files from transfer format to binary format. Converting SPK and CK Files from Transfer to Binary Format The files that NAIF delivers to you in the Toolkit are example files. To find them, look in (installation directory)/toolkit/data The files with the extensions .tsp and .tc need to be converted to binary format. Use the extensions .bsp for binary SPK files, and .bc for binary CK files. The SPICELIB readers and all of the NAIF Toolkit programs that read ephemeris and pointing files require the files to be in binary format. Consult the SPACIT User's Guide (spacit.ug) in the directory (installation directory)/toolkit/doc for information about running SPACIT, the program that converts and summarizes S- and P- kernel and C- kernel files. How to Contact NAIF -------------------------------------------------------- If you have problems or suggestions you can contact NAIF via U.S. Mail, electronic mail or phone as specified below. U.S. Mail address: Charles Acton Jet Propulsion Laboratory Navigation Ancillary Information Facility 4800 Oak Grove Drive Mail Stop 301-125L Pasadena, CA 91109 Electronic mail address: Internet: cacton@spice.jpl.nasa.gov (cacton@128.149.126.2) btaber@spice.jpl.nasa.gov (btaber@128.149.126.2) nbachman@spice.jpl.nasa.gov (nbachman@128.149.126.2) bsemenov@spice.jpl.nasa.gov (bsemonov@128.149.126.2) Phone number: (818) 354-3869 (Chuck Acton) (818) 354-4279 (Bill Taber) (818) 354-7454 (Nat Bachman) (818) 354-8136 (Boris Semenov) Installation Problems -------------------------------------------------------- Although the installation does not make a lot of assumptions about your computing environment, it must make a few. Installation problems usually occur because one of these assumptions is not met by the system where the SPICE package is being installed. Shell Prompt In several examples below, we will talk about interacting with the UNIX shell. We shall assume that the shell prompts you for input by displaying the string: myprompt> What your system displays will almost certainly be different. UNIX SHELL It is assumed that you have the UNIX C-shell installed on your machine and that it is the normal shell you use when working on your system. It is easy to determine if this is in fact the case. At the shell prompt type: myprompt> echo $shell If you are using the C-shell, you should see the following message on your screen. /bin/csh If your process responds with some other message, then either you are not using the C-shell, or its not in the expected location. To see if you have the C-shell available on your system type the following command. myprompt> ls -1 /bin/csh You should get the following response from your process. /bin/csh* If you don't get this, your system doesn't satisfy the installation script assumptions. You can't install the SPICE package using these instructions. uncompress and tar The SPICE package is delivered via a compressed "tar" file. You must have the "uncompress" and "tar" program present on your system to install the toolkit. You can find out if you have these programs by typing: mypropmt> which uncompress myprompt> which tar Your system should respond with messages similar to the following /usr/ucb/uncompress /bin/tar If it doesn't you won't be able to extract the toolkit from the "tar" file. FORTRAN It is assumed that you have a working FORTRAN compiler and that your environment is set up so that you can simply type "f77" to invoke the compiler. Moreover, it is assumed that "f77" is not an alias. You can determine whether or not "f77" is an alias for some other command by typing: myprompt> alias f77 If f77 is an not an alias, the the shell responds by re-issuing the shell prompt. In this case you've passed the last hurdle and you should be ready to install the SPICE package. If "f77" is an alias, how "f77" is aliased will be displayed. In this case you need to perform the following two commands. myprompt> unalias f77 myprompt> which f77 The second command should yield a fully qualified path for your FORTRAN compiler. If it doesn't you need to find out which directory contains the FORTRAN compiler and add this directory to your path.