文件列表:

DATA\#aa# (6, 2003-04-07)
DATA\.#aa (0, 2003-04-07)
DATA\aviris.flt (459055, 2000-11-28)
DATA\BMP97_01.ASC (24056543, 2000-11-28)
DATA\BMP97_01.BIN (9252540, 2003-04-07)
DATA\BMP97_15.ASC (893819, 2000-11-28)
DATA\BMP97_15.BIN (343800, 2003-04-07)
DATA\cebchkur.dat (924273, 2000-11-28)
DATA\CFC96_15.ASC (15912, 2000-11-28)
DATA\CFCBMP96.ASC (207012, 2000-11-28)
DATA\chkur.dat (1111061, 2000-11-28)
DATA\CORK01.ASC (4625083, 2000-11-28)
DATA\CORK01.BIN (1577240, 2007-04-05)
DATA\CORK15.ASC (1341347, 2000-11-28)
DATA\CORK15.BIN (457588, 2007-04-05)
DATA\newkur.dat (1049103, 2000-11-28)
DATA\PARAM.LST (5589, 2003-04-07)
DATA\refbkg (5136, 2000-11-28)
DATA\thkur.dat (926493, 2000-11-28)
DATA\MOLBMP_Src\MOLBMP.for (20324, 2000-11-28)
DATA\MOLBMP_Src\MOLBMP.exe (565306, 2007-04-05)
DATA\MOLBMP_Src\MOLBMP.dsw (535, 2007-04-05)
DATA\MOLBMP_Src\MOLBMP.dsp (3759, 2007-04-05)
DATA\MOLBMP_Src\MOLBMP.plg (1104, 2007-04-05)
DATA\MOLBMP_Src\MOLBMP.ncb (41984, 2007-04-12)
DATA\MOLBMP_Src\MOLBMP.opt (48640, 2007-04-12)
DATA\CKBIN_Src\CKBIN.ncb (41984, 2007-04-12)
DATA\CKBIN_Src\CKBIN.for (7656, 2000-11-28)
DATA\CKBIN_Src\CKBIN.exe (159715, 2003-04-07)
DATA\CKBIN_Src\CKBIN.dsw (533, 2007-04-05)
DATA\CKBIN_Src\CKBIN.dsp (3747, 2007-04-05)
DATA\CKBIN_Src\CKBIN.plg (739, 2007-04-05)
DATA\CKBIN_Src\CKBIN.opt (48640, 2007-04-12)
manual\aerosol.ps (56673, 2000-11-28)
manual\cloud.ps (100305, 2000-11-28)
manual\cloud.wp6 (66141, 2000-11-28)
manual\npoessreport.doc (1917440, 2000-11-28)
manual\npoessreport.ps (1339372, 2000-11-28)
manual\npoessreport.wp5 (1165548, 2000-11-28)
... ...

