USER MANUAL SWAN Cycle III version 40.72A

More documents

Recommendations

Info

48 Chapter 4 With this optional command (not fully tested) a nested SWAN run can be carried out with the boundary conditions obtained from a coarse grid WAM run (WAM Cycle 4.5, source code as distributed by the Max Planck Institute in Hamburg). For this nested SWAN run the user has to give the CGRID command to define the computational grid before this BOUNDNEST2 command. The computational grid for SWAN in geographic space is the area bounded by the WAM coarse run nest (WAM boundary points of the nest). This implies that the boundaries of the WAM nest and the boundaries of the SWAN computational area should be (nearly) identical (see below). The spectral frequencies and directions of the coarse grid run do not have to coincide with the frequencies and directions used in the nested SWAN run (as defined in the CGRID command); SWAN will interpolate to these frequencies and directions in the nested run (see Section 2.6.3). Note that SWAN will accept output of a WAM output location only if the SWAN grid point on the nest boundary lies within a rectangle between two consecutive WAM output locations with a width equal to 0.1 times the distance between these output locations on either side of the line between these WAM output locations. This BOUNDNEST command is not available for 1D computations. Only boundary conditions generated by WAM Cycle 4.5 can be read properly by SWAN. A nested SWAN run may use either Cartesian or spherical coordinates. A curvi-linear grid may be used in the nested grid but the boundaries of this nest should conform to the rectangular course grid nest boundaries. WAM output files are unformatted (binary); this usually implies that WAM and SWAN have to run on the same computer. For those cases where WAM and SWAN run on different types of machines (binary files do not transfer properly), the option FREE is available in this command. The distributed version of WAM does not support the required free format nesting output; WAM users who modify WAM such that it can make formatted output, must modify WAM such that the files made by WAM can be read in free format, i.e. with at least a blank or comma between numbers. Note that the format of time and date that can be accepted by SWAN is YYMMDDHHMMSS (i.e. include seconds). ’fname’ a file name that contains all the names of WAM files containing the nested boundary conditions in time-sequence (usually one file per day). For example, the contents of ’fname’ can look like: CBO9212010000 CBO9212020000 CBO9212030000 .... SWAN will read the boundary data from these WAM files one after the other. UNFORMATTED the user indicates that the WAM files are binary.
Description of commands 49 CRAY WKSTAT FREE [xgc] [ygc] input will be read from file created by the CRAY version of WAM. input will be read from file created by the WORKSTATION version of WAM. the user indicates that the WAM files can be read with free format (these files are not generated standard by WAM!). if SWAN is used with Cartesian coordinates: longitude of south-west corner of SWAN computational grid (in degrees); if the south-west corner of the nest in the WAM computation is on land this value is required. If SWAN is used with spherical coordinates then [xgc] is ignored by SWAN. Default: the location of the first spectrum encountered in the nest file. if SWAN is used with Cartesian coordinates: longitude of south-west corner of SWAN computational grid (in degrees); if the south-west corner of the nest in the WAM computation is on land this value is required. If SWAN is used with spherical coordinates then [ygc] is ignored by SWAN. Default: the location of the first spectrum encountered in the nest file. | -> CLOSed | BOUNdnest3 WWIII ’fname’ < > [xgc] [ygc] | OPEN | CANNOT BE USED IN CASE OF UNSTRUCTURED GRIDS. With this optional command (not fully tested) a nested SWAN run can be carried out with the boundary conditions obtained from a coarse grid WAVEWATCH III run. For this nested SWAN run the user has to give the CGRID command to define the computational grid before this BOUNDNEST3 command. The computational grid for SWAN in geographic space is the area bounded by the WAVEWATCH III nest (WAVEWATCH III boundary points of the nest). This implies that the boundaries of the WAVEWATCH III nest and the boundaries of the SWAN computational area should be (nearly) identical (see below). The spectral frequencies and directions of the coarse grid run do not have to coincide with the frequencies and directions used in the nested SWAN run (as defined in the CGRID command); SWAN will interpolate to these frequencies and directions in the nested run (see Section 2.6.3). The output files of WAVEWATCH III (version 1.18 as distributed by NOAA) have to be created with the post-processor of WAVEWATCH III as output transfer files with WW_3 OUTP (output type 1 sub type 3) at the locations along the nest boundary (i.e. computational grid points in WAVE- WATCH III). These locations are equal to the corner points of the SWAN nested grid
Page 1:
SWAN USER MANUAL SWAN Cycle III ver
Page 5 and 6: Contents 1 Introduction 1 2 General
Page 7 and 8: TABLE . . . . . . . . . . . . . . .
Page 9 and 10: Chapter 1 Introduction The informat
Page 11 and 12: Chapter 2 General definitions and r
Page 13 and 14: General definitions and remarks 5 r
Page 15 and 16: General definitions and remarks 7 I
Page 17 and 18: which SWAN performs the computation
Page 19 and 20: General definitions and remarks 11
Page 27 and 28: Chapter 3 Input and output files 3.
Page 29 and 30: Chapter 4 Description of commands 4
Page 31 and 32: (h) Commands to write or plot outpu
Page 33 and 34: Description of commands 25 ’name
Page 35 and 36: Description of commands 27 Default:
Page 37 and 38: Description of commands 29 mesh. Th
Page 39 and 40: ⎛ ∆f = ⎝−1 + Description of
Page 41 and 42: Description of commands 33 • Easy
Page 43 and 44: Description of commands 35 grids ca
Page 45 and 46: Description of commands 37 y ′
Page 47 and 48: Description of commands 39 [fac]
Page 49 and 50: Description of commands 41 ’(10X,
Page 51 and 52: Description of commands 43 | | East
Page 53 and 54: Description of commands 45 CONSTANT
Page 55: Description of commands 47 points o
Page 59 and 60: Description of commands 51 This com
Page 61 and 62: Description of commands 53 | JANSse
Page 63 and 64: Description of commands 55 [Csh3] c
Page 65 and 66: Description of commands 57 [ursell]
Page 67 and 68: Description of commands 59 [slope]
Page 69 and 70: Description of commands 61 [cgmod]
Page 71 and 72: Description of commands 63 < > [lim
Page 73 and 74: Description of commands 65 SIGIMPL
Page 75 and 76: Description of commands 67 ’sname
Page 77 and 78: Description of commands 69 (see bel
Page 79 and 80: Description of commands 71 [alpn] d
Page 81 and 82: Description of commands 73 ‘long
Page 83 and 84: | HSign | | | | HSWEll | | | | DIR
Page 85 and 86: Description of commands 77 | WLENgt
Page 87 and 88: Description of commands 79 QP DEPTH
Page 89 and 90: Description of commands 81 [tbegblk
Page 91 and 92: Description of commands 83 OUTput [
Page 93 and 94: Description of commands 85 If SWAN
Page 95 and 96: Description of commands 87 ACCUR MX
Page 97 and 98: Appendix A Definitions of variables
Page 99 and 100: Definitions of variables 91 RPER co
Page 101 and 102: Definitions of variables 93 WLEN Th
Page 103 and 104: Appendix B Command syntax B.1 Comma
Page 105 and 106: Repetitions of keywords and/or othe
Page 107 and 108:
Required data and optional data Com
Page 109 and 110:
Appendix C File swan.edt Below the
Page 111 and 112:
File swan.edt 103 ! | -> DEFault !
Page 113 and 114:
File swan.edt 105 ! FRAME ’sname
Page 115 and 116:
Appendix D Spectrum files, input an
Page 117 and 118:
0.3892E-03 192.0 15.2 0.8007E-03 24
Page 119 and 120:
Spectrum files, input and output 11
Page 121 and 122:
Spectrum files, input and output 11
Page 123 and 124:
Bibliography [1] SWAN - Implementat
Page 125:
117 longitude, 8, 27, 49, 50, 85, 1
show all

USER MANUAL SWAN Cycle III version 40.72A

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?