USER MANUAL SWAN Cycle III version 40.72A
USER MANUAL SWAN Cycle III version 40.72A USER MANUAL SWAN Cycle III version 40.72A
40 Chapter 4 in the file. =5: SWAN reads the map from top to bottom starting in the lower-left-hand corner of the map. A new column in the map should start on a new line in the file. The lay-out is as follows: 1,1 1,2 ... 1, myc+1 2,1 2,2 ... 2, myc+1 ... ... ... ... mxc+1,1 mxc+1,2 ... mxc+1, myc+1 [nhedf] [nhedt] [nhedvec] FREE FORMAT ’form’ =6: as [idla]=5 but a new column in the map need not start on a new line in the file. Default: [idla]=1. is the number of header lines at the start of the file. The text in the header lines is reproduced in the print file created by SWAN (see Section 3.3). The file may start with more header lines than [nhedf] because the start of the file is often also the start of a time step and possibly also of a vector variable (each having header lines, see below, [nhedt] and [nhedvec]). Default: [nhedf]=0. only if variable is time dependent: number of header lines in the file at the start of each time level. A time step may start with more header lines than [nhedt] because the variable may be a vector variable which has its own header lines (see below [nhedvec]). Default: [nhedt]=0. for each vector variable: number of header lines in the file at the start of each component (e.g., x− or y−component). Default: [nhedvec]=0. With this option the user indicates that the values are to be read with free format. Free format is a standard of the computer programming language FORTRAN. The free format conventions in reading from a file are almost the same as the conventions for the command syntax given elsewhere in this manual; the most important differences are: 1. There are no continuation marks, reading continues until the required number of data has been read, or until a slash (/) is encountered. 2. Input lines can be longer than 80 characters (depending on the operating system of the computer). 3. Comment is not allowed. With free format empty fields, repetition factors, and closure of a line by a slash, can be used. with this option the user indicates that fixed format (FORTRAN convention) is to be used when reading the values from file. The format can be defined in one of two ways, by giving the format number [idfm] or the format string ’form’. a user−specified format string according to Fortran convention, e.g.
Description of commands 41 ’(10X,12F5.0)’. =1: Format according to BODKAR convention (a standard of the Ministry of Transport and Public Works in the Netherlands). Format string: (10X,12F5.0). =5: Format (16F5.0), i.e. an input line consists of 16 fields of 5 places each. =6: Format (12F6.0), i.e. an input line consists of 12 fields of 6 places each. =8: Format (10F8.0), i.e. an input line consists of 10 fields of 8 places each. UNFORMATTED is a form of reading without conversion (binary files). Not recommended for ordinary use. If the file does not contain a sufficient number of data (i.e. less than the number of grid points of the input grid), SWAN will write an error message to the PRINT file, and if [itest]>0 (see command TEST) it will reproduce the data in the PRINT file, using the lay-out according to [idla]=1. This echo of the data to print file is also made if the READINP command is embedded between two TEST commands in the command file as follows: TEST 120 READINP .... TEST 0 WIND [vel] [dir] With this optional command the user indicates that the wind is constant. [vel] [dir] wind velocity at 10 m elevation (m/s). wind direction at 10 m elevation (in degrees, Cartesian or Nautical convention, see command SET). Both quantities are required if this command is used. Note that SWAN converts U 10 to U ∗ (see Scientific/Technical documentation). 4.5.3 Boundary and initial conditions | -> JONswap [gamma] | | | | -> PEAK | BOUNd SHAPespec < PM > < > & | | | MEAN | | GAUSs [sigfr] |
- 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 21 and 22: General definitions and remarks 13
- Page 23 and 24: General definitions and remarks 15
- Page 25 and 26: General definitions and remarks 17
- 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: Description of commands 39 [fac]
- Page 51 and 52: Description of commands 43 | | East
- Page 53 and 54: Description of commands 45 CONSTANT
- Page 55 and 56: Description of commands 47 points o
- Page 57 and 58: Description of commands 49 CRAY WKS
- 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
Description of commands 41<br />
’(10X,12F5.0)’.<br />
=1: Format according to BODKAR convention (a standard of the Ministry of<br />
Transport and Public Works in the Netherlands).<br />
Format string: (10X,12F5.0).<br />
=5: Format (16F5.0), i.e. an input line consists of 16 fields of 5 places each.<br />
=6: Format (12F6.0), i.e. an input line consists of 12 fields of 6 places each.<br />
=8: Format (10F8.0), i.e. an input line consists of 10 fields of 8 places each.<br />
UNFORMATTED is a form of reading without con<strong>version</strong> (binary files). Not recommended for<br />
ordinary use.<br />
If the file does not contain a sufficient number of data (i.e. less than the number of grid<br />
points of the input grid), <strong>SWAN</strong> will write an error message to the PRINT file, and if<br />
[itest]>0 (see command TEST) it will reproduce the data in the PRINT file, using the<br />
lay-out according to [idla]=1. This echo of the data to print file is also made if the<br />
READINP command is embedded between two TEST commands in the command file as<br />
follows:<br />
TEST 120<br />
READINP ....<br />
TEST 0<br />
WIND [vel] [dir]<br />
With this optional command the user indicates that the wind is constant.<br />
[vel]<br />
[dir]<br />
wind velocity at 10 m elevation (m/s).<br />
wind direction at 10 m elevation (in degrees, Cartesian or Nautical<br />
convention, see command SET).<br />
Both quantities are required if this command is used. Note that <strong>SWAN</strong> converts U 10 to U ∗<br />
(see Scientific/Technical documentation).<br />
4.5.3 Boundary and initial conditions<br />
| -> JONswap [gamma] |<br />
| | | -> PEAK |<br />
BOUNd SHAPespec < PM > < > &<br />
| | | MEAN |<br />
| GAUSs [sigfr] |
Change language