MODTRAN INSTALLATION AND I/O FILES This appendix outlines the steps required to obtain, install and execute MODTRAN on a UNIX system. It also mentions a new input/output (I/O) file structure for MODTRAN. Therefore, this file should be read even if one has already installed the code, or is familiar with the installation process. This file is duplicated as the 'README' file in the MODTRAN distribution tar file. The top-level directory for modtran is now called something like mod40r00, mod37r00, etc. '40r00' refers to version 4.0, revision 00; whereas '37r00' refers to version 3.7, revision 00. INSTALLATION STEPS 1) Contact Gail Anderson (email: ganderson@PLH.AF.MIL) or Jim Chetwynd (chetwynd@plh.af.mil) and obtain the code (bundled into a single UNIX tar file and compressed to save space) from the ftp-site. 2) Unzip the file: 'gunzip mod40r00.tar.gz' will produce the tar file mod40r00.tar. The 'uncompress' command will also work. Then untar the file: 'tar -xvf mod40r00.tar'; this will build a MODTRAN directory structure, mod40r00, beneath the directory in which mod40r00.tar is located. The top-level directory, mod40r00, will contain these subdirectories: DATA, srcmod40, objmod40, TEST, novam, novam/src, and novam/test. 3) This step is for MODTRAN 4.0. Create correlated-K binary data files in the DATA subdirectory. In that directory, compile CKBIN.f (f77 CKBIN.f -o CKBIN.exe). Run CKBIN.exe; you will be prompted for a correlated-K ascii file name. Reply with 'CORK15.ASC', which should have been placed in this directory during the untar process. You will then be prompted for a binary name; reply with 'CORK15.BIN'. The program should announce a successful write and place the file in the DATA directory. Repeat for CORK01.ASC. 4) Create band model parameter files. Compile and run MOLBMP.f. Select a binary-to-ascii conversion. Although entering names of ascii files is possible, the files of interest should appear in the menu; select 3 for BMP97_15.ASC (MODTRAN 4.0 only), or 2 for BMP97_01.ASC. Another menu permits choosing output filenames; select the corresponding .BIN names. The outputs of the conversions specify the value, for your computer, of the RECL parameter. Note this number for the following step. 5) In the scrmod40 subdirectory, edit the file openbm.f. Find the 'RECL=' specification in the OPEN statement, and change its value to that specified by MOLBMP.exe for your platform and compiler. For an HP 9000/735, for example, the value will be 60; for an SGI, 15; for GNU and PC (Lahey and WATCOM) compilers, it is also 60. 6) The command 'make -f Makefile' will run the FORTRAN compiler (using 'Makefile') to create the executable file mod40.exe. Object files will be placed in the objmod40 directory. You may need to edit the makefile to set compiler parameters as needed by your compiler. Most likely, editing will not be needed. 7) This version of MODTRAN (version 3.7 and higher) has the ability to use the Navy Oceanic Vertical Aerosol Computer Model (NOVAM). If you need to use this code, NOVAM must be compiled and run before MODTRAN, producing output files for use when needed. The NOVAM files are located in the novam subdirectory tree under the top MODTRAN directory. Depending on need, not all users will require NOVAM. MODTRAN is independent of NOVAM. To prepare using NOVAM, go to the novam subdirectory. Execute the UNIX script file createnovamexecutable, which will create the NOVAM executable, novam.exe. NOVAM (novam.exe) reads input from novam.in, and writes output to novam.out. Three test case inputs are located in the novam/test subdirectory. Copy one into the novam.in file name, or create one, and use 'novam.exe' to create novam.out. Copy that to NOVAM.OUT (upper case) in the topmost MODTRAN directory, which contains mod40.exe, for use in runs requiring NOVAM data. 8) The TEST subdirectory holds a number of input files designed to exercise various parts of MODTRAN. The input files are named in the pattern *.tp5; output files have .tp6, .tp7, .tp8, .7sc, .7sr, .plt, .psc, .clr, and .chn extensions. Copy a *.tp5 file into tape5 in the top-level directory, and then 'mod40.exe' will run that case. The other way of running MODTRAN and naming I/O files make use of the file 'modroot.in' or 'MODROOT.IN' as described below. I/O FILES An attempt has been made in MODTRAN 3.7/4.0 to make it easier for the users to keep track of input and output (I/O) files. The need for easier file handling is evident to anyone who runs MODTRAN using different tape5's and wants to save the corresponding output files (the tape6's, pltout's, tape7's and so on). The problem is that every MODTRAN input file must be called 'tape5' and that earlier I/O files must be renamed to avoid overwriting them with newer files. The need for renaming is now avoided by creating a new MODTRAN input file (referred to as the root name file) called modroot.in or MODROOT.IN. If 'modroot.in' does not exist, 'MODROOT.IN' is looked for. If neither exists, MODTRAN I/O files are the usual ones: 'tape5', 'tape6', 'tape7', 'tape8', etc. If the root name file exists and contains a non-null string (maximum length is 80 characters), this string is treated as a prefix. It is suggested that this string contain no blanks other than leading and trailing ones. If the string consists of all blanks or is a null string, the I/O files are the usual ones. Otherwise, this string, stripped of all leading and trailing blacks, is used as a prefix for the I/O files whose names have mnemonic suffixes listed below. As an example, if the string is 'case1', the MODTRAN I/O files will have these names: case1.tp5 (corresponding to tape5) case1.tp6 (corresponding to tape6) case1.tp7 (corresponding to tape7) case1.tp8 (corresponding to tape8) case1.7sc (corresponding to tape7.scn case1.7sr (corresponding to tape7.scr) case1.plt (corresponding to pltout) case1.psc (corresponding to pltout.scn) case1.clr (corresponding to clrates in MODTRAN 4.0) case1.chn (corresponding to channels.out in MODTRAN 4.0)

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：