Once the software has been installed or upgraded, the user will need to make three additions to their user environment. The first is to add an environment variable called DIRSIG_HOME that points to the installed directory. The second step is to modify the program path so that the DIRSIG programs will be found. The final step is to make sure that the path to the dynamic libraries includes the DIRSIG library directory.
For example, if the user's default UNIX shell is C-shell (csh(1)) and DIRSIG model was installed into the /usr/local/dirsig directory, then the user should add the following lines to their .cshrc file:
setenv DIRSIG_HOME /usr/local/dirsig
set path = (${DIRSIG_HOME}/bin $path)
setenv LD_LIBRARY_PATH ${DIRSIG_HOME}/lib:${LD_LIBRARY_PATH}
Once you have made the changes to your .cshrc file you will need to either logout, or "source" your .cshrc file for the changes to take effect:
prompt> source ~/.cshrc
Since every user environment is slightly different, you should discuss with other users and your system administrator how to best make these changes to your user environment. For example, you may wish to place these commands in a central file that all users can source from their .cshrc file.
To verify that you correctly configured your user environment, you will want to try the following tests. First, we want to check if your executable path was correctly updated. The which command tells the user the full path corresponding a particular command. In this case, we want to make sure that we are running the main DIRSIG executable from the $DIRSIG_HOME/bin directory.
prompt> which dirsig
/usr/local/dirsig/bin/dirsig
If the person that installed the software did not make some optional links, then this command may return with the following error:
prompt> which dirsig
dirsig: Command not found.
or a similar message. In this case, you should try the following:
prompt> which dirsig-3.6.0
/usr/local/dirsig/bin/dirsig-3.6.0
If the optional executable links were made at installation time then either of these commands should work.
You are now sure that your UNIX shell knows where to find the executables. The next test is to make sure that you can run them. If you attempt to run the main executable without any options, the following usage method should be printed.
prompt> dirsig-3.6.0
DIRSIG - Digital Imaging and Remote Sensing Image Generation Model
Release 3.6.0
Build Date: Jun 16 2004 22:22:23
usage: usage: dirsig [options] <CFG filename>
where [options] are:
-standard standard mode
-preview preview image mode
-probe <filename> probe pixel mode
-restart <filename> restart mode
If you have problems at this point, refer to the Installation Troubleshooting section. If problems persist, you may wish to contact the person that installed the DIRSIG software.
Most of the tutorials require you to use one of the GUI editors. If your environment has been correctly set-up, then you should be able to start the bulldozer scene editor from the command line using the following syntax:
prompt> bulldozer
You should see a large graphical user interface start up which you can exit from. The fact that it correctly starts up is all that we care about at this point. If you have problems at this point, refer to the Installation Troubleshooting section. If problems persist, you may wish to contact the person that installed the DIRSIG software or a UNIX savvy user to help resolve your specific issue.