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
(5) |
Sep
(7) |
Oct
(1) |
Nov
(6) |
Dec
|
|
From: Rafael G. <raf...@ya...> - 2025-11-11 21:17:17
|
In case this is helpful, the rompy-swan python package provides a framework to help setting up SWAN, including the generation of the input files like wind, and the full SWAN INPUT cmd file itself. There are a few example notebooks you could check that may be helpful, for example this one. All you need to do is define some base objects like Grid and TimeRange, then you could use them with your wind data (which could be prescribed in different ways, like an xarray object or a netcdf file) to generate your SWAN input files.
Rafael
On Tuesday, 11 November 2025 at 08:27:05 am NZDT, Sergio Veliz <ser...@gm...> wrote:
Hello
I left this link to other question with similar answer:
https://sourceforge.net/p/swanmodel/mailman/message/59222557/
Never used grib files, and always have to process a netcdf to a ascii file
Hope it helps!
El lun, 10 nov 2025 a las 15:56, Natalia Rodeiro (<nat...@gm...>) escribió:
Dear SWAN community,
I've been trying to set up the SWAN model for the past few weeks, but I keep running into issues with the wind field input. I downloaded 96 hours of GFS winds, and I'm not quite sure what the correct format is for SWAN to read them.
Since I’m downloading GRIB files, I tried using a Python script to convert them into the format I need. However, even after trying different ways of organizing the data (using u/v components, wind speed and direction, and changing the IDLA options), SWAN still doesn’t read the wind input file properly.
Does anyone have an example of this type of input file? How did you organize the information? Were you also working with GRIBs?
Thank you so much!
Best regards,Natalia_______________________________________________
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: Sergio V. <ser...@gm...> - 2025-11-10 19:24:13
|
Hello I left this link to other question with similar answer: https://sourceforge.net/p/swanmodel/mailman/message/59222557/ Never used grib files, and always have to process a netcdf to a ascii file Hope it helps! El lun, 10 nov 2025 a las 15:56, Natalia Rodeiro (<nat...@gm...>) escribió: > Dear SWAN community, > > I've been trying to set up the SWAN model for the past few weeks, but I > keep running into issues with the wind field input. I downloaded 96 hours > of GFS winds, and I'm not quite sure what the correct format is for SWAN to > read them. > > Since I’m downloading GRIB files, I tried using a Python script to convert > them into the format I need. However, even after trying different ways of > organizing the data (using u/v components, wind speed and direction, and > changing the IDLA options), SWAN still doesn’t read the wind input file > properly. > > Does anyone have an example of this type of input file? How did you > organize the information? Were you also working with GRIBs? > Thank you so much! > > Best regards, > Natalia > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > |
|
From: Natalia R. <nat...@gm...> - 2025-11-10 18:54:51
|
Dear SWAN community, I've been trying to set up the SWAN model for the past few weeks, but I keep running into issues with the wind field input. I downloaded 96 hours of GFS winds, and I'm not quite sure what the correct format is for SWAN to read them. Since I’m downloading GRIB files, I tried using a Python script to convert them into the format I need. However, even after trying different ways of organizing the data (using u/v components, wind speed and direction, and changing the IDLA options), SWAN still doesn’t read the wind input file properly. Does anyone have an example of this type of input file? How did you organize the information? Were you also working with GRIBs? Thank you so much! Best regards, Natalia |
|
From: Paulo Avilez-V. <pva...@fe...> - 2025-11-07 09:05:12
|
Dear Sihyeon Lee If you define the boundary conditions at two or more points along a boundary line, SWAN will handle the interpolation itself. See the manual information for the BOUNDSPEC command with the VARIABLE option. Best regards Paulo Avilez-Valente Dr-Eng Paulo Avilez-Valente Assistant Professor Faculdade de Engenharia Universidade do Porto Rua Dr Roberto Frias P-4200-465 Porto Portugal On Thu, 6 Nov 2025 at 20:17, 이시현학부생 via swanmodel-users <swa...@li...> wrote: > > Dear SWAN supports, > > Hi there, I am currently conducting numerical wave modeling using the SWAN model. > At present, I have observed wave data (such as significant wave height, period, and direction) from a single point. For one latitude line, there are only two or three observation points available. > > So far, I have applied the data from a single observation point uniformly along one boundary side (SIDE) to run SWAN. However, I have found some limitations with this approach. > > To improve the boundary condition, I am now trying to construct the boundary using multiple observation points — specifically, by interpolating between two points to generate wave conditions along the segments between them. > > My question is: > > What interpolation methods are generally recommended for such boundary construction (e.g., linear, spline, or others)? > > Or, are there alternative approaches to represent spatially varying wave conditions along the boundary instead of simple interpolation? > > Any guidance or references you could share would be greatly appreciated. > > Thank you very much for your time and help. > > Best regards, > Sihyeon Lee > > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users |
|
From: 이시현학부생 <pet...@ha...> - 2025-11-06 20:14:07
|
Dear SWAN supports, Hi there, I am currently conducting numerical wave modeling using the SWAN model. At present, I have observed wave data (such as significant wave height, period, and direction) from a single point. For one latitude line, there are only two or three observation points available. So far, I have applied the data from a single observation point uniformly along one boundary side (SIDE) to run SWAN. However, I have found some limitations with this approach. To improve the boundary condition, I am now trying to construct the boundary using multiple observation points — specifically, by interpolating between two points to generate wave conditions along the segments between them. My question is: - What interpolation methods are generally recommended for such boundary construction (e.g., linear, spline, or others)? - Or, are there alternative approaches to represent spatially varying wave conditions along the boundary instead of simple interpolation? Any guidance or references you could share would be greatly appreciated. Thank you very much for your time and help. Best regards, Sihyeon Lee |
|
From: Cristián S. <cri...@gm...> - 2025-11-03 01:18:47
|
Dear SWAN group, I'm using SWAN v41.51 with an unstructured triangular mesh generated for ADCIRC (fort.14 file), and I need to define boundary conditions between certain nodes. I've tried different methods, for example, specifying the nodes: BOUndspec SEGMent IJ 650 125 1 57 170 225 1161 I also tried using xy coordinates (BOUndspec SEGMent XY), but I get the following error: 'Terminating error: SwanBpntlist: list of boundary vertices could not be completed' I've attached the model files, along with the fort.14 mesh, to this Google Drive link: https://drive.google.com/drive/folders/1m26MyRWZ8fEMOa5Ej_VP74WF0CiJ5BMJ?usp=drive_link Any guidance would be greatly appreciated. -- Cristián Santander Escudero. Ingeniero Civil Oceánico. Universidad de Valparaíso. LinkedIn <https://www.linkedin.com/in/cristi%C3%A1n-santander-70262921/> |
|
From: Eunice O. <eol...@in...> - 2025-10-17 15:33:06
|
Dear SWAN community, We recently replicated a wave modeling case in Antarctic polynyas using SWAN. The full scenario runs in about 4.25 hours on average using the Inductiva API. We’ve documented the setup and results here: 🔗 https://inductiva.ai/guides/swan/modeling-waves-in-polynyas/index Feedback is very welcome. If there are other cases or published studies you think would be worth exploring, feel free to share them. Best regards, -- *Eunice Oliveira* Product Owner at Inductiva.AI |
|
From: 이시현학부생 <pet...@ha...> - 2025-09-25 08:24:19
|
Dear SWAN support team, I am currently setting up a SWAN model using a *curvilinear grid*. My input lines are: CGRID CURVILINEAR 3 1 EXC -999 -999 CIRCLE 36 0.05 1.0 30READGRID COOR 1. '/Volumes/Krong/Pohang/Depth_data/Pohang_CoordBlocks.txt' 1 0 0 FREE However, SWAN does not seem to read my coordinate file correctly. I would like to ask for clarification about the exact format required for the coordinate file when using READGRID COOR. - Should the file contain two blocks (first the X-coordinates, then the Y-coordinates) in matrix form? - For example, for a grid defined as CGRID CURVILINEAR 3 2 ..., should the file look like this? 129.45 129.46 129.47 129.45 129.46 129.47 36.00 36.00 36.00 36.01 36.01 36.01 I would greatly appreciate it if you could confirm the correct formatting, or provide a small working example file for reference. Thank you very much for your time and support. Best regards, Sihyeon |
|
From: k k <kar...@gm...> - 2025-09-25 01:58:38
|
Hi Zhiyun, Good day. The time series input is a great approach, but essentially the model indicates the energy needs redistribution in some sorts. Wondering if the depth is too shallow for assumed spectral construct, i.e., the model isn't as simple as TPAR, might need better parameterisation or change the model domain. Regards -- Nga Mihi Namaste KarunaKar Kintada., On Thu, 25 Sept 2025, 06:13 Zhiyun Du via swanmodel-users, < swa...@li...> wrote: > Dear SWAN group, > > I am running a SWAN model and having boundary convergence issues. The open > boundary condition to force swan was downloaded from the WW3 model outputs. > I used TPAR files for boundary inputs. > > I started my model from 2005, and when it ran until some times, some of > the TPAR files showed this error: > > Boundary data type TPAR processed, time: 83289600. > Boundary data type TPAR processed, time: 83300400. > Boundary data type TPAR processed, time: 83311200. > Boundary data type TPAR processed, time: 83322000. > ** Severe error : No convergence calculating the spectrum > ** Severe error : at the boundary using parametric bound. cond. > > Then, I changed my start time to 2008 just to let the model check the > boundaries. I found many "severe no convergence error" in different files > and at different times. > > The only way I can let the model run is to comment out the TPAR files that > had this error. However, I will lose wave inputs at these TPAR > locations(?). I tried to modify the values at these "bad times" by (1) > simply deleting or (2) interpolating from near hours, but none worked, and > the error still existed. > > I am writing to ask if you may have this issue before and know how to fix > it. Thank you very much. > > Best, > Zhiyun > > > > Zhiyun Du > Andrews Hall 215 | PhD student > Department of Physical Sciences > Virginia Institute of Marine Science > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > |
|
From: Alex C. <al...@oc...> - 2025-09-24 18:25:29
|
I am out of the office this week so please allow additional time for responses. If you are at the Workshop on Waves, Storm Surge and Coastal Hazards in Santander, ES, you can find me there as well. For urgent matters please email er...@oc... or oc...@oc.... Thanks for your understanding! |
|
From: Zhiyun Du <zd...@vi...> - 2025-09-24 18:11:09
|
Dear SWAN group, I am running a SWAN model and having boundary convergence issues. The open boundary condition to force swan was downloaded from the WW3 model outputs. I used TPAR files for boundary inputs. I started my model from 2005, and when it ran until some times, some of the TPAR files showed this error: Boundary data type TPAR processed, time: 83289600. Boundary data type TPAR processed, time: 83300400. Boundary data type TPAR processed, time: 83311200. Boundary data type TPAR processed, time: 83322000. ** Severe error : No convergence calculating the spectrum ** Severe error : at the boundary using parametric bound. cond. Then, I changed my start time to 2008 just to let the model check the boundaries. I found many "severe no convergence error" in different files and at different times. The only way I can let the model run is to comment out the TPAR files that had this error. However, I will lose wave inputs at these TPAR locations(?). I tried to modify the values at these "bad times" by (1) simply deleting or (2) interpolating from near hours, but none worked, and the error still existed. I am writing to ask if you may have this issue before and know how to fix it. Thank you very much. Best, Zhiyun Zhiyun Du Andrews Hall 215 | PhD student Department of Physical Sciences Virginia Institute of Marine Science [cid:55e85f39-e879-4ab2-b5e8-779ffb595fef] |
|
From: k k <kar...@gm...> - 2025-09-18 23:29:59
|
Hi Sihyeon, It's bit tricky to understand the problem with out knowledge of area being simulated. But two things to consider. 1. Is there any wind generation component. 2. Is the water shallow for spectral changes within few cells? Definitely not wave breaking, as wave heights are increasing, not strong reflection unless specified and not sure triads are. Is friction enough? -- Nga Mihi Namaste KarunaKar Kintada., On Thu, 18 Sept 2025, 23:52 이시현학부생 via swanmodel-users, < swa...@li...> wrote: > Dear SWAN Support Team, > > I am currently conducting wave modeling using SWAN for a coastal region, > and I have encountered an issue at the model boundary. > > At the beginning of the simulation, the significant wave height (Hs) at > the open boundary matches the prescribed input condition. However, as time > progresses, I observe that the wave height on the right-hand side of the > boundary becomes larger than the intended input, in some cases by up to 0.6 > m. > > From my understanding, this may be related to wave energy not leaving the > domain properly and being accumulated near the boundary. I have learned > that some other wave models (e.g., Boussinesq-type models, CFD solvers) > implement a "sponge layer" to absorb excess energy, but it seems that SWAN > does not provide such a direct option. > > > Could you kindly advise how to properly handle this boundary condition in > SWAN, so that the incoming wave at the open boundary remains constant > throughout the simulation? > For example, is there a recommended practice (such as domain extension, > nesting, or applying certain dissipation mechanisms) to avoid this kind of > boundary growth? > > Your guidance would be greatly appreciated. Thank you very much for your > support. > > Best regards, > Sihyeon > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > |
|
From: 이시현학부생 <pet...@ha...> - 2025-09-18 11:50:23
|
Dear SWAN Support Team, I am currently conducting wave modeling using SWAN for a coastal region, and I have encountered an issue at the model boundary. At the beginning of the simulation, the significant wave height (Hs) at the open boundary matches the prescribed input condition. However, as time progresses, I observe that the wave height on the right-hand side of the boundary becomes larger than the intended input, in some cases by up to 0.6 m. >From my understanding, this may be related to wave energy not leaving the domain properly and being accumulated near the boundary. I have learned that some other wave models (e.g., Boussinesq-type models, CFD solvers) implement a "sponge layer" to absorb excess energy, but it seems that SWAN does not provide such a direct option. Could you kindly advise how to properly handle this boundary condition in SWAN, so that the incoming wave at the open boundary remains constant throughout the simulation? For example, is there a recommended practice (such as domain extension, nesting, or applying certain dissipation mechanisms) to avoid this kind of boundary growth? Your guidance would be greatly appreciated. Thank you very much for your support. Best regards, Sihyeon |
|
From: Eunice O. <eol...@in...> - 2025-09-04 11:34:25
|
Dear SWAN community, We are pleased to share that we have integrated *UnSWAN*, the unstructured-mesh version of the SWAN model, into our platform. To help validate the implementation and move toward making it available for broader community use, we are currently looking for a *public use case* suitable for testing. If you know of any open or well-documented test cases or if you are interested in collaborating on this effort, we would greatly appreciate your input. Best regards, Eunice Oliveira Inductiva.AI eol...@in... |
|
From: Sergio V. <ser...@gm...> - 2025-08-19 20:44:00
|
Good afternoon Here I have a little example, hope it helps (sorry for the amount of digits): INPGRID WIND REG -55 -56 0. 9 9 0.1 0.1 EXC -999 NONSTAT 20221230.202000 10 MIN 20221230.204000 READINP WIND 1. 'vientos.dat' 1 0 1 0 FREE 20221230.202000 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -1.343667460402191 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 -2.3729910989837966 20221230.203000 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -1.8568357749385336 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 -3.0467663029691687 Kind regards, Sergio El lun, 18 ago 2025 a las 5:00, 이시현학부생 via swanmodel-users (< swa...@li...>) escribió: > Dear SWAN Experts, > > I’m preparing wind-field inputs for SWAN using *INPGRID WIND* and *READINP > WIND*. > I understand from the manual that the model reads *all U (first > component) for the full grid, then all V (second component)*, and that > for *NONSTATIONARY* cases the inputs are provided as a *sequence of > fields over time*. However, I could not find a concrete, minimal example > file. > > Could you kindly share a small text example illustrating: > > 1. > > *STATIONARY* case: > - > > For an NX×NY grid in ASCII FREE format, how to arrange one time > slice as U-block → V-block (including scan order). > 2. > > *NONSTATIONARY* case: > - > > A minimal example for *two time steps (t₁, t₂)* (both without a > time header and—with nhedt/nhedvec—with a header, if applicable). > 3. > > Any notes for *rotated rectilinear grids*, where U and V are along *grid > (ξ, η)* directions rather than geographic east/north. > > My planned settings are: > > - > > INPGRID WIND: rectilinear, origin (x0, y0)=…, NX=…, NY=…, dX=…, dY=…, > angle=… > - > > READINP WIND: FREE, nhedf=…, nhedt=…, nhedvec=…, idla=… > > Thank you very much for your time and assistance. > Best regards, > Sihyeon > _______________________________________________ > swanmodel-users mailing list > swa...@li... > https://lists.sourceforge.net/lists/listinfo/swanmodel-users > |
|
From: Alex C. <al...@oc...> - 2025-08-18 08:13:32
|
I am out of the office this week so please allow additional time for responses. For urgent matters please email er...@oc... or oc...@oc.... Thanks for your understanding! |
|
From: 이시현학부생 <pet...@ha...> - 2025-08-18 07:58:49
|
Dear SWAN Experts,
I’m preparing wind-field inputs for SWAN using *INPGRID WIND* and *READINP
WIND*.
I understand from the manual that the model reads *all U (first component)
for the full grid, then all V (second component)*, and that for
*NONSTATIONARY* cases the inputs are provided as a *sequence of fields over
time*. However, I could not find a concrete, minimal example file.
Could you kindly share a small text example illustrating:
1.
*STATIONARY* case:
-
For an NX×NY grid in ASCII FREE format, how to arrange one time slice
as U-block → V-block (including scan order).
2.
*NONSTATIONARY* case:
-
A minimal example for *two time steps (t₁, t₂)* (both without a time
header and—with nhedt/nhedvec—with a header, if applicable).
3.
Any notes for *rotated rectilinear grids*, where U and V are along *grid
(ξ, η)* directions rather than geographic east/north.
My planned settings are:
-
INPGRID WIND: rectilinear, origin (x0, y0)=…, NX=…, NY=…, dX=…, dY=…,
angle=…
-
READINP WIND: FREE, nhedf=…, nhedt=…, nhedvec=…, idla=…
Thank you very much for your time and assistance.
Best regards,
Sihyeon
|
|
From: <mer...@do...> - 2025-08-07 08:05:15
|
Dear Sihyeon, You can check the user manual for regular grids and input files. I think it will be helpful to you. I am attaching a screenshot from the user manual. Saygılarımla, Best regards, Mert Yaman İnşaat Yüksek Mühendisi Civil/Coastal Engineer, MSc. Dolfen Danışmanlık Mühendislik A.Ş. Üsküp Caddesi (Çevre Sokak) 20/3, Kavaklıdere, 06680 Ankara T: (312) 468 5930 pbx F: (312) 468 5941 E: <mailto:mer...@do...> mer...@do... W: <http://www.dolfen.com/> www.dolfen.com From: 이시현학부생 via swanmodel-users <swa...@li...> Sent: Wednesday, August 6, 2025 5:21 PM To: swa...@li... Subject: [swanmodel-users] Question about INPGRID BOTTOM Hello, my name is Sihyeon, and I am a student currently studying the SWAN modeling software for academic purposes. As I am relatively new to this field, I would greatly appreciate your guidance regarding an issue I have encountered. I have created a bathymetric data set in MATLAB, which has a dimension of 66 rows by 53 columns. To input this data into SWAN, I initially wrote the following commands: INPGRID BOTTOM 552305. 4002200. 0. 53 66 150. 150. READINP BOTTOM 1. 'Botinfo_0805.txt' 1 0 FREE However, SWAN returned the following error message: Error: Unexpected end of file while reading To resolve this, I modified the command to: INPGRID BOTTOM 552305. 4002200. 0. 52 65 150. 150. READINP BOTTOM 1. 'Botinfo_0805.txt' 1 0 FREE With this adjustment, SWAN successfully read the entire dataset without any errors. Could you kindly explain why this issue occurs and clarify how SWAN reads and interprets the bathymetric data? Your assistance and detailed explanation would greatly enhance my understanding and help me progress in my studies. Thank you very much for your time and assistance. Best regards, Sihyeon |
|
From: 이시현학부생 <pet...@ha...> - 2025-08-06 15:12:43
|
Hello, my name is Sihyeon, and I am a student currently studying the SWAN modeling software for academic purposes. As I am relatively new to this field, I would greatly appreciate your guidance regarding an issue I have encountered. I have created a bathymetric data set in MATLAB, which has a dimension of 66 rows by 53 columns. To input this data into SWAN, I initially wrote the following commands: INPGRID BOTTOM 552305. 4002200. 0. 53 66 150. 150. READINP BOTTOM 1. 'Botinfo_0805.txt' 1 0 FREE However, SWAN returned the following error message: Error: Unexpected end of file while reading To resolve this, I modified the command to: INPGRID BOTTOM 552305. 4002200. 0. 52 65 150. 150. READINP BOTTOM 1. 'Botinfo_0805.txt' 1 0 FREE With this adjustment, SWAN successfully read the entire dataset without any errors. Could you kindly explain why this issue occurs and clarify how SWAN reads and interprets the bathymetric data? Your assistance and detailed explanation would greatly enhance my understanding and help me progress in my studies. Thank you very much for your time and assistance. Best regards, Sihyeon |
|
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
|
36 messages has been excluded from this view by a project administrator.
