-
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
coawst model without any output #329
Comments
you need to look at what is different. something is different. |
Didn't produce any Err* |
i am not sure. one of the models is not getting the correct info. |
I believe the model is not actually starting to run. I have tried the following: First, I changed the name of the .in file, and the model ran normally but reported an error saying it could not find the corresponding file. However, when I input the correct file name, this problem arises. Second, I changed the number of cores, causing it to mismatch the setting in the .in file. At this point, the model still runs but does not report any errors or produce any output. |
when you changed the number of cores, you say the model 'still runs' . what does that mean? |
For instance, if I define the use of 64 cores in the namelist but only specify 4 cores in the coupling setup, theoretically, there should be an error message. However, there isn't any, and the model continues to run but produces no output. |
So I believe that the model has not correctly read the coupling.in file. |
can you show me the stdout from the model? |
Model only output Intel(R) Parallel Studio XE 2020 Update 4 for Linux* |
this is my coupling,in , the strange thing is that when I debugged using a two-day simulation, it ran successfully and produced results. |
The remaining .in files are provided below. |
i do know that swan does not like long file path_names did that work before? |
When I run the coupled model of WRF, SWAN, and ROMS for a month, I found that the model does not terminate and produces no output except for two lines stating "Coupled Input File name = Projects/cangnan/coupling.in". However, when I debugged using a two-day simulation, it ran normally and produced results. The only thing I changed was the input files corresponding to different time periods and the time settings in the .in file. Now, I'm encountering this issue. Does anyone know what might be causing this? Please help.
The text was updated successfully, but these errors were encountered: