close
Warning:
Can't synchronize with repository "(default)" (/srv/svn/repos/chg does not appear to be a Subversion repository.). Look in the Trac log for more information.
- Timestamp:
-
Jan 24, 2014, 5:03:42 PM (10 years ago)
- Author:
-
kyle
- Comment:
-
--
Legend:
- Unmodified
- Added
- Removed
- Modified
-
v1
|
v2
|
|
13 | 13 | - In the testcases directory, make a new directory called `Channeltest` |
14 | 14 | - cd to this directory, and type |
15 | | `cp /org/groups/chg/clint/PADCIRC/Projects/Channel_test/fort.14` |
16 | | `cp /org/groups/chg/clint/PADCIRC/Projects/Channel_test/fort.15` |
| 15 | {{{ |
| 16 | cp /org/groups/chg/clint/PADCIRC/Projects/Channel_test/fort.14 |
| 17 | cp /org/groups/chg/clint/PADCIRC/Projects/Channel_test/fort.15 |
| 18 | }}} |
17 | 19 | - Let's open `fort.14` and look at it. This file is generated by SMS or some grid generation program. It contains the mesh and boundary condition information. The first number is the number of elements, and the second is the number of nodes. For each node, it reads the node number, x and y coordinates, and bathymetry. (The coordinates may be in meters or in degrees (lon/lat). This is specified by the variable `ICS` in the `fort.15` file. `ICS=1` is for meters, `ICS=2` is for lon/lat or spherical coordinates. Bathymetry is always in meters). Then for each element, the `fort.14` file lists the nodes attached to that element (the connectivity table). The boundary condition information is at the bottom of the file. |
18 | 20 | - Open `fort.15`. It contains a lot of parameters, most of which you don't need to change. The parameters which you commonly will change are the following: |
… |
… |
|
28 | 30 | - Let's look at the output files: |
29 | 31 | * `fort.61` -- contains the station data for elevation |
30 | | * `fort.62 -- contains the station data for velocity |
| 32 | * `fort.62` -- contains the station data for velocity |
31 | 33 | * `fort.63` -- contains global elevation data |
32 | 34 | * `maxele.63` --contains the maximum elevation at each node over the entire simulation (useful mainly for storm surge applications). |
… |
… |
|
44 | 46 | * `HOTSTART`: say we want to go back and run this test case out to 10 days from where we left off. There are 2 hot start files, `fort.67` and `fort.68`. See which one was last written. Open the `fort.15` file, and change the parameter `IHOT` from `0` to either `67` or `68`. Change `RNDAY` to `10.0` and run `adcirc` again. It should pick up where it left off, it will include all of the output written up to the point of the hotstart. |
45 | 47 | |
| 48 | '''Note:''' In the `trunk_130423/work` directory, check the file `cmplrflags.mk` and look for the character string `intel-lonestar`. You will see a bunch of compiler options. Make sure the `-DDEBUG_WARN_ELEV` option is commented out, as so: |
| 49 | {{{ |
| 50 | DA := -DREAL8 -DLINUX -DCSCA #-DDEBUG_WARN_ELEV -fpe-all=0 -check all -traceback |
| 51 | DP := -DREAL8 -DLINUX -DCSCA -DCMPI #-DDEBUG_WARN_ELEV # -fpe-all=0 -check all -traceback |
| 52 | }}} |
| 53 | |
| 54 | You will need to recompile. |