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
It seems that while forc_wa is intended to be active, the associated vertical velocity is not being read from the UFS history files and is consequently set to zero.
In my recent SFS work with casegen using zero wa(dzdt) forcing, I found the SCM results to be unsatisfactory compared to UFS simulation, particularly in simulating tropical precipitation over the Indian Ocean. To address this, I conducted a comparative experiment where I reintroduced proper wa forcing during case generation. The results indicated a notable improvement (in my subjective assessment) in precipitation simulations for both hydrostatic and nonhydrostatic scenarios within the SFS project. For hydrostatic cases, I utilized forc_wap since there is no wa (dzdt), but utilized wap (omga) output from the hydrostatic runs.
The text was updated successfully, but these errors were encountered:
It seems that while forc_wa is intended to be active, the associated vertical velocity is not being read from the UFS history files and is consequently set to zero.
In my recent SFS work with casegen using zero wa(dzdt) forcing, I found the SCM results to be unsatisfactory compared to UFS simulation, particularly in simulating tropical precipitation over the Indian Ocean. To address this, I conducted a comparative experiment where I reintroduced proper wa forcing during case generation. The results indicated a notable improvement (in my subjective assessment) in precipitation simulations for both hydrostatic and nonhydrostatic scenarios within the SFS project. For hydrostatic cases, I utilized forc_wap since there is no wa (dzdt), but utilized wap (omga) output from the hydrostatic runs.
The text was updated successfully, but these errors were encountered: