Chapter VIII - Final Installation Steps
This chapter discusses optional steps that you may take after installing and testing the NONMEM system.
NONMEM VI 1.0 is available only in double precision. However, if in the future a single precision version is provided, the comments in this section may be useful.
All examples in this guide showed the installation and use of double precision versions of NONMEM, PREDPP, and NM-TRAN library subroutines. If only single precision is installed, it is simple to choose the other set of files from the distribution medium.
If you are installing both single and double precision versions, repeat Chapters III, IV, and VI for the other set of files from the distribution medium. Be aware that all NONMEM routines, all NM-TRAN library routines, and almost all PREDPP routines have the same names in both single and double precision versions. You must keep them separate! In UNIX, use separate directories. In CMS, use separate TXTLIBs. The TEXT files that users must have available locally (e.g., BLKDAT, ADVAN2, TRANS1, SSS) must also be kept separate. One strategy is to give them different names. For example:
In double precision: DBLKDAT TEXT A,
DADVAN2 TEXT A, etc.
In single precision: SBLKDAT TEXT A, SADVAN2 TEXT A,
etc.
Create a set of command files similar to those of Chapter VII, but using the new set of files and/or directories.
The problems used as test cases in this guide are all variations of the same problem, which uses a small amount of individual data. As the final stage in the installation of the NONMEM system, you may want to test the system with other problems, in particular those using larger population data sets. See Section 3 of Chapter X for a description of data provided on the distribution medium which may be useful for further testing.
When you are confident that the NONMEM system has been installed correctly and that no routines will need to be re-compiled, you may choose to erase the source code from the disk. Remember that you will have to read the source code back from the distribution medium if any changes are needed in the future. At the very least, you should retain copies of any source code that you have modified, e.g., NONMEM’s BLKDAT and BEGIN routines, so that the same modifications can be made if NONMEM must be re-installed.
If the installation has been performed by the automatic installation utilities SETUP or CDSETUP6.BAT, then all plain files (not directories!) in the NONMEM VI directory may be erased because all files of interest have been copied to sub-directories. UNIX "rm *" command and MS-DOS "erase *" commands may be used safely because they do not erase sub-directories. Source files (*.f and *.for) in sub-directories nm, pr, tr, and tl may also be erased.
To uninstall NONMEM VI, remove the NONMEM VI directory. You may use windows utilities to do this. Or, assuming that the NONMEM VI directory is called nmvi, the following commands may be used in the directory above nmvi:
UNIX:
rm -r -f nmvi
MS-DOS: |
With Windows 95:
deltree nmvi
With Windows NT: |
rmdir /s nmvi
If you have made any changes to the user’s path or to any system directories or files, these changes should be undone.
TOP
TABLE OF CONTENTS
NEXT CHAPTER ...