swanmodel-users Mailing List for SWAN
Brought to you by:
mzijlema
Menu
▾
▴
swanmodel-users — for questions and discussion related to SWAN
You can subscribe to this list here.
| 2011 |
Jan
(1) |
Feb
(6) |
Mar
(9) |
Apr
(5) |
May
(15) |
Jun
(23) |
Jul
(6) |
Aug
(5) |
Sep
(4) |
Oct
(10) |
Nov
(5) |
Dec
(5) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2012 |
Jan
(7) |
Feb
(3) |
Mar
(4) |
Apr
(7) |
May
(16) |
Jun
(8) |
Jul
(7) |
Aug
(4) |
Sep
(2) |
Oct
(10) |
Nov
(12) |
Dec
(6) |
| 2013 |
Jan
(6) |
Feb
(1) |
Mar
(3) |
Apr
(5) |
May
|
Jun
(4) |
Jul
(4) |
Aug
(4) |
Sep
(3) |
Oct
(10) |
Nov
(6) |
Dec
(4) |
| 2014 |
Jan
(8) |
Feb
(7) |
Mar
(18) |
Apr
(21) |
May
(12) |
Jun
(12) |
Jul
(21) |
Aug
(10) |
Sep
(22) |
Oct
(6) |
Nov
(3) |
Dec
(12) |
| 2015 |
Jan
(12) |
Feb
(11) |
Mar
(8) |
Apr
(3) |
May
(5) |
Jun
(6) |
Jul
|
Aug
(3) |
Sep
(12) |
Oct
(10) |
Nov
(27) |
Dec
(18) |
| 2016 |
Jan
(16) |
Feb
(3) |
Mar
(7) |
Apr
(12) |
May
(6) |
Jun
(25) |
Jul
(2) |
Aug
(21) |
Sep
(36) |
Oct
(11) |
Nov
(10) |
Dec
(6) |
| 2017 |
Jan
(9) |
Feb
(1) |
Mar
(5) |
Apr
(8) |
May
(6) |
Jun
(6) |
Jul
(1) |
Aug
(2) |
Sep
(11) |
Oct
(4) |
Nov
(3) |
Dec
(2) |
| 2018 |
Jan
(6) |
Feb
|
Mar
(1) |
Apr
(8) |
May
(8) |
Jun
(5) |
Jul
(5) |
Aug
(8) |
Sep
(13) |
Oct
(5) |
Nov
(10) |
Dec
(2) |
| 2019 |
Jan
(14) |
Feb
(8) |
Mar
(14) |
Apr
(10) |
May
(7) |
Jun
(27) |
Jul
(37) |
Aug
(19) |
Sep
(4) |
Oct
(9) |
Nov
(9) |
Dec
|
| 2020 |
Jan
(14) |
Feb
(4) |
Mar
(2) |
Apr
(3) |
May
(1) |
Jun
(19) |
Jul
(2) |
Aug
|
Sep
(7) |
Oct
(4) |
Nov
|
Dec
(4) |
| 2021 |
Jan
(1) |
Feb
(10) |
Mar
(20) |
Apr
(15) |
May
(7) |
Jun
(11) |
Jul
(5) |
Aug
(14) |
Sep
(5) |
Oct
(15) |
Nov
(5) |
Dec
(4) |
| 2022 |
Jan
(6) |
Feb
(5) |
Mar
(11) |
Apr
(4) |
May
(1) |
Jun
(2) |
Jul
|
Aug
(9) |
Sep
(6) |
Oct
(3) |
Nov
(2) |
Dec
(7) |
| 2023 |
Jan
(2) |
Feb
(6) |
Mar
(9) |
Apr
(4) |
May
(3) |
Jun
(4) |
Jul
(3) |
Aug
(2) |
Sep
(4) |
Oct
(3) |
Nov
(4) |
Dec
|
| 2024 |
Jan
|
Feb
(3) |
Mar
(3) |
Apr
(1) |
May
|
Jun
(2) |
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(7) |
Nov
(2) |
Dec
|
| 2025 |
Jan
|
Feb
(2) |
Mar
(3) |
Apr
(2) |
May
(7) |
Jun
(1) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Yi L. <YL...@es...> - 2025-07-24 19:27:35
|
Hi SWAN Experts, Hope everyone is doing well. I am reaching out to ask if anyone has experience representing spatially varying vegetation height using SWAN. Based on my read of the manual, I understand that the vegetation density can vary spatially with the NPLANTS file, but the height is a fixed number with the command VEGETATION [height] [diamtr] [nstems] [draft]. The manual also says we can repeat the VEGETATION command as many vertical layers to be chosen, but I'm not sure how to implement that. I know it can be done (found a paper here Modeling wave attenuation induced by the vertical density variations of vegetation - ScienceDirect<https://www.sciencedirect.com/science/article/abs/pii/S0378383916300199>) but how do we define each vertical layer? Can we associate different NPLANTS file to different vertical layers so the model can represent riparian forest in some locations and tulle marsh in other locations? Any input would be helpful. Thanks in advance! [https://ars.els-cdn.com/content/image/1-s2.0-S0378383916X0004X-cov150h.gif]<https://www.sciencedirect.com/science/article/abs/pii/S0378383916300199> Modeling wave attenuation induced by the vertical density variations of vegetation - ScienceDirect<https://www.sciencedirect.com/science/article/abs/pii/S0378383916300199> The wave height decay rate, which was approximated by Dalrymple et al. (1984) as H s x H s 1 = 1 1 + αx where Hs (x) is the significant wave height at a horizontal distance x from the leading edge of the vegetation at G1, Hs,1 is the significant wave height at G1, and α is a damping factor. In this paper, the vegetation transmission coefficient, Kv(x), refers to the attenuation of the ... www.sciencedirect.com Best, Yi [ESA large.png] Yi Liu, PhD (she/her) Engineer III ESA | Environmental Science Associates San Francisco, CA (remote in NJ) 718.309.7972 cell YL...@es... | esassoc.com<https://esassoc.com/> ESA partners with clients and communities to drive sustainable, resilient, and equitable solutions that shape a better world. Let's stay in touch: Sign up for our newsletter.<https://esassoc.com/newsletter/> |
|
From: Paulo B. <pba...@in...> - 2025-06-09 14:40:25
|
Hello everyone,
I’ve been trying to compile SWAN with METIS support. The compilation completes successfully, but when I run an example with an unstructured grid, I keep encountering malloc-related errors.
Specifically, I’m running the f32harin simulation available on the SWAN website, and I get errors like these:
swan.exe: malloc.c:2617: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
Program received signal SIGABRT: Process abort signal.
Backtrace for this error:
swan.exe: malloc.c:2617: sysmalloc: Assertion `(old_top == initial_top (av) && old_size == 0) || ((unsigned long) (old_size) >= MINSIZE && prev_inuse (old_top) && ((unsigned long) old_end & (pagesize - 1)) == 0)' failed.
Program received signal SIGABRT: Process abort signal.
OR:
free(): invalid pointer
Program received signal SIGABRT: Process abort signal.
If I run the simulation with -mpi 1, it runs fine. However, as soon as I increase -mpi to 2 or more, these errors appear.
I have installed GKlib and METIS, and I’m compiling SWAN with the following commands:
cmake .. \
-DMETIS=ON \
-DMPI=ON \
-DCMAKE_C_COMPILER=mpicc \
-DNETCDF=ON \
-DCMAKE_INSTALL_PREFIX=${SWAN_HOME} && \
make && \
make install
Does anyone have any tips or suggestions to help resolve this issue? Any help would be greatly appreciated.
Thanks!
┌────────────────
│ Best regards,
│ Paulo Barbosa - Software Dev
│ pba...@in...
└────────────────
|
|
From: Henrique R. <hra...@gm...> - 2025-05-28 21:34:31
|
Hi Andrew, That does seem odd. Do you happen to have the spectrum that produced those values? Henrique Em qua., 28 de mai. de 2025, 07:14, Andrew Watson < and...@me...> escreveu: > Hi Henrique, > > Many thanks for your help with this, that worked perfectly so much > appreciated. > > However, I do have more more question. I have output a wind-sea and a > swell partition as well as total Hm0. I get the following results for one > example time-step: > > Hsig = 13.34418 > > HsPT01 = 13.49326 > > HsPT02 = 2.14402 > > Now, I would've though that Hsig = sqrt(HsPT01^2 + HsPT02^2), i.e. that > total Hm0 would equal the square root of the sum of the squares of the > wind-sea and swell partitions. However, this clearly isn't the case, the > answer instead being 13.6625. Can you explain why this discrepancy exists? > > Kind Regards, > > Andrew > > -- > Andrew Watson > Msc, Bsc, Csci, CMarSci, MIMarEST > Director & Senior Metocean Consultant > MetOceanWorks Ltd. > > Mobile +44 (0)7763 896635 > Registered in England and Wales Company Number 8078702 > > On 26/05/2025 23:56, Henrique Rapizo wrote: > > Hi Andrew, > > Try adding 'PTHS', for example: > 'QUANTity PTHS NOSWLL 2' > > Best regards > Henrique > > On Mon, 26 May 2025 at 11:02, Andrew Watson < > and...@me...> wrote: > >> Hi All, >> >> I am trying to set the number of output partitions using NOSWLL by >> including the following command: >> >> QUANT NOSWLL=2 >> >> However, this throws an error. Can anyone please give me some help about >> how to define the number of output partitions? >> >> Kind Regards, >> >> Andrew >> >> -- >> Andrew Watson >> Msc, Bsc, Csci, CMarSci, MIMarEST >> Director & Senior Metocean Consultant >> MetOceanWorks Ltd. >> >> Mobile +44 (0)7763 896635 >> Registered in England and Wales Company Number 8078702 >> >> _______________________________________________ >> swanmodel-users mailing list >> swa...@li... >> https://lists.sourceforge.net/lists/listinfo/swanmodel-users >> > |
|
From: Moniki M. <mm...@ap...> - 2025-05-28 15:54:21
|
Hello All, I am a new user of SWAN, and I am having issues with creating the boundary conditions. I created 12 segment files (these file structures are shown below "TPAR") (2), and some of my swan configurations as well (1). The error example is shown in (3). I'd like to know some ideas on how to create a boundary condition at SWAN, why the error below.. Many thanks in advance! 1) $ --- Computational Grid (100x100, ~0.012° resolution) --- CGRID REGULAR 107.8 0.19 1 1 99 99 CIRCLE 36 0.05 1.0 27 ....... $ --- Initial Condition --- INITIAL ZERO $ --- Boundary Conditions from ERA5 (12 segments) --- BOUND SHAPESPEC JONSWAP 3.3 PEAK DSPR DEGREES BOUNDSPEC SEGMENT IJ 1 1 1 6 CON FILE 'C:\SWAN\Gosong98\segment_1.txt' 1 BOUNDSPEC SEGMENT IJ 1 15 1 31 CON FILE 'C:\SWAN\Gosong98\segment_2.txt' 1.... 2) TPAR 19980101.000000 0.406844 4.935890 17.008274 26.353151 19980101.060000 0.433937 6.153664 17.414360 26.414999 19980101.120000 0.417535 6.223488 17.697376 26.846189 19980101.180000 0.396951 6.268898 18.114628 27.259344 3) COMPUTE NONSTAT 19980101.000000 21600.0 19980105.180000 ** Warning : sign. wave height at boundary is not positive Boundary data type TPAR processed, time: ************ Boundary data type TPAR processed, time: 0. ** Warning : sign. wave height at boundary is not positive Boundary data type TPAR processed, time: ************ Boundary data type TPAR processed, time: 0. -- Moniki Melo Senior Hydrometeorologist Applied Weather Associates, LLC *https://www.appliedweatherassociates.com/ <https://www.appliedweatherassociates.com/>* |
|
From: Andrew W. <and...@me...> - 2025-05-28 10:34:12
|
Hi Henrique, Many thanks for your help with this, that worked perfectly so much appreciated. However, I do have more more question. I have output a wind-sea and a swell partition as well as total Hm0. I get the following results for one example time-step: Hsig = 13.34418 HsPT01 = 13.49326 HsPT02 = 2.14402 Now, I would've though that Hsig = sqrt(HsPT01^2 + HsPT02^2), i.e. that total Hm0 would equal the square root of the sum of the squares of the wind-sea and swell partitions. However, this clearly isn't the case, the answer instead being 13.6625. Can you explain why this discrepancy exists? Kind Regards, Andrew -- Andrew Watson Msc, Bsc, Csci, CMarSci, MIMarEST Director & Senior Metocean Consultant MetOceanWorks Ltd. Mobile +44 (0)7763 896635 Registered in England and Wales Company Number 8078702 On 26/05/2025 23:56, Henrique Rapizo wrote: > Hi Andrew, > > Try adding 'PTHS', for example: > |'QUANTity PTHS NOSWLL 2'| > | > | > |Best regards| > |Henrique| > > On Mon, 26 May 2025 at 11:02, Andrew Watson > <and...@me...> wrote: > > Hi All, > > I am trying to set the number of output partitions using NOSWLL by > including the following command: > > QUANT NOSWLL=2 > > However, this throws an error. Can anyone please give me some help > about how to define the number of output partitions? > > Kind Regards, > > Andrew > > -- > Andrew Watson > Msc, Bsc, Csci, CMarSci, MIMarEST > Director & Senior Metocean Consultant > MetOceanWorks Ltd. > > Mobile +44 (0)7763 896635 > Registered in England and Wales Company Number 8078702 > > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > |
|
From: Moniki M. <mm...@ap...> - 2025-05-27 00:18:31
|
Hi All,
I am having several errors regarding the boundary conditions, could anyone
please give me some help about how to define the boundaries? The simulation
also fails when I do not define the boundary.
Thank you so much!
1
Execution started at 20250526.004150
---------------------------------------
SWAN
SIMULATION OF WAVES IN NEAR SHORE AREAS
VERSION NUMBER 41.51
---------------------------------------
$ SWAN Simulation (5-day test, Jan 1–5, 1998)
$ Version: SWAN 41.51
PROJECT 'GOSONG98' 'T100'
SET LEVEL 1.5
SET NAUT
SET MAXERR 2
MODE NONSTATIONARY
$ --- Computational Grid (100x100, ~0.012° resolution) ---
CGRID REGULAR 107.8 0.19 1 1 99 99 CIRCLE 36 0.05 1.0 27
Resolution in sigma-space: df/f = 0.1173
$ --- Bathymetry ---
INPGRID BOTTOM REGULAR 107.8 0.19 1 1 99 99
READINP BOTTOM 1 'C:\SWAN\Gosong98\gebco_depth_100x100_adjusted3.txt' 1 0
FREE
$ --- Wind (speed + direction, interleaved, nautical convention) ---
INPGRID WIND REGULAR 107.8 0.19 1 1 99 99 NONSTATIONARY 19980101.000000
21600.0 19980105.180000
READINP WIND 1 'C:\SWAN\Gosong98\wind_matrix_100x100_windonly.txt' 2 0 FREE
$ --- Water Level ---
INPGRID WLEV REGULAR 107.8 0.19 1 1 99 99 NONSTATIONARY 19980101.000000
21600.0 19980105.180000
READINP WLEV 1 'C:\SWAN\Gosong98\tide_1998_5day_100x100.txt' 1 0 FREE
$ --- Initial Condition ---
INITIAL ZERO
$ --- Boundary Conditions from ERA5 (12 segments) ---
BOUND SHAPESPEC JONSWAP 3.3 PEAK DSPR DEGREES
BOUNDSPEC SEGMENT XY 107.8 0.19 107.8 0.4930 FILE
'C:\SWAN\Gosong98\segment_1.txt' 1
** Error : invalid boundary point
segment point 107.80 0.49 grid 0.52 100.25 2 101
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_1.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 107.8 0.4930 107.8 0.7961 FILE
'C:\SWAN\Gosong98\segment_2.txt' 1
** Error : invalid boundary point
segment point 107.80 0.49 grid 0.52 100.25 2 101
** Error : invalid boundary point
segment point 107.80 0.80 grid 1.05 200.53 2 202
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_2.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 107.8 0.7961 107.8 1.0991 FILE
'C:\SWAN\Gosong98\segment_3.txt' 1
** Error : invalid boundary point
segment point 107.80 0.80 grid 1.05 200.53 2 202
** Error : invalid boundary point
segment point 107.80 1.10 grid 1.57 300.77 3 302
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_3.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 107.8 1.0991 107.8 1.435 FILE
'C:\SWAN\Gosong98\segment_4.txt' 1
** Error : invalid boundary point
segment point 107.80 1.10 grid 1.57 300.77 3 302
** Error : invalid boundary point
segment point 107.80 1.43 grid 2.15 411.91 3 413
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_4.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 107.8 0.19 108.0909 0.19 FILE
'C:\SWAN\Gosong98\segment_5.txt' 1
** Error : invalid boundary point
segment point 108.09 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : At least two points needed for a segment
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_5.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 108.0909 0.19 108.3818 0.19 FILE
'C:\SWAN\Gosong98\segment_6.txt' 1
** Error : invalid boundary point
segment point 108.09 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Error : invalid boundary point
segment point 108.38 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : No points on the boundaries found
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_6.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 108.3818 0.19 108.6727 0.19 FILE
'C:\SWAN\Gosong98\segment_7.txt' 1
** Error : invalid boundary point
segment point 108.38 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Error : invalid boundary point
segment point 108.67 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : No points on the boundaries found
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_7.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 108.6727 0.19 109.0 0.19 FILE
'C:\SWAN\Gosong98\segment_8.txt' 1
** Error : invalid boundary point
segment point 108.67 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Error : invalid boundary point
segment point 109.00 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : No points on the boundaries found
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_8.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 109.0 0.19 109.0 0.4930 FILE
'C:\SWAN\Gosong98\segment_9.txt' 1
** Error : invalid boundary point
segment point 109.00 0.19 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Error : invalid boundary point
segment point 109.00 0.49 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : No points on the boundaries found
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_9.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 109.0 0.4930 109.0 0.7961 FILE
'C:\SWAN\Gosong98\segment_10.txt' 1
** Error : invalid boundary point
segment point 109.00 0.49 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Error : invalid boundary point
segment point 109.00 0.80 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : No points on the boundaries found
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_10.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 109.0 0.7961 109.0 1.0991 FILE
'C:\SWAN\Gosong98\segment_11.txt' 1
** Error : invalid boundary point
segment point 109.00 0.80 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Error : invalid boundary point
segment point 109.00 1.10 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : No points on the boundaries found
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_11.txt
** Error : Data field skipped:1
BOUNDSPEC SEGMENT XY 109.0 1.0991 109.0 1.435 FILE
'C:\SWAN\Gosong98\segment_12.txt' 1
** Error : invalid boundary point
segment point 109.00 1.10 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Error : invalid boundary point
segment point 109.00 1.43 grid -99.00 -99.00 -98 -98
** Error : ( -99 -99) is outside computational grid
** Warning : No points on the boundaries found
** Error : Illegal keyword: FILE
** Error : Data field skipped:C:\SWAN\Gosong98\segment_12.txt
** Error : Data field skipped:1
$ --- Physics ---
GEN3 KOMEN
BREAKING CONSTANT ALPHA=1.0 GAMMA=0.73
FRICTION JONSWAP CFJON=0.038
$ --- Numerical Parameters ---
NUM ACCUR 0.1 2.0 0.2
$ --- Monitoring Points (on water) ---
POINTS 'NF1' 108.818182 0.655303
POINTS 'NF2' 108.830303 0.655303
POINTS 'NF3' 108.842424 0.655303
POINTS 'NF4' 108.854545 0.655303
TABLE 'NF1' HEADER 'nf1_100x100_v4.dat' HSIGN DIR TMM10 WIND
TABLE 'NF2' HEADER 'nf2_100x100_v4.dat' HSIGN DIR TMM10 WIND
TABLE 'NF3' HEADER 'nf3_100x100_v4.dat' HSIGN DIR TMM10 WIND
TABLE 'NF4' HEADER 'nf4_100x100_v4.dat' HSIGN DIR TMM10 WIND
$ --- Grid Output ---
BLOCK 'COMPGRID' HEADER 'swan_output_1998_test5day_100x100_v4.dat' HSIGN
DIR TMM10 WIND
$ --- Run the Model ---
COMPUTE NONSTAT 19980101.000000 21600.0 19980105.180000
Time of computation -> 19980101.060000 in sec: 21600.
----------------------------------------------------------------
COMPUTATIONAL PART OF SWAN
----------------------------------------------------------------
Gridresolution : MXC 100 MYC 32760
: MCGRD 3276001
: MSC 28 MDC 36
: MTC 19
: NSTATC 1 ITERMX 1
Propagation flags : ITFRE 1 IREFR 1
Source term flags : IBOT 1 ISURF 1
: IWCAP 1 IWIND 3
: ITRIAD 0 IQUAD 2
: IBRAG 0 IQCM 0
: IVEG 0 ITURBV 0
: IMUD 0 IICE 0
Spatial step : DX 0.1010E-01 DY 0.3022E-02
Spectral bin : df/f 0.1173E+00 DDIR 0.1000E+02
Physical constants : GRAV 0.9810E+01 RHO 0.1025E+04
Wind input : WSPEED 0.0000E+00 DIR 0.0000E+00
: ICEWIND 0.00
Tail parameters : E(f) 0.4000E+01 E(k) 0.2500E+01
: A(f) 0.5000E+01 A(k) 0.3000E+01
Accuracy parameters : DREL 0.1000E+00 NPNTS 0.9950E+02
: DHOVAL 0.2000E+01 DTOVAL 0.2000E+00
: GRWMX 0.1000E+00
Drying/flooding : LEVEL 0.1500E+01 DEPMIN 0.5000E-01
The nautical convention for wind and wave directions is used
Scheme for geographic propagation is S&L
Scheme geogr. space : PROPSC 3 ICMAX 13
Scheme spectral space: CSS 0.5000E+00 CDD 0.5000E+00
Solver is SIP
: EPS2 0.1000E-03 OUTPUT 0
: NITER 20
Current is off
Quadruplets : IQUAD 2
: LAMBDA 0.2500E+00 CNL4 0.3000E+08
: CSH1 0.5500E+01 CSH2 0.8330E+00
: CSH3 -0.1250E+01
Maximum Ursell nr for Snl4 : 0.1000E+02
Triads is off
Bragg scattering is off
QC scattering is off
Surfbeat (IEM) is off
JONSWAP (`73) : GAMMA 0.3800E-01
Vegetation is off
Turbulence is off
Fluid mud is off
Dissipation by sea ice is off
W-cap Komen (`84) : EMPCOF (CDS2): 0.2360E-04
W-cap Komen (`84) : APM (STPM) : 0.3020E-02
W-cap Komen (`84) : POWST : 0.2000E+01
W-cap Komen (`84) : DELTA : 0.1000E+01
W-cap Komen (`84) : POWK : 0.1000E+01
Wind drag is Wu
Snyder/Komen wind input
Battjes&Janssen (`78): ALPHA 0.1000E+01 GAMMA 0.7300E+00
Set-up is off
Diffraction is off
Janssen (`89,`90) : ALPHA 0.1000E-01 KAPPA 0.4100E+00
Janssen (`89,`90) : RHOA 0.1280E+01 RHOW 0.1025E+04
1st and 2nd gen. wind: CF10 0.1880E+03 CF20 0.5900E+00
: CF30 0.1200E+00 CF40 0.2500E+03
: CF50 0.2300E-02 CF60 -0.2230E+00
: CF70 0.0000E+00 CF80 -0.5600E+00
: RHOAW 0.1249E-02 EDMLPM 0.3600E-02
: CDRAG 0.1230E-02 UMIN 0.1000E+01
: LIM_PM 0.1300E+00
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980101.120000 in sec: 43200.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980101.180000 in sec: 64800.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980102.000000 in sec: 86400.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980102.060000 in sec: 108000.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980102.120000 in sec: 129600.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980102.180000 in sec: 151200.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980103.000000 in sec: 172800.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980103.060000 in sec: 194400.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980103.120000 in sec: 216000.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980103.180000 in sec: 237600.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980104.000000 in sec: 259200.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980104.060000 in sec: 280800.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980104.120000 in sec: 302400.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980104.180000 in sec: 324000.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980105.000000 in sec: 345600.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980105.060000 in sec: 367200.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980105.120000 in sec: 388800.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
Time of computation -> 19980105.180000 in sec: 410400.
accuracy OK in NaN % of wet grid points ( 99.50 % required)
STOP
--
Moniki Melo
Senior Hydrometeorologist
|
|
From: Henrique R. <hra...@gm...> - 2025-05-26 22:56:36
|
Hi Andrew, Try adding 'PTHS', for example: 'QUANTity PTHS NOSWLL 2' Best regards Henrique On Mon, 26 May 2025 at 11:02, Andrew Watson <and...@me...> wrote: > Hi All, > > I am trying to set the number of output partitions using NOSWLL by > including the following command: > > QUANT NOSWLL=2 > > However, this throws an error. Can anyone please give me some help about > how to define the number of output partitions? > > Kind Regards, > > Andrew > > -- > Andrew Watson > Msc, Bsc, Csci, CMarSci, MIMarEST > Director & Senior Metocean Consultant > MetOceanWorks Ltd. > > Mobile +44 (0)7763 896635 > Registered in England and Wales Company Number 8078702 > > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > |
|
From: Andrew W. <and...@me...> - 2025-05-26 14:00:56
|
Hi All, I am trying to set the number of output partitions using NOSWLL by including the following command: QUANT NOSWLL=2 However, this throws an error. Can anyone please give me some help about how to define the number of output partitions? Kind Regards, Andrew -- Andrew Watson Msc, Bsc, Csci, CMarSci, MIMarEST Director & Senior Metocean Consultant MetOceanWorks Ltd. Mobile +44 (0)7763 896635 Registered in England and Wales Company Number 8078702 |
|
From: Perez, L. <Lar...@rp...> - 2025-05-06 01:37:05
|
Hi all, I’m a relatively new user of SWAN and OceanMesh2D. I have created a grid using OceanMesh2D and used the same tools to create my boundary files as I used to with Triangle. I can make my model run and results look sensible. However, I do have a couple of grid cells near the boundary corner showing me very low significant wave height, which don’t change regardless of timestep. I have tried modifying my grid in many ways – improving the resolution, using the high fidelity option… - and tried using 72 direction bins in SWAN, turning TRIADS off, etc.. Nothing seems to fix the problem. Has anyone come across something like this before? The figure is below. Many thanks! [cid:image001.png@01DBBE76.7E2676F0] Dr Larissa Perez (She/Her) Environmental Engineer PO Box 1048, Robina, QLD, 4230, Lakehouse Corporate Space, Suite 425, Level 2, 34-38 Glenferrie Drive | Robina, QLD, 4226, Australia T +61 7 5553 6900 E lar...@rp...<mailto:lar...@rp...> [cid:image002.png@01DBBE76.7E2676F0]<http://rpsgroup.com/> Follow us on: rpsgroup.com<https://rpsgroup.com> | LinkedIn<https://www.linkedin.com/company/rps> | Facebook<https://www.facebook.com/RPSmakingcomplexeasy/> | Instagram<https://www.instagram.com/rps.group/> | YouTube<https://www.youtube.com/channel/UCW82nGFvPwMSNpX-EMw8wFg> We acknowledge the Traditional Owners of Country throughout Australia and recognise their continuing connection to land, waters and community. We pay our respect to them and their cultures and to Elders past and present. |
|
From: Paulo B. <pba...@in...> - 2025-04-22 15:23:00
|
Hi all, I’m encountering an issue with SWAN and could use some help understanding or resolving it. I'm running a SWAN simulation (version 41.51, compiled with GNU compilers and using OpenMPI v4.1.6). At a certain point, the simulation fails and generates a file called Errfile1 with the following contents: Severe error : incorrect code in b.c. file: 20111101.030000 Severe error : incorrect code in b.c. file: 414.3062996667177 84 Severe error : incorrect code in b.c. file: 511.5982052216145 51 Severe error : incorrect code in b.c. file: 9999.0 -9999.0 Severe error : incorrect code in b.c. file: 9999.0 -9999.0 Severe error : incorrect code in b.c. file: 9999.0 -9999.0 Severe error : incorrect code in b.c. file: 9999.0 -9999.0 -9999 Severe error : incorrect code in b.c. file: -9999.0 -9999.0 -99 ... The error itself is expected due to incorrect input. However, the issue is that after this error occurs, the simulation hangs indefinitely. There’s no output to stdout or stderr, and all processes remain active, consuming 100% CPU. Does anyone know what might be causing SWAN to hang like this instead of terminating? I’m fine with the simulation failing due to the error, but I need SWAN to exit gracefully when that happens. Any insight or suggestions would be greatly appreciated. Thanks in advance! ┌──────────────── │ Best regards, │ Paulo Barbosa - Software Dev │ pba...@in... └──────────────── |
|
From: Hosnie G. <hos...@ya...> - 2025-04-08 14:32:30
|
hiI intend to simulate infragravity waves using the SWAN model. As it is clear, the “obstacle FIG” command should be used, and for this command, the parameters Hss and Tss are required. Unfortunately, I do not have these parameters in the form of field data, so I have conducted a simulation and obtained the wave spectrum for the specific point of interest. What confuses me is whether Hss is different from Hsig, and how Tss relates to Tm02. SWAN does not directly output the Hss and Tss parameters. What can be done to solve this problem? Can anyone explain? Is it possible to use Hs and Tm02 instead? How can I calculate the parameters Hss and Tss from a two-dimensional wave spectrum? Hss and Tss refer to the height and period of the combined sea and swell waves.?! Thank you very much. |
|
From: Alex C. <al...@oc...> - 2025-03-24 15:07:12
|
Hi Alex, We have found similar things in WW3 and SWAN. Are you using global HYCOM as the current input? We have found that the intensity and position of eddies, even in hindcast reanalyses, are not accurate enough with respect to how the resulting gradients influence longer period waves. We have experimented with manipulation of the current fields directly to reduce the intensity of gradients, which can improve the response and still out perform runs without wave-current interaction, but it is not a perfect solution. Curious if you find anything out with respect to numerical parametrization of the model. Best, -- Alex Crosby Ocean Engineer Vice President Oceanweather Inc. Stamford, CT 06901 https://oceanweather.com al...@oc... For urgent access to our forecast team, please use for...@oc... For general inquiries about data and services feel free to email oc...@oc... -----Original message----- From: Alex Gibbs - NOAA Federal via swanmodel-users <swa...@li...> Sent: Monday, March 24 2025, 2:41 am To: swa...@li... <swa...@li...> Subject: [swanmodel-users] Inflated/Spurious Wave Heights w/ Currents Attached is a three-panel plot from the 12Z 03/21 SWAN run, showing: * Left Panel: Gulf Stream current magnitude with significant wave height contours overlaid * Middle Panel: Significant wave heights, highlighting some anomalously high values * Right Panel: TAFB wind forcing It looks like smaller-scale eddies along the edges of the Gulf Stream are locally influencing the wave field significantly, contributing to the inflated or possibly spurious wave heights. The model seems to be over-amplifying the wave steepening effects associated with wave-current interactions, particularly in these high-shear transition zones. As a short-term fix, I could test some of the SWAN suggested numerics and physics controls(refraction by currents/freq shifting/etc.). Any suggestions are appreciated. FYI -- SWAN allows us to test these controls in the main input file: DIRIMPL this option is used to influence the numerical scheme for refraction. [cdd] A value of [cdd]=0 corresponds to a central scheme and has the largest accuracy (diffusion 0) but the computation may more easily generate spurious fluctuations. A value of [cdd]=1. corresponds to a first order upwind scheme and it is more diffusive and therefore preferable if (strong) gradients in depth or current are present. Default: [cdd] = 0.5. SIGIMPL controls the accuracy of computing the frequency shifting and the stopping criterion and amount of output for the SIP solver (used in the computations in the presence of currents or time varying depth). Alex Gibbs NOAA's National Weather Service Honolulu Weather Forecast Office Central Pacific Hurricane Center 808-973-5280 (O) _______________________________________________ swanmodel-users mailing list swa...@li... https://lists.sourceforge.net/lists/listinfo/swanmodel-users |
|
From: Alex G. - N. F. <ale...@no...> - 2025-03-24 03:38:45
|
Attached is a three-panel plot from the 12Z 03/21 SWAN run, showing: - *Left Panel:* Gulf Stream current magnitude with significant wave height contours overlaid - *Middle Panel:* Significant wave heights, highlighting some anomalously high values - *Right Panel:* TAFB wind forcing It looks like smaller-scale eddies along the edges of the Gulf Stream are locally influencing the wave field significantly, contributing to the inflated or possibly spurious wave heights. The model seems to be over-amplifying the wave steepening effects associated with wave-current interactions, particularly in these high-shear transition zones. As a short-term fix, I could test some of the SWAN suggested numerics and physics controls(refraction by currents/freq shifting/etc.). Any suggestions are appreciated. FYI -- SWAN allows us to test these controls in the main input file: DIRIMPL this option is used to influence the numerical scheme for refraction. [cdd] A value of [cdd]=0 corresponds to a central scheme and has the largest accuracy (diffusion [image: $\approx$] 0) but the computation may more easily generate spurious fluctuations. A value of [cdd]=1. corresponds to a first order upwind scheme and it is more diffusive and therefore preferable if (strong) gradients in depth or current are present. Default: [cdd] = 0.5. SIGIMPL controls the accuracy of computing the frequency shifting and the stopping criterion and amount of output for the SIP solver (used in the computations in the presence of currents or time varying depth). Alex Gibbs NOAA's National Weather Service Honolulu Weather Forecast Office Central Pacific Hurricane Center 808-973-5280 (O) |
|
From: amany H. <ama...@ya...> - 2025-03-05 10:56:04
|
Hi all ,I try to run swan model, i got this error in boundary condition BOUN SEGM IJ [x] [y] [i] [j] CON PAR [hs] [per] [dir] [dd] ** Error : Wrong type of data for variable I -> I item read=[x] ** Warning : No points on the boundaries found ** Error : Data field skipped:[y] ** Error : Data field skipped:[i] ** Error : Data field skipped:[j] ** Severe error : Wrong type of data for variable HS -> HS item=[hs] ** Severe error : Wrong type of data for variable PER -> PER item=[per] ** Severe error : Wrong type of data for variable DIR -> DIR item=[dir]** Severe error : Wrong type of data for variable DD -> DD item=[dd] and my input file is:SET 1 CARTesian COORDINATES SPHE MODE STAT TWOD $CGRID [xpc] [ypc] [alpc] [xlenc] [ylenc] [mxc] [myc] CIRCLE [mdc] [flow] [fhigh] [msc] CGRID 28.8 31 0. 0.3999999 0.8999999 95 215 CIRCLE 72 0.05 1. 34 $CGRID 28.8 31 0. 0.4 0.9 215 95 CIRCLE 20 1 0.4 15 $INPGRID BOTTOM [xpc] [ypc] [alpc] [mxc] [myc] [dxinp] [dyinp] INPGRID BOTTOM 28.8 31 0. 95 215 0.0042 0.0042 READINP BOTTOM 1. 'depth_main.dat' 3 0 FREE BOU SHAP JON 3.3 PEAK DSPR POWER BOUN SIDE W CCW CON PAR 13.359 15.880 293.000 24.100 $North BOUNDARY $BOUN SEGM IJ [x] [y] [i] [j] CON PAR [hs] [per] [dir] [dd] BOUN SEGM IJ 0 90 92 210 CON PAR 2 4 292.5 5.5 $South BOUNDARY BOUN SEGM IJ 0 0 10 0 CON PAR 2 4 292.5 5.5 DIFFRAC 1 0 0 1 BRE CONSTANT 1.0 0.78 OFF QUAD OFF WCAP GROUP 'coarse' SUBG 0 215 0 95 BLOCK 'coarse' NOHEAD 'Ind_HS.nc' LAY 4 HS BLOCK 'coarse' NOHEAD 'Ind_DIR.mat' LAY 4 DIR BLOCK 'coarse' NOHEAD 'Ind_PER.mat' LAY 4 TM01 BLOCK 'coarse' NOHEAD 'Ind_DEPTH.mat' LAY 4 DEPTH TEST 1,0 COMPUTE STOP please help me to correct this error thanks in advance Amani |
|
From: Pelin U. <pel...@gm...> - 2025-02-16 06:44:31
|
Hi Zeinab, It can be challenging to prepare input files for the first time. First, I think, you should read the SWAN user manual, especially the parts related to the Readinput command. You should be extra careful with 'IDLA' and whether your input file includes headers or not (header at the beginning of the file and header at each time step). Then you should construct your .swn file accordingly. I am using MATLAB to create an input text file but you can use Python or any other computing software. You should construct a text file according to 'IDLA' you chose. IDLA decides in which order to read the input file and insert it in SWAN. So, you should store your data in the text file according to this order (there are six options, it is up to you) and repeat storing at each time step. Be careful with the wind input data. You have to store the x-component of the data and the y-component consecutively and continue with the next time step. I hope it helps to answer your questions. Good luck with your research. Regards, PU Zeinab Salah <zei...@gm...>, 15 Şub 2025 Cmt, 23:48 tarihinde şunu yazdı: > Hello All, > I'm beginner in SWAN model, and I want to know how to prepare the > bathymetry file from gebco website and wind data from ERA5 netcdf to be in > the suitable format for SWAN. > > Thank you in advance. > Best regards, > Zeinab > > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > -- Pelin Uzun *Research Assistant* *Ph.D. Candidate* *Boğaziçi University* *Hydraulics and Coastal Engineering* |
|
From: Zeinab S. <zei...@gm...> - 2025-02-15 20:46:49
|
Hello All, I'm beginner in SWAN model, and I want to know how to prepare the bathymetry file from gebco website and wind data from ERA5 netcdf to be in the suitable format for SWAN. Thank you in advance. Best regards, Zeinab |
|
From: Paulo B. <pba...@in...> - 2024-11-20 11:11:13
|
Dear SWAN Users, I hope this message finds you well. I recently compiled SWAN v41.45 using OpenMPI (version 4.1.2) with GCC 10, G++ 10, and GFortran 10. However, I’ve encountered some issues during simulations, and I’m reaching out to seek your advice. When running simulations with `swanrun`, I’ve observed inconsistent behavior in the generation of output files: - Sometimes, only the PTR files are created, while the ERF files are missing. - Other times, neither file is created. - On occasion, both files are generated successfully. - In some cases, the ERF file is created but remains empty. This unpredictable behavior makes debugging simulations quite difficult. Interestingly, the same simulation, when run on another setup (a different computer with a different SWAN compilation), generates both the ERF and PTR files as expected. I am wondering if the issue could be related to the compilers I am using or if I might be missing some flags during the `make config` or `make mpi` steps. Has anyone experienced similar issues or have suggestions on how to resolve this? Any guidance would be greatly appreciated. Thank you in advance for your support! ┌──────────────── │ Best regards, │ Paulo Barbosa - Software Dev │ pba...@in... └──────────────── |
|
From: Luis S. <sar...@in...> - 2024-10-17 05:34:32
|
Dear Javi and Jannik, Thank you so much for your help. I may try to compile the version from Javi's repo. That should be enough for the tests we want to perform. Thank you! Cheers L A terça, 15/10/2024, 17:33, Javi Rodriguez <ja...@pr...> escreveu: > Hi Luis, > > > https://github.com/apchoi79/SWAN-Support/ > <https://github.com/apchoi79/SWAN-Support/tree/master> is a clone of my > current repository located at https://gitlab.com/xavirg/swan-support > > I created such repository because (like it is for you) it was hard to get > old official versions from the original website. > > I can confirm all the SWAN files from my repository come from the original > source and should even have the original timestamps. > > > Regards, > Javier > On Tuesday, October 15th, 2024 at 17:59, Luis Sarmento < > sar...@in...> wrote: > > Dear Jannik, > > Thank you so much for your assistance. > However, if we follow the link for version 41.31 (or most of other links) > we end up here: > > https://sourceforge.net/projects/swanmodel/files/ > > and then we end up again in version 41.51. > > https://sourceforge.net/projects/swanmodel/files/swan/ > > I just can't seem to find the source of 41.31. > I ended up finding it here, a sort of non-official snapshot: > > https://github.com/apchoi79/SWAN-Support/tree/master/source > But I was hoping to find the official version. > Many thanks! > > L > > > On Tue, Oct 15, 2024 at 4:48 PM Jannik Kühn via swanmodel-users < > swa...@li...> wrote: > >> Hi Luis, >> >> it looks like you can download previous versions on their sourceforge >> website (on the activity tab, link below) >> >> >> https://sourceforge.net/p/swanmodel/activity/?page=0&limit=100#66e021c5be081c70c45b1757 >> >> Hope this helps, >> Jannik >> On 15/10/2024 16:38, Luis Sarmento wrote: >> >> Hi everyone, >> >> I am looking for an older version of SWAN, namely version 41.31. I would >> like to compare v 41.31 with 41.45. >> Is there any place where I can download 41.31? I can't seem to find any >> pointer in the repo to older versions. >> Pointers to the original source code would be greatly appreciated! >> Many thanks! >> Best, >> >> L >> >> >> >> >> _______________________________________________ >> swanmodel-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/swanmodel-users >> >> _______________________________________________ >> swanmodel-users mailing list >> swa...@li... >> https://lists.sourceforge.net/lists/listinfo/swanmodel-users >> > > |
|
From: Javi R. <ja...@pr...> - 2024-10-15 16:34:00
|
Hi Luis, [https://github.com/apchoi79/SWAN-Support/](https://github.com/apchoi79/SWAN-Support/tree/master) is a clone of my current repository located at https://gitlab.com/xavirg/swan-support I created such repository because (like it is for you) it was hard to get old official versions from the original website. I can confirm all the SWAN files from my repository come from the original source and should even have the original timestamps. Regards, Javier On Tuesday, October 15th, 2024 at 17:59, Luis Sarmento <sar...@in...> wrote: > Dear Jannik, > > Thank you so much for your assistance. > However, if we follow the link for version 41.31 (or most of other links) we end up here: > > https://sourceforge.net/projects/swanmodel/files/ > > and then we end up again in version 41.51. > > https://sourceforge.net/projects/swanmodel/files/swan/ > > I just can't seem to find the source of 41.31. > I ended up finding it here, a sort of non-official snapshot: > > https://github.com/apchoi79/SWAN-Support/tree/master/source > > But I was hoping to find the official version. > Many thanks! > > L > > On Tue, Oct 15, 2024 at 4:48 PM Jannik Kühn via swanmodel-users <swa...@li...> wrote: > >> Hi Luis, >> >> it looks like you can download previous versions on their sourceforge website (on the activity tab, link below) >> >> https://sourceforge.net/p/swanmodel/activity/?page=0&limit=100#66e021c5be081c70c45b1757 >> >> Hope this helps, >> Jannik >> >> On 15/10/2024 16:38, Luis Sarmento wrote: >> >>> Hi everyone, >>> >>> I am looking for an older version of SWAN, namely version 41.31. I would like to compare v 41.31 with 41.45. >>> Is there any place where I can download 41.31? I can't seem to find any pointer in the repo to older versions. >>> Pointers to the original source code would be greatly appreciated! >>> Many thanks! >>> Best, >>> >>> L >>> >>> _______________________________________________ >>> swanmodel-users mailing list >>> swa...@li... >>> >>> https://lists.sourceforge.net/lists/listinfo/swanmodel-users >> >> _______________________________________________ >> swanmodel-users mailing list >> swa...@li... >> https://lists.sourceforge.net/lists/listinfo/swanmodel-users |
|
From: Luis S. <sar...@in...> - 2024-10-15 15:59:18
|
Dear Jannik, Thank you so much for your assistance. However, if we follow the link for version 41.31 (or most of other links) we end up here: https://sourceforge.net/projects/swanmodel/files/ and then we end up again in version 41.51. https://sourceforge.net/projects/swanmodel/files/swan/ I just can't seem to find the source of 41.31. I ended up finding it here, a sort of non-official snapshot: https://github.com/apchoi79/SWAN-Support/tree/master/source But I was hoping to find the official version. Many thanks! L On Tue, Oct 15, 2024 at 4:48 PM Jannik Kühn via swanmodel-users < swa...@li...> wrote: > Hi Luis, > > it looks like you can download previous versions on their sourceforge > website (on the activity tab, link below) > > > https://sourceforge.net/p/swanmodel/activity/?page=0&limit=100#66e021c5be081c70c45b1757 > > Hope this helps, > Jannik > On 15/10/2024 16:38, Luis Sarmento wrote: > > Hi everyone, > > I am looking for an older version of SWAN, namely version 41.31. I would > like to compare v 41.31 with 41.45. > Is there any place where I can download 41.31? I can't seem to find any > pointer in the repo to older versions. > Pointers to the original source code would be greatly appreciated! > Many thanks! > Best, > > L > > > > > _______________________________________________ > swanmodel-users mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/swanmodel-users > > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > |
|
From: Jannik K. <jan...@un...> - 2024-10-15 15:47:16
|
Hi Luis, it looks like you can download previous versions on their sourceforge website (on the activity tab, link below) https://sourceforge.net/p/swanmodel/activity/?page=0&limit=100#66e021c5be081c70c45b1757 Hope this helps, Jannik On 15/10/2024 16:38, Luis Sarmento wrote: > Hi everyone, > > I am looking for an older version of SWAN, namely version 41.31. I > would like to compare v 41.31 with 41.45. > Is there any place where I can download 41.31? I can't seem to find > any pointer in the repo to older versions. > Pointers to the original source code would be greatly appreciated! > Many thanks! > Best, > > L > > > > > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users |
|
From: Luis S. <sar...@in...> - 2024-10-15 15:07:06
|
Hi everyone, I am looking for an older version of SWAN, namely version 41.31. I would like to compare v 41.31 with 41.45. Is there any place where I can download 41.31? I can't seem to find any pointer in the repo to older versions. Pointers to the original source code would be greatly appreciated! Many thanks! Best, L |
|
From: Andrea B. <and...@un...> - 2024-10-03 22:38:53
|
Hi Marta, has the file the string TPAR in its first line? Bye Andrea [cid:image001.png@01DB15E8.B4D6BED0] Da: Marta Vallès <ma...@th...> Inviato: giovedì 3 ottobre 2024 12:24 A: swa...@li... Oggetto: [swanmodel-users] Unsupported boundary data file Hello everyone, I have set the boundary conditions on my configuration file like ------------------- BOUNDSPEC SEGMENT IJ 0 0 0 1 CONSTANT PAR 0.56 6.19 43.55 20 BOUNDSPEC SEGMENT IJ 0 1 0 18 CONSTANT PAR 0.47 6.21 38.69 20 ... ------------------- and everything worked correctly. Now I have a non-stationary case and I have defined it like ------------------- MODE NONSTATIONARY TWODIMENSIONAL ... BOUNDSPEC SEGMENT IJ 0 0 0 1 CONSTANT FILE 'bound-0001.bnd' 1 BOUNDSPEC SEGMENT IJ 0 1 0 18 CONSTANT FILE 'bound-01018.bnd' 1 ... COMPUTE NONSTAT 20240930.060000 1 HR 20241001.050000 STOP HOTOUT 'output_wave_params' ------------------- The files 'bound-xxxxx.bnd' have the following structure: ------------------- 20240930.220000 0.19 331.49 6.24 20 20240930.230000 0.18 330.84 6.14 20 20241001.000000 0.19 329.93 6.06 20 20241001.010000 0.19 328.85 5.98 20 20241001.020000 0.18 327.78 5.88 20 ... ------------------- Now I get this error: ------------------- BOUNDSPEC SEGMENT IJ 0 0 0 1 CONSTANT FILE 'bound-0001.bnd' 1 ** Severe error : unsupported boundary data file BOUNDSPEC SEGMENT IJ 0 1 0 18 CONSTANT FILE 'bound-01018.bnd' 1 ** Severe error : unsupported boundary data file ... ------------------- Does someone understands why am I getting this error and how to fix it? Thank you. -- Marta Vallès |
|
From: Marta V. <ma...@th...> - 2024-10-03 11:19:17
|
Hello everyone, I have set the boundary conditions on my configuration file like ------------------- BOUNDSPEC SEGMENT IJ 0 0 0 1 CONSTANT PAR 0.56 6.19 43.55 20 BOUNDSPEC SEGMENT IJ 0 1 0 18 CONSTANT PAR 0.47 6.21 38.69 20 ... ------------------- and everything worked correctly. Now I have a non-stationary case and I have defined it like ------------------- MODE NONSTATIONARY TWODIMENSIONAL ... BOUNDSPEC SEGMENT IJ 0 0 0 1 CONSTANT FILE 'bound-0001.bnd' 1 BOUNDSPEC SEGMENT IJ 0 1 0 18 CONSTANT FILE 'bound-01018.bnd' 1 ... COMPUTE NONSTAT 20240930.060000 1 HR 20241001.050000 STOP HOTOUT 'output_wave_params' ------------------- The files 'bound-xxxxx.bnd' have the following structure: ------------------- 20240930.220000 0.19 331.49 6.24 20 20240930.230000 0.18 330.84 6.14 20 20241001.000000 0.19 329.93 6.06 20 20241001.010000 0.19 328.85 5.98 20 20241001.020000 0.18 327.78 5.88 20 ... ------------------- Now I get this error: ------------------- BOUNDSPEC SEGMENT IJ 0 0 0 1 CONSTANT FILE 'bound-0001.bnd' 1 ** Severe error : unsupported boundary data file BOUNDSPEC SEGMENT IJ 0 1 0 18 CONSTANT FILE 'bound-01018.bnd' 1 ** Severe error : unsupported boundary data file ... ------------------- Does someone understands why am I getting this error and how to fix it? Thank you. -- *Marta Vallès* |
36 messages has been excluded from this view by a project administrator.
