-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SCRIP_COAWST error #332
Comments
This is the running log file |
These are the in file for scrip, the grid files for roms and wrf, and the h file for coawst(hato.txt) |
can you try scrip with just 2 wrf grids? |
Thank you for your reply. |
so i downloaded your wrf-roms.zip, and the roms grid has all 0's for the lon_rho and all 20 for the lat_rho. |
Thanks for your reply. I want to make an ideal tropical cyclone experiment with coawst, so I designed an ideal wrf grid according to the practices of some articles, and obtained the corresponding roms grid according to wrf grid through the wrf2roms_mw file in tools. I will try to change the approach of the ideal grid file. Thanks again. The article I refer to is Zhao X, Chan J C L. Changes in tropical cyclone intensity with translation speed and mixed‐layer depth: idealized WRF‐ROMS coupled model simulations[J]. Quarterly Journal of the Royal Meteorological Society, 2017, 143(702): 152-163. |
Hello,
I'm trying to create an ideal coupling experiment to simulate tropical cyclone. Therefore, the grid information of wrfinput_d01 and roms I obtained did not contain the latitude and longitude information. When I do three layers of nesting for wrf and move the nesting between the second and third layers, I need a scrip file. However, I generated scrip files that could not run m files (Tools/mfiles/mtools/plot_scrip_weights.m).
I find that the Total number of links in the output log file is always 0. Is it a problem with my wrf and roms grid files? The scrip_coawst program can always end successfully and get a scrip file, even though the file is wrong.
Thanks in advance,
The text was updated successfully, but these errors were encountered: