You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the WW3 model with a cold start, and to avoid initializing the model with Hs = 0 m, I used ww3_strt to generate the initial conditions using Option 3. My simulation involves two-way (bidirectional) nesting, so I ran ww3_multi.
However, after the simulation completed, I noticed that in the parent domain, the nested (child) domain becomes visible, particularly in regions where the wave heights in both domains do not match. For example, in the parent domain the wave height may be around 2 meters, while in the overlapping boundary region of the nested domain it remains at 1 meter. This causes a discontinuity and an unrealistic transition at the nesting interface.
Is there a way to prevent this behavior?
Also, is it correct to use the output from ww3_strt as a restart file at the beginning of the run? Specifically, I execute ww3_strt for both domains and then rename the outputs to restart.grid1, restart.grid2, and restart.input, so that WW3 recognizes them as initial conditions for the simulation.
Any guidance or clarification would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I am running the WW3 model with a cold start, and to avoid initializing the model with Hs = 0 m, I used ww3_strt to generate the initial conditions using Option 3. My simulation involves two-way (bidirectional) nesting, so I ran ww3_multi.
However, after the simulation completed, I noticed that in the parent domain, the nested (child) domain becomes visible, particularly in regions where the wave heights in both domains do not match. For example, in the parent domain the wave height may be around 2 meters, while in the overlapping boundary region of the nested domain it remains at 1 meter. This causes a discontinuity and an unrealistic transition at the nesting interface.
Is there a way to prevent this behavior?
Also, is it correct to use the output from ww3_strt as a restart file at the beginning of the run? Specifically, I execute ww3_strt for both domains and then rename the outputs to restart.grid1, restart.grid2, and restart.input, so that WW3 recognizes them as initial conditions for the simulation.
Any guidance or clarification would be greatly appreciated.
Sincerely,
Alejandro
Beta Was this translation helpful? Give feedback.
All reactions