SYSTEM MANAGER'S GUIDE ********************** 1. Installation Procedures ========================== 2. Introduction to Login Files ============================== 3. Conventions for Directory Structures ======================================= Appendix A - Caveats ==================== Appendix B - Installation Notes for Unsupported Systems ======================================================= Appendix C - Documentation ========================== LAS Disclaimer ================== 1. Installation Procedures ************************** The Land Analysis System (LAS) consists of three software packages. They are: TAE - Transportable Applications Executive TAE interacts with end-users and manages the execution of the LAS applications. See the TAE Programmer's Reference Manual (not delivered) for detailed information on TAE. LAS - Land Analysis System LAS consists of image analysis routines designed to ingest, manipulate, and analyze digital image data and provide the user with a wide spectrum of functions and statistical tools for image analysis. See the LAS Overview for detailed information about LAS. ADAPS - AVHRR Data Acquisition and Processing System ADAPS is designed to receive, archive, and process Advanced Very High Resolution Radiometer (AVHRR) data from National Oceanic Atmospheric Administration (NOAA) Tiros-N polar orbiting satellites. See the ADAPS Overview for detailed information about ADAPS. This section describes the procedure needed to install the LAS package. Please read all of the information within the System Manager's Guide before beginning. Note that all of the example procedures listed are based on C shell syntax. LAS 7.4 has been installed on computer systems that support the following configurations: (See Appendix B if you have an unsupported machine.) o SGI IRIX 6.5 using the SGI MIPSpro C and Fortran Compilers: Version 7.3.1.2m o SUN Solaris 2.7 on a Sparc processor using gcc and g77, version 2.95.2 o Various Redhat, Mandrake, and SuSE Linux distributions with gcc 2.95 and 2.96 RH compilers (a mixture of what we have installed on developer machines, our local beowulf cluster, and developer's home machines). Both the 2.2 and 2.4 kernel series have been used. Previous versions of LAS have also been installed on the following systems, which are no longer supported: o DEC/VAX computers running VMS 4.7 or higher operating systems o SUN2 and SUN3 computers running SUN/OS operating system o Gould PowerNode computers running UTX 2.0 or higher operating systems o IBM RS6000 computers running AIX operating system o IBM RT computers running AIX operating system o Data General running DG/UX 5.4.1 Disclaimer ========== Although this software has been successfully installed on a computer system of the Geological Survey, U.S. Department of the Interior, no warranty, expressed or implied, is made by the Geological Survey as to the functionality of the software on any other system, nor shall the fact of distribution constitute any such warranty, and no responsibility is assumed by the Geological Survey in connection herewith. 1.1 Install Instructions ======================== LAS 7.4 is distributed in a compressed Unix tar file. To restore the executables, approximately 180 megabytes of disk space is required. To optionally install from the source code, approximately 200 megabytes additional disk space is required. o Backup any previous versions of TAE, LAS, ADAPS before the installation procedure is run. The previous versions can then be removed if the disk space is needed to install the new versions. o After the new version has been installed, any contributed or local code unique to the installation site should be extracted from the old version and placed in the appropriate directories. If using a supported platform and installing the binary distribution, follow the instructions listed below in Section 1.1.1. If planning to install and build the source distribution, skip forward to Section 1.1.2. 1.1.1 Binary Distribution Installation ====================================== The process for installing the binary distribution is as follows: o Download the proper tar file for your platform. The filename is of the form las_74_.tar.gz, where is "irix65" or "sun27". o Create a directory in which you wish to install LAS, and move into new directory. mkdir -p //las74 cd //las74 o Untar the contents using the command gzcat //las_74_.tar.gz | tar -xvpf - o Set the response variable. The response should be "las74" for general, non-development usage and "las74d" if development by a programmer is required. set response=las74 o Set environment variables. setenv EDCSOFT $PWD setenv TAE $EDCSOFT/tae source env/las/assign/lasinit Note: o Do not use upper case letters anywhere within the path name. TAE is case insensitive and will assume all lower case. 1.1.2 Source Distribution Installation ====================================== The entire system can be rebuilt from source code if desired. This is only necessary for non-supported platforms. Some of the modules require support libraries that are not distibuted with LAS/ADAPS. The external libraries must be installed (or linked) to a directory that is known by the corresponding LAS/ADAPS module. Below is a list of the modules that require external libraries, the associated library and version number that are known to be compatible, and the directory location in which LAS will expect the library to reside. If your site does not require these modules, you may simply ignore any errors associated with these modules occurring during the build process. LAS/ADAPS module Required library Location ---------------- ---------------- -------- L7HDF2LAS HDF 4.1r3 $EDCSOFT/build/hdf/include /lib PDS ODL Label Library $EDCSOFT/build/odl/include Light v0.5 /lib SPOTHDF2LAS HDF 4.1r3 The HDF library can be downloaded from the National Center for Supercomputing Applications (NCSA) at http://hdf.ncsa.uiuc.edu/hdf4.html. The process for building from source is as follows: o Download the source tar file. The filename is las_74_src.tar.gz. o Create a directory in which you wish to install LAS, and move into new directory. mkdir -p //las74 cd //las74 o Untar the contents using a command of the form (may vary from system to system). tar -xvpzf //las_74_src.tar.gz (GNU tar) or gzcat //las_74_src.tar.gz | tar -xvpf - or gzip -dc //las_74_src.tar.gz | tar -xvpf - or gunzip -c //las_74_src.tar.gz | tar -xvpf - o If you have installed a previous version of LAS, remove all environment variable assignments to this previous version. These assignments are normally set in your .login or .cshrc file. The script src/las/env/install/lasenv_off.csh may be helpful. It must be run using the command source src/las/env/install/lasenv_off.csh o Ensure that the C compiler, C preprocessor, Fortran compiler, and archive commands (i.e., cc, cpp, f77, and ar) are available via your $PATH environment variable. o Ensure that all of the required support libraries listed above can be found in their designated locations. (Note that $EDCSOFT will be set to the //las74 directory.) These libraries are only necessary if you want to build the associated applications. o If required, edit the top of the source install script src/las/env/install/lasinstall_src.csh to change any variables that may be user-modified. Note the list of application files that may also need modifications. o Run the source install script source src/las/env/install/lasinstall_src.csh The following describes the process accomplished by lasinstall_src: - Build TAE. - Create LAS/ADAPS build/run directories. - Build LAS/ADAPS. - Set up LAS environment variables. The build process may take from one half hour to several hours, depending on your system. o Review tae/build.log and src/build.log to ensure that no errors were encountered. Notes: o Do not use upper case letters anywhere within the path name. TAE is case insensitive and will assume all lower case. o Unsupported systems may require modifications and/or additions to several include files. See Appendix B for more information. 1.2 Environment Variable Assignments ==================================== The environment variables TAE and EDCSOFT need to be set to define access to LAS 7.4. (For source installation (Section 1.1.2), this has already been done.) % setenv EDCSOFT /your_path_name/las74 (Root directory for LAS 7.4) % setenv TAE $EDCSOFT/tae (Root directory for the TAE package) The variable "response" is used to denote whether the user plans to do software development within the LAS framework. If no development is to take place, execute % set response=las74 Otherwise, if development by a programmer is required, execute % set response=las74d The other required environment variables for LAS 7.4 are set by executing the command: % source $EDCSOFT/env/las/assign/lasinit Environment variables to LAS 7.4, will be setup when lasinit has been executed. Usually, the previously stated commands are placed in a masterlog file and the user's .login file. See Section 2.0. At this point LAS 7.4 is installed. The user can type "las" at the operating system prompt to enter the LAS environment. To exit LAS and return to the operating system, the user can type "exit". See the LAS Overview for detailed information about getting started. Example: % (Operating system prompt) % las (Enter the LAS environment) LAS74> (LAS environment prompt) LAS74>exit (Exit the LAS environment) % (Back to the operating system prompt) 1.3 Installation Notes ====================== o To run tape ingest or output routines, you will need to make some manual modifications to a tape configuration file. The $LASTABLES/tape.config file contains tape drive information for various systems and drive types. Modify this file for your site following the instructions within this file before running any tape I/O applications. Refer to the Programmer's Guide, Tape I/O section, for more specific information relating to tape operations. o The file $LASBASE/lasgbls.pdf may optionally be modified to set site specific TAE global variables. o For Sun installations: If you encounter problems running the XID application, it may be necessary to create a link pointing to the X color database. XID looks for the X color database in the directory /usr/lib/X11 for the file rgb.txt. On Sun systems, this file may be in /usr/openwin/lib/X11, /opt/X11R5/usr/lib/X11, or other directory as set up by the System Administrator. Have your System Administrator create a link from /usr/lib/X11 to one of the other directories listed. 2. Introduction to Login Files ****************************** Anyone who wants to use the LAS system must ensure that several UNIX environment variables are set. Some of these point to directories used by TAE, while others point to directories used by LAS. The easiest way to get these variables set is to place commands in the user's login file which will execute existing shell scripts/command files to define them. 2.1 UNIX Login File =================== On UNIX systems, the .login file should contain the following lines if a masterlog is being used: if ( -r /your_path_name/las74/env/las/assign/masterlog) then eval `/your_path_name/las74/env/las/assign/masterlog response \ comfile las74` eval $comfile else echo "Cannot prompt," \ "/your_path_name/las74/env/las/assign/masterlog does not exist." endif where "/your_path_name/" specifies the directory used for the installation. The first line looks for the file /your_path_name/las74/env/las/assign/masterlog. Masterlog prompts the user for a subsystem (LAS74) and sends back the response and commands to be evaluated. The next line executes the commands placed in the shell variable comfile by masterlog. These commands execute shell scripts to define the necessary environment variables. Samples of these shell scripts are given in Section 2.2. A masterlog file is included within the distribution. You will need to modify this file before using it. Edit $EDCSOFT/env/las/assign/masterlog. At the location in the file which states "Site specific modifications go here", change the tae and edcsoft symbols to "/your_path_name/" as used during the installation. 2.2 Sample Shell Scripts for Defining Environment Variables =========================================================== These are examples of scripts used for setting up UNIX environment variables for LAS. They are included here for illustrative purposes and are subject to change. oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Example of masterlog: oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo #!/bin/csh -f # # FUNCTION: masterlog # # PURPOSE: Set up the necessary environment for the Land Analysis System (LAS). # This function requires one argument and can optionally except a # second. The first must the name of a csh variable which will be set # to the user's response for the desired system setup. The second # argument, if present, will be used as the user's initial response # to the type of system to be set up. # # The output consists of several csh commands which will set up the # desired system. This function should be run as follows: # # eval `masterlog response` # # or # # eval `masterlog response las74d` # # After this command has been executed, the shell variable $response # will contain the user's response to the question asking which # system should be set up. # # #---------------------------------------------------------- # Ensure the correct number of arguments have been supplied #---------------------------------------------------------- if ($#argv < 4) then echo 'echo "usage: masterlog ";' echo 'echo "";' echo 'echo " Where is a shell variable, usually response,";' echo 'echo " is a shell variable, usually comfile, ";' echo 'echo " is an optional argument designating the desired";' echo 'echo " system, and is the full directory";' echo 'echo " path to use for the installation (overrides default";' echo 'echo " path).";' echo 'echo "";' echo 'echo " Example: masterlog response comfile las74d /home/las";' exit 1 endif #----------------------------------------------------------------------------- # Get the desired system. If there is no terminal associated with the current # session and the desired system was not specified as argument two, assume # LAS74. #----------------------------------------------------------------------------- tty -s set response = "$3" set inspath = "$4" set response = `echo $response | tr "[a-z]" "[A-Z]"` #----------------------------------------------------------------------------- # Site specific modifications go here #----------------------------------------------------------------------------- set edcsoft = $inspath set tae = $edcsoft/tae #------------------------------------------- # Set up the commands for the desired system #------------------------------------------- switch ($response) case LAS74: case LAS74D: set cmds = ( \ set $1 = $response; \ setenv TAE $tae; \ setenv EDCSOFT $edcsoft; \ source $edcsoft/env/las/assign/lasinit; \ set $2 = true \ ) breaksw case TAE: set cmds = ( \ set $1 = $response; \ setenv TAE $tae; \ source $TAE/bin/csh/las.setup; \ set $2 = true \ ) breaksw case UNIX: default: set cmds = ( \ set $1 = $response; \ set $2 = true \ ) breaksw endsw #---------------------------- # Echo the necessary commands #---------------------------- echo $cmds oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Example of lasinit: oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo #------------------------------------------------------------------------------- # This script defines the necessary environment variables for the LAS package. # This file should be source'd and not executed. # # LAS70,LAS71: User assignments for all executable commands. # LAS70D,LAS71D:Programmer assignments for development directories. # # USGS/EROS Data Center, 05/18/94 #------------------------------------------------------------------------------- #------------------------ # Ensure $response is set #------------------------ if (! $?response) then echo '$response must be set to LAS74 or LAS74D.' exit 1 endif #--------------------------------------------------- # Ensure the necessary environment variables are set #--------------------------------------------------- if ((! $?EDCSOFT) || (! $?TAE)) then echo '$EDCSOFT and $TAE must be set.' exit 1 endif #------------------------------------ # Set the LASSYS environment variable #------------------------------------ set tmp = `uname -a | awk '{print $1}' | tr "[A-Z]" "[a-z]"` switch ($tmp) case irix*: setenv LASSYS sgi-irx breaksw case sunos: setenv LASSYS sun-bsd breaksw case linux: setenv LASSYS linux breaksw default: echo 'Unknown operating system. Contact system administrator.' exit 1 breaksw endsw #----------------------------------------------------------------- # Set the appropriate environment variables according to $response #----------------------------------------------------------------- set response = `echo $response | tr "[a-z]" "[A-Z]"` switch ("$response") case LAS74: source $EDCSOFT/env/las/assign/usrassign breaksw case LAS74D: source $EDCSOFT/env/las/assign/usrassign source $EDCSOFT/env/las/assign/pgmassign breaksw default: echo '$response must be set to LAS74 or LAS74D.' exit 1 breaksw endsw #-------------------------------------------- # Set the environment variables for TAE users #-------------------------------------------- source $TAE/bin/csh/las.setup #---------------------------------- # Create an alias for las and las74 #---------------------------------- alias tae taetm alias las taetm alias las74 taetm #------------------------------------------------------------------ # Set an environment variable indicating the user's LAS environment #------------------------------------------------------------------ setenv LAS_RESP $response #---------------------------------------------------------- # Set an environment variable for the LAS system definition #---------------------------------------------------------- setenv SYSDEF "LAS74" oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Example of LAS usrassign: oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo #------------------------------------------------------------------------------- # This script sets the necessary environment variables for ADAPS and LAS users. # Because it sets environment variables this file should be source'd and not # executed. UNIX evironment variables are not exported to a parent shell. # # USGS/EROS Data Center, 05/18/94 #------------------------------------------------------------------------------- #------------------------ # ADAPS Environment Paths #------------------------ setenv ADAPSASSIGN $EDCSOFT/env/adaps/assign setenv ADAPSTABLES $EDCSOFT/env/adaps/tables #----------------------- # ADAPS Executable Paths #----------------------- setenv ADAPSBASE $EDCSOFT/run/adaps/base setenv ADAPSCONTRIB $EDCSOFT/run/adaps/contrib setenv ADAPSDOC $EDCSOFT/run/las/doc/adaps setenv ADAPSLOCAL $EDCSOFT/run/adaps/local #------------------------------------------------------------------------- # ADAPS Processing Directories. These are not used at most installations. #------------------------------------------------------------------------- setenv ADAPSACQ $EDCSOFT/avhrr/acquire setenv ADAPSARC $EDCSOFT/avhrr/archive setenv ADAPSBRW $EDCSOFT/avhrr/browse setenv ADAPSDB $EDCSOFT/avhrr/dbdata setenv ADAPSDBTMP $EDCSOFT/avhrr/dbtemp setenv ADAPSERR $EDCSOFT/avhrr/error setenv ADAPSFAX $EDCSOFT/avhrr/fax setenv ADAPSIMG $EDCSOFT/avhrr/images setenv ADAPSING $EDCSOFT/avhrr/ingest setenv ADAPSLOG $EDCSOFT/avhrr/log setenv ADAPSMIC $EDCSOFT/avhrr/micro setenv ADAPSORB $EDCSOFT/avhrr/orbit setenv ADAPSPROD $EDCSOFT/avhrr/prod #------------------- # World Data Bank II #------------------- setenv WDBII $EDCSOFT/avhrr/wdb2 #---------------------- # LAS Environment Paths #---------------------- setenv APPLOG $EDCSOFT/env/las/logfiles setenv LASASSIGN $EDCSOFT/env/las/assign setenv LASTABLES $EDCSOFT/env/las/tables setenv WORCONFIG $EDCSOFT/env/las/tables #--------------------- # LAS Executable Paths #--------------------- setenv LASBASE $EDCSOFT/run/las/base setenv LASCONTRIB $EDCSOFT/run/las/contrib setenv LASDITTY $EDCSOFT/run/las/ditty setenv LASDITTO $EDCSOFT/run/las/ditto setenv LASDOC $EDCSOFT/run/las/doc setenv LASLOCAL $EDCSOFT/run/las/local setenv LASTOOLS $EDCSOFT/run/bin setenv LASDDP $EDCSOFT/run/las/ddp #------------------------------------------ # Environmet variable for drainage software #------------------------------------------ setenv LASDRAIN $EDCSOFT/run/las/local #------------------------------------------------------- # Add LASTOOLS and /usr/local/gnu/bin to the user's path #------------------------------------------------------- set path = ($path $LASTOOLS) if (-d /usr/local/gnu/bin) set path = ($path /usr/local/gnu/bin) #----------------------------- # Set aliases #----------------------------- alias xid $LASBASE/xid alias tiepts $LASBASE/tiepts alias xplot $ADAPSBASE/xplot alias xsched $ADAPSBASE/xsched #-------------------------------------------- # Set up the correct data type representation #-------------------------------------------- setenv DATASYS ieee-std #------------------------------------------------------------------------------- # Add the LASTOOLS directory to the XUSERFILESEARCHPATH environment variable. # This allows TIEPTS to pick up the appropriate resource file. # #------------------------------------------------------------------------------- if ($?XUSERFILESEARCHPATH) then setenv XUSERFILESEARCHPATH ${XUSERFILESEARCHPATH}:$LASTOOLS/%N.ad else setenv XUSERFILESEARCHPATH $LASTOOLS/%N.ad endif oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo Example of LAS pgmassign: oooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo #------------------------------------------------------------------------------- # This script sets the necessary environment variables for LAS programmers. # This file should be source'd and not executed. # # USGS/EROS Data Center, 06/05/96 #------------------------------------------------------------------------------- #--------------------------------------------------------------------------- # Determine the root directory needed for the enviroment variables used to # build applications. The include files and libraries are only located on # those system that we compile on. Other systems of the same type must have # the appropriate disk cross mounted. #--------------------------------------------------------------------------- setenv ADAPSINCLUDE $EDCSOFT/build/adaps/include setenv ADAPSLIB $EDCSOFT/build/adaps/lib setenv LASINCLUDE $EDCSOFT/build/las/include setenv LASLIB $EDCSOFT/build/las/lib setenv CONTRIBINCLUDE $EDCSOFT/build/contrib/include setenv CONTRIBLIB $EDCSOFT/build/contrib/lib #------------------------------------------------------------------------- # Set the environment variables that control the tape I/O network software #------------------------------------------------------------------------- setenv TPLIB '$(LASLIB)/tapeio.a' setenv WORTPMTREQ 1 setenv NETINCLUDE _NOT_USED_ #-------------------------------------------------- # Set the environment variables for public software #-------------------------------------------------- source $EDCSOFT/env/las/assign/pubassign #------------------------------------------------------------ # Set TRLIB appropriately. If /etc/termcap exists, set it to # -ltermlib. #------------------------------------------------------------ if ("$LASSYS" == "linux") then setenv TRLIB "-lcurses" else if (-r /etc/termcap) then setenv TRLIB -ltermlib else if ("$LASSYS" == "sgi-irx") then setenv TRLIB "-lcurses" endif #-------------------------------------------- # Set compiler flags for K&R C and Fortran 77 #-------------------------------------------- switch ($LASSYS) case sun-bsd: if (! $?CC) then setenv CC gcc endif if (! $?FC) then setenv FC g77 endif if (! $?FLINKS) then setenv FLINKS endif if (! $?CFLAGS) then setenv CFLAGS "-O -s -D_FILE_OFFSET_BITS=64 -funsigned-char -fwritable-strings -Wall" # NOTE: If your sun does not support 64-bit file systems, remove # the -D_FILE_OFFSET_BITS=64 in the CFLAGS endif if (! $?FFLAGS) then setenv FFLAGS "-O -s -fno-second-underscore" endif if (! $?LD_OPTIONS) then setenv LD_OPTIONS "-lsocket -lnsl -ldl" endif breaksw case sgi-irx: if (! $?CC) then setenv CC cc endif if (! $?FC) then setenv FC f77 endif if (! $?FLINKS) then setenv FLINKS "" endif if (! $?CFLAGS) then setenv CFLAGS "-O -s" endif if (! $?FFLAGS) then setenv FFLAGS "-O -s" endif if (! $?SGI_CC) then setenv SGI_CC -xansi endif breaksw case linux: if (! $?CC) then setenv CC gcc endif if (! $?FC) then setenv FC f77 endif if (! $?FLINKS) then setenv FLINKS "" endif if (! $?CFLAGS) then setenv CFLAGS "-O -funsigned-char -fwritable-strings -Wall" endif if (! $?FFLAGS) then setenv FFLAGS "-O -fno-second-underscore" endif if (! $?LD_OPTIONS) then setenv LD_OPTIONS "-lsocket -lnsl -ldl" endif breaksw endsw #------------------------------------- # Set up the appropriate library flags #------------------------------------- switch (`uname -s`) case IRIX*: setenv AR "/bin/ar" setenv ARFLAGS "rcsl" breaksw case SunOS: setenv AR "/usr/ccs/bin/ar" setenv ARFLAGS "rcs" breaksw endsw #-------------------------------------------------------- # Set environment variables for compiling C++ source code #-------------------------------------------------------- switch (`uname -s`) case IRIX*: if (! $?CPP) then setenv CPP CC #IRIX make defines CXX=CC endif if (! $?CPPFLAGS) then setenv CPPFLAGS -O #IRIX make defines CXXFLAGS=-O endif breaksw default: if (! $?CPP) then setenv CPP g++ endif if (! $?CPPFLAGS) then setenv CPPFLAGS "-O -D_FILE_OFFSET_BITS=64" endif endsw 3. Conventions for Directory Structures *************************************** 1. Environment variables should point to directories, not to files or libraries. 2. Environment variables should not differ between like systems at different installations. 3. A given directory should contain either all directories or all files -- not a mixture of both. An exception to this is the build file or Makefile. 4. Menus will be treated similar to the way procedure PDF's are treated: They will be in the source directory and installed in the run directory just as any other function would be. Appendix A: Caveats ******************** The following is a list of items that affect the system as a whole. Problems with individual application modules are not addressed here. 1. The base directories ($LASBASE, $ADAPSBASE) contain officially released "baseline" applications that are supported by the Software Engineering Department. All modules within these directories should work at all sites. The local directories ($LASLOCAL, $ADAPSLOCAL) include applications that are primarily used at the EDC, use EDC specific hardware, or require site-specific modifications. They are not typically supported outside of the EDC. The contrib directories ($LASCONTRIB, $ADAPSCONTRIB) contain modules that have not been formally tested. Nor do they conform to the software standards (documentation and functionality) of the Software Engineering Department. The ditty and ddp directories ($LASDITTY, $LASDDP) contain modules and procedure definition files (PDF's) contributed by production personnel. The local, contrib, ditty, and ddp directories are included for informational purposes and should not be considered part of the LAS Baseline Release. 2. Equations that are found in the Description/Algorithm section of the user guides have not been standardized and, therefore, may be confusing. 3. Some applications make use of a public domain software package called gnuplot that is not included within the LAS distribution. Gnuplot is available through anonymous ftp at ftp.dartmouth.edu (129.170.16.79) in pub/gnuplot. Appendix B: Installation Notes for Unsupported Systems ****************************************************** The following is a list of helpful hints when porting LAS to a computer that is not supported. This list was compiled from the phone support given to sites that are porting LAS to an unsupported system. Therefore, this list is not comprehensive. 1. Some of the source code has been placed within ifdef statements. As a consequence, files with ifdef statements need to be edited in order to build on an unsupported computer. We know of the following: $EDCSOFT/src/las/base/include/typlim.h $EDCSOFT/src/las/base/include/typlim.mfi $EDCSOFT/src/las/base/include/imageio.h $EDCSOFT/src/las/base/include/imageio.mfi $EDCSOFT/src/bin/fame/faim $EDCSOFT/src/las/base/include/sysdef.h $EDCSOFT/src/las/base/include/sysdef.mfi $EDCSOFT/src/las/base/include/tapeio.h $EDCSOFT/src/las/base/include/tapeio.mfi $EDCSOFT/src/las/base/support/pixman/c_pxsys.c $EDCSOFT/src/las/base/support/util/c_sysset.c $EDCSOFT/src/las/base/support/ddr/c_comsys.c $EDCSOFT/src/las/base/support/ddr/c_getsys.c 2. The supports for the tapeio modules may have to be revised for the specific drivers of the unsupported system. Appendix C: Documentation ************************* The documentation for LAS 7.4 is contained on-line in HTML (Hyper-Text Markup Language) format. After LAS 7.4 has been installed, you can access the documentation by typing lasdoc at the UNIX prompt. Note: If a browser other than Mosaic is used, you must modify $LASTOOLS/lasdoc to reflect this change. ******** LAS Disclaimer ******** The USGS EROS Data Center (EDC) has provided LAS to outside users since 1983 and continues to provide limited support. Originally, the LAS and ADAPS system was developed to support research and development of image processing applications within NASA and the USGS and has migrated to provide special services for EDC image production. Since the software is public-domain, it is available to any government or private institution. As the popularity of these systems has grown, so has the impact of external support on EDC resources. This impact has greatly hampered the continued development of EDC's internal image processing capabilities. As a result, EDC no longer provides external support. Occasionally, limited support will be considered for agencies with whom we have cooperative agreements or mutual goals. All requests for copies of these software packages must be made formally. The request should state that you have read and understand this disclaimer. Distribution is now made available through the world wide web, unless otherwise requested. LAS WWW address: http://edcwww.cr.usgs.gov/programs/sddm/lasdist. Other requests should be mailed or faxed to: LAS Administrator Software Engineering USGS EROS Data Center Sioux Falls, SD 57198. FAX: 605-594-6940. ********************************* The following packages are included: LAS - The Land Analysis System is an image processing, image analysis and raster GIS system originally developed cooperatively by NASA's Goddard Space Flight Center (GSFC) and the U.S. Geological Survey's EROS Data Center (EDC). ADAPS - The AVHRR Data Acquisition and Processing System is a reception, processing, and product generation system for AVHRR imagery from NOAA satellites. ADAPS was built using the LAS system and additional capabilities. XID - The X Image Display program allows users to display and interactively manipulate images on display terminals running the X Window System. TIEPTS - Allows users to interactively select tie points between unregistered images and a reference source, such as a registered image, a base map, or vector data. Documentation is provided in Hyper Text Markup Language (HTML). If you have questions, send email to edclasadmin@usgs.gov.