Why So_h is commented in the WW3 cap? #1280
Replies: 4 comments 3 replies
-
@JessicaMeixner-NOAA @DeniseWorthen Any idea? |
Beta Was this translation helpful? Give feedback.
-
@uturuncoglu I know of no specific reason it is not enabled. We do not export |
Beta Was this translation helpful? Give feedback.
-
Okay. Let me try in my end to see what happens. If it works without any issue. Maybe we could activate it. It would be nice to ask also to @mvertens since it is part of NCAR cap. |
Beta Was this translation helpful? Give feedback.
-
@uturuncoglu It is due to scale and coarseness of global scale applications (~km), which were the initial intention of UFS-weather-model development where the wave component runs on static depth (MSL). The MOM6 grid is also curvilinear (I recall it around 5 to 10 min, which is very coarse in the coastal regions). The topobathy is not resolved in such scale, therefore water surface was excluded. I did some preliminary work, showing it does not add values on waves for such coarse resolution and also in the ocean model. On the contrary, in coastal scale, water level and current in very shallow water matter (tens of meter scale). |
Beta Was this translation helpful? Give feedback.
-
We are plaining to use sea surface height for coupling with ocean model under UFS Coastal since it is important for the shallow regions but when I checked the the NUOPC cap (mesh cap) it seems that
So_h
variable is commented out. Is there any specific reason for it? Otherwise, it would be activate it and test it under UFS Coastal.WW3/model/src/wav_import_export.F90
Line 109 in d9b3172
Beta Was this translation helpful? Give feedback.
All reactions