USF Home
Administrators
Hardware Status



Home
Getting Started
Support and Contacts
Software Portal
Documentation
Tutorial / Links
C Programming Linux MPI Programming
Get Account
Request Licensed Software
 

Changes between Version 20 and Version 21 of CMAQ-4.7

Show
Ignore:
Timestamp:
09/17/09 16:07:20 (2 months ago)
Author:
brs
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • CMAQ-4.7

    v20 v21  
    3838}}} 
    3939 
    40 == Building the Model Components == 
    41 These particular sections may need to be recompiled from time to time, depending on parameter changes.  For the sake of simplicity, we will go ahead and follow the tutorial instructions while building these modules.  These modules include `bcon`, `icon`, `jproc`, and `cctm`. 
    42  
    43 === 1. jproc === 
    44  a. Change directory to `$M3HOME/scripts/jproc` 
    45  b. Run the build script by executing 
    46     {{{ 
    47 [user@host jproc]$ ./bldit.jproc | tee bldit.jproc.out 
    48 }}} 
    49  c. Check the file `bldit.jproc.out` to ensure that there are no errors and that the executable compiled correctly.  You should see the file `JPROC_d1a_Linux2_x86_64pg` in the current directory. 
    50  d. Run the JPROC binary by running 
    51     {{{ 
    52 [user@host jproc]$ ./run.jproc 
    53 }}} 
    54  e. Data should be generated in the directory `$M3DATA/jproc` 
    55  
    56 === 2. icon === 
    57  a. Change directory to `$M3HOME/scripts/icon` 
    58  b. Run the build script by executing 
    59     {{{ 
    60 user@host icon]$ ./bldit.icon | tee bldit.icon.out 
    61 }}} 
    62  c. Check the file `bldit.icon.out` to ensure that there are no errors and that the executable compiled correctly.  You should see the file ICON_e1a_Linux2_x86_64pg in the current directory. 
    63  d. Run the ICON binary by running 
    64     {{{ 
    65 [user@host icon]$ ./run.icon 
    66 }}} 
    67  e. Data should be generated in the directory `$M3DATA/icon`.   
    68  
    69 === 3. bcon ===  
    70  a. Change directory to `$M3HOME/scripts/bcon` 
    71  b. Run the build script by executing 
    72     {{{ 
    73 user@host bcon]$ ./bldit.bcon | tee bldit.bcon.out 
    74 }}} 
    75  c. Check the file `bldit.bcon.out` to ensure that there are no errors and that the executable compiled correctly.  You should see the file `BCON_e1a_Linux2_x86_64pg` in the current directory. 
    76  d. Run the BCON binary by running 
    77     {{{ 
    78 [user@host bcon]$ ./run.bcon 
    79 }}} 
    80  e. Data should be generated in the directory `$M3DATA/bcon`. 
    81  
    82 === 4. cctm === 
    83  a. Change directory to `$M3HOME/scripts/cctm` 
    84  b. Run the build script by executing 
    85     {{{ 
    86 [user@host cctm]$ ./bldit.cctm | tee bldit.cctm.out 
    87 }}} 
    88  c. Ensure that the binary `CCTM_e3a_Linux2_x86_64ifort` was created in the current directory. 
    89   
    9040== Tutorial: Day 1, 32 km Run == 
    9141At this point, `cctm` should be ready to run the included 32 km tutorial.  You can follow these instructions for running it if you wish to test your installation or get a feel for the program.   
    … …  
    9343 a. Rename and submit the modified script to the queue by issuing  
    9444    {{{ 
     45[user@host ~]$ cd $M3HOME/scripts/cctm 
    9546[user@host cctm]$ cp run.cctm run.cctm.tut_day1 
    9647[user@host cctm]$ qsub run.cctm.tut_day